On Tue, Sep 16, 2008 at 05:46:55PM +0200, Patrick Winnertz wrote: > > *shrug* Bash does that. The issue would be to do the following upon > > exiting: lock the file, read the history in it, append the new history, > > close the file, unlock the file. > Try it. I've always issues with bash and parallel logging into the history > file. > One session is always missing.
Well, I have worse issues: my .bash_history gets truncated after it is about 2 MiB :) . But I'm not sure whether bash locks the file. But that doesn't mean this is not doable. > ps: If you like , implement it, and I'll fix it. I had logged it so that someone who feels like that wouldn't look in vain for a task :) . With kind regards, -- Baurzhan Ismagulov http://www.kz-easy.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
