Hello *, Am 2008-09-24 23:14:24, schrieb Baurzhan Ismagulov: > This is certainly interesting. I suppose you mean history -w and history > -a, don't you? But if bash doesn't lock the file, I still don't see how > this can be "mathematically" correct: If history -a reads the file into > the memory and writes the new one instead, another session could still > corrupt the file. Could you please elaborate?
While writing out the history file it seems to be locked,
but WHILE BaSH is running, there is nothing locked.
Thanks, Greetings and nice Day/Evening
Michelle Konzack
Systemadministrator
24V Electronic Engineer
Tamay Dogan Network
Debian GNU/Linux Consultant
--
Linux-User #280138 with the Linux Counter, http://counter.li.org/
##################### Debian GNU/Linux Consultant #####################
Michelle Konzack Apt. 917 ICQ #328449886
+49/177/9351947 50, rue de Soultz MSN LinuxMichi
+33/6/61925193 67100 Strasbourg/France IRC #Debian (irc.icq.com)
signature.pgp
Description: Digital signature
