[colug-432] Search Command History

Brian Miller bnmille at gmail.com
Tue Feb 11 19:32:18 EST 2014


On 02/11/2014 08:44 AM, Richard Hornsby wrote:

> On a related note, one thing I’ve noticed is that the bash history
> doesn’t seem to be written to disk immediately.  Even from within our
> office, we’re required to VPN into the datacenter before being able to
> log onto any hosts.  The VPN isn’t the most stable thing in the world,
> nor the are wireless connections we have to use.  (They recently moved
> us to a brand new building and decided during construction that wired
> connections for employees’ desks were an unnecessary expense.)  It seems
> that when my connection gets dropped and the shell is pre-maturely
> terminated, all the history from that session is gone.
>


I would get into the habit of running "screen" whenever you make an SSH 
connection to your server.  That way, when your connection gets dropped, 
you can re-connect, and run "screen -r" to pick up where you left off. 
It's really handy if you need to kick off a long running process.  You 
can start the process at work, disconnect, go home, eat dinner, log in 
through the VPN, and then move on to the next step.




More information about the colug-432 mailing list