Anthony Boynes wrote:
> Each user should have a .bash_history file in their
> home directory, which contains that information.
Do "man bash" for a very detailed discussion on the
behavior and options of bash's history feature.
Certain commands may not be logged, and successive
duplications may be suppressed. The output file
name can be changed. You can turn history off by
unsetting the HISTFILE variable. HISTSIZE defaults
to 500 lines -- I tend to set it at a few thousand,
heeding Napoleon's warning. You can suppress the
first line of a recorded command based on patterns,
but any continuation lines aren't screened.
Note that the history is generally not written until
the session ends, but is kept in memory during the
session. Some aborts or disconnects seem to lose
the session's history, not writing it out to the
history file.
This also means that one session can't see the current
history stream of another current session. But you
can get a session to dump its current history preceded
by whatever's in .bash_history using:
history > some-other-file
... note that this blindly dumps all available history
so you'd need to be aware of redundant information.
These behaviors differ among operating systems and
shells. There may be a .history file (sh) for
example. In Solaris 8 under ksh, the current history
among all sessions was available for recall immediately
-- a curse or a blessing, depending on what you wanted
to recall. On balance I prefer keeping them separate,
since you can always paste between sessions. I don't
remember if Solaris ksh kept everything updated
currently to disk, but if so that would explain how
one session's history would be available to another.
Vic
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)