This is discussed a bit here, along with a common pain point for
tmux/screen users:
https://news.ycombinator.com/item?id=10164053
zsh gets around both issues with a variety of options to have a synchronous
and interleaved history file.
-Jonathan Hankins
On Tue, Jan 31, 2017 at 1:40 PM Greg Wool
GW> Log out, log back in as root, issue the command, and accept that root's
GW> (very short) shell history will be lost.
Well mention that on the man page.
I.e., the man page should address the paradox of saving a complete
history vs. being able to turn off one's computer.
On Wed, Feb 01, 2017 at 03:31:57AM +0800, ? Dan Jacobson wrote:
> GW> Log out, log back in as root, issue the command, and accept that root's
> GW> (very short) shell history will be lost.
>
> Well mention that on the man page.
> I.e., the man page should address the paradox of saving a co
On Wed, Feb 01, 2017 at 03:13:45AM +0800, ? Dan Jacobson wrote:
> GW> I'm confused. You don't logout before shutting down your computer?
> GW> I would strongly recommend doing so, unless it's an emergency.
>
> All I know is I want to issue one command to turn off the computer.
> If I logg
GW> I'm confused. You don't logout before shutting down your computer?
GW> I would strongly recommend doing so, unless it's an emergency.
All I know is I want to issue one command to turn off the computer.
If I logged off first, how could I issue that (poweroff(8)) command?
OK you people turn of
On Tue, Jan 31, 2017 at 10:13:46AM +0800, ? Dan Jacobson wrote:
> However on slower systems, at the end of the day when the user issues
> the poweroff(8) command, all this might not complete, resulting in the
> entire day's of history getting thrown away.
I'm confused. You don't logout be
Man page says:
When a shell with history enabled exits...
and
The shell exits by default upon receipt of a SIGHUP...
However on slower systems, at the end of the day when the user issues
the poweroff(8) command, all this might not complete, resulting in the
entire day's of history getting thr
