On 1/30/15 3:50 PM, Jonathan Hankins wrote:
> I agree about being able to use named pipes, etc. as HISTFILE. My concern
> is that I think there may be a code path that leads to rename() and
> open(O_TRUNC...) being called on something that isn't a regular file.
OK, say the history file is not a r
On 1/30/15 4:39 PM, Jonathan Hankins wrote:
> And with both rename()
> calls, ERRNO should be reported to the user if they fail.
No. The return code should indicate whether or not the history file
was written correctly. Failing to backup the history file should not
affect that return value, sin
Dear bash developers -
It is very difficult to overcome the problems caused by
the scenario described within this email without something the
enclosed "setpgrp " and "killpg "
bash loadable builtins .
Without them, or options to change signal handling for simple
commands, it is too easy to cre
