|
| From: | gregrwm |
| Subject: | Re: history EINTR bug |
| Date: | Sun, 22 Feb 2015 16:57:13 -0600 |
On Feb 13, 2015 7:38 AM, "Chet Ramey" <chet.ramey@case.edu> wrote:
> On 2/12/15 9:06 AM, gregrwm wrote:
> > i now suspect bash does not properly handle EINTR while handling history.
>
> Maybe. There's not enough information here to say.
>
> > this just happened:
> > bash: history: write error: Interrupted system call
>
> What command did you use?
history|&less
on seeing less than the full history, with that error instead, it got me to thinking it's quite likely something quite similar sometimes happens to cause failure to write out all the history at shutdown, followed by further attempts to write the history again.
> Writing the history to stdout is different
> from writing to a pipe, which is different from using history -a or
> history -w to write to a file.
>
> It's difficult to say more without knowing which signal interrupted
> the command.
| [Prev in Thread] | Current Thread | [Next in Thread] |