From owner-freebsd-questions@freebsd.org Tue Mar 21 15:19:58 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD49AD168C7 for ; Tue, 21 Mar 2017 15:19:58 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay12.qsc.de (mailrelay12.qsc.de [212.99.163.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 279653D7 for ; Tue, 21 Mar 2017 15:19:57 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay12.qsc.de; Tue, 21 Mar 2017 16:19:49 +0100 Received: from r56.edvax.de (port-92-195-127-117.dynamic.qsc.de [92.195.127.117]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 86D3D3CBF9; Tue, 21 Mar 2017 16:19:48 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id v2LFJllw002153; Tue, 21 Mar 2017 16:19:47 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Tue, 21 Mar 2017 16:19:47 +0100 From: Polytropon To: Arthur Chance Cc: Ernie Luzar , freebsd-questions@freebsd.org Subject: Re: command line history broken in 11.0 Message-Id: <20170321161947.f34a308d.freebsd@edvax.de> In-Reply-To: References: <58D019EE.9030508@gmail.com> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay12.qsc.de with C73246A4CDE X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.2080 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Mar 2017 15:19:58 -0000 On Tue, 21 Mar 2017 14:31:34 +0000, Arthur Chance wrote: > On 20/03/2017 18:05, Ernie Luzar wrote: > > On 10.3 I had the current session saving the command line history when > > issuing the shutdown, halt, and reboot command by using these alias > > commands that I added to the .cshrc file of my logged in user account. > > > > alias sd "exit && shutdown now" > > alias sdp "exit && shutdown -p now" > > alias rboot "exit && reboot" > > alias stop "exit && halt" > > > > Now after doing a clean install of 11.0 and using the same .cshrc file > > the rboot and stop alias commands no longer save the current history. > > They act like the exit command is not getting executed. The sd and sdp > > alias commands are working as expected. > > > > When existing from a session terminal by issuing the exit command does > > still save the current history. > > > > Is there an alternate method I can use? > > > > To the best of my understanding, reboot and halt should really only be > used in single user mode, because they don't cleanly close down running > programs - they're more like pulling the power plug after a couple of > syncs. That's been the case for a long time now. Basically, "reboot" is equivalent to "shutdown -r now", just as "halt" is to "shutdown -h now". Both things do the same. >From "man reboot": The halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM (and subsequently a SIGKILL) and, respec- tively, halt or restart the system. The action is logged, including entering a shutdown record into the wtmp(5) file. This is what shutdown does as well. But see "man shutdown", especially option -o, for differences related to calling init. Both variations should be fully safe to use from multi user mode. The manpages don't say otherwise... > Is there any reason for you not to use shutdown exclusively? The -p and > -r modifiers give you power off and reboot abilities, and daemons get > cleanly shut down, which may save you from a broken database one day. Note: -p = power off, -h = halt (does _not_ power off); "halt -p" and "shutdown -p now" perform the same task (shut down, then power off), while "halt" and "shutdown -h now" keep the system powered on after shutting down. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...