Hi all,
I routinely am logged into a server with multiple consoles (I log in
with one (the same) regular user, then su - to root).
This morning I tried to grep roots .bash_history for a command I ran
some time ago, and it wasn't there. I know I ran it, so I'd like to
configure my bash
On Wed, Jan 08, 2014 at 07:10:10AM -0500, Tanstaafl wrote:
Hi all,
I routinely am logged into a server with multiple consoles (I log in
with one (the same) regular user, then su - to root).
This morning I tried to grep roots .bash_history for a command I ran
some time ago, and it wasn't
On 08/01/2014 14:10, Tanstaafl wrote:
Hi all,
I routinely am logged into a server with multiple consoles (I log in
with one (the same) regular user, then su - to root).
This morning I tried to grep roots .bash_history for a command I ran
some time ago, and it wasn't there. I know I ran
Bruce Hill da...@happypenguincomputers.com wrote:
On Wed, Jan 08, 2014 at 07:10:10AM -0500, Tanstaafl wrote:
Hi all,
I routinely am logged into a server with multiple consoles (I log in
with one (the same) regular user, then su - to root).
This morning I tried to grep roots
http://mywiki.wooledge.org/BashFAQ/088
The advice here to use awk to compress log files seems a bit dated.
Bash now allows you to set in .bashrc:
export HISTCONTROL=erasedups
I don't know that there's an ultimate answer to history management.
Personally, for years I have had my prompt set
5 matches
Mail list logo