Date: Sat, 22 Oct 2016 11:01:15 -0500 From: Adam Vande More <amvandemore@gmail.com> To: Ernie Luzar <luzar722@gmail.com> Cc: Freebsd Questions <FreeBSD-questions@freebsd.org> Subject: Re: console command history Message-ID: <CA%2BtpaK3wfHRJJhoEpLdsCD=Ws1vP7W5h0qjeo-Oy5YQ%2BERpiCA@mail.gmail.com> In-Reply-To: <580B7A86.9050209@gmail.com> References: <580A4A2F.4020902@gmail.com> <CA%2BtpaK2W5chboZSgGt3%2BrEkjhtaRpMd_1_=ymi=R81U3omtQWw@mail.gmail.com> <580B7A86.9050209@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Thank you. You hit the mail on the head. The original posted problem has > nothing to do with those statements referenced in previous posts in this > thread. > > The real problem is the shutdown, halt, and reboot commands just kill the > system which includes the csh shell that the command was issued from > denning the running shell the opportunity to save the current console > command history so it can be restored when the root logs in after the > system is started again. > FYI, reboot(1) should not be used to reboot from multiuser mode, use shutdown(1) for that. Something like "history -S" would need to be part of the prompt, or a specific option in tcsh to commit history at each new prompt. Linux/Bash seems to do the sensible thing, perhaps it would be good to determine how it's done there. -- Adam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BtpaK3wfHRJJhoEpLdsCD=Ws1vP7W5h0qjeo-Oy5YQ%2BERpiCA>