Re: history EINTR bug

2015-02-24 Thread Chet Ramey
On 2/22/15 10:45 PM, gregrwm wrote: >> >> > this just happened: >> >> > bash: history: write error: Interrupted system call >> >> >> >> What command did you use? >> > >> > history|&less >> >> The most likely possibility is that you quit out of less before `history' >> wrote enough data to cause st

Re: history EINTR bug

2015-02-22 Thread gregrwm
On Feb 22, 2015 7:57 PM, "Chet Ramey" wrote: > On 2/22/15 5:57 PM, gregrwm wrote: > > On Feb 13, 2015 7:38 AM, "Chet Ramey" > > wrote: > >> On 2/12/15 9:06 AM, gregrwm wrote: > >> > i now suspect bash does not properly handle EINTR while handling history. > >> > >> May

Re: history EINTR bug

2015-02-22 Thread Chet Ramey
On 2/22/15 5:57 PM, gregrwm wrote: > On Feb 13, 2015 7:38 AM, "Chet Ramey" > 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. >> >> > thi

Re: history EINTR bug

2015-02-22 Thread gregrwm
On Feb 13, 2015 7:38 AM, "Chet Ramey" 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

Re: history EINTR bug

2015-02-13 Thread Chet Ramey
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? Writing the history to stdout