possible bash bug - 'history'

2013-07-19 Thread Mike Fied
Dear GNU developer/code maintainer, Please take a second to take a look at this problem - this might or might not be a bug, or rather a feature is not implemented in BASH: I am trying to get the current or "last" command line printed as the result of history, or a BASH variable ( to my knowledge i

Re: bash kill(1) doesn't report errors when $(ulimit -i) is exceeded

2013-07-19 Thread Irek Szczesniak
On Wed, Jul 17, 2013 at 1:52 AM, Cedric Blancher wrote: > On 16 July 2013 23:12, Linus Torvalds wrote: >> On Tue, Jul 16, 2013 at 1:31 PM, Lionel Cons >> wrote: >>> >>> Either your ulimit -i is greater than 63000 or we have a Linux bug. If >>> ulimit -i is reached then kill(1) should fail. >> >

Re: History file clobbered by multiple simultaneous exits

2013-07-19 Thread Chet Ramey
On 7/19/13 3:40 AM, Geoff Kuenning wrote: > Now, to clarify: the difficulty isn't that bash overwrites the history > file. That's the default behavior, and it's to be expected. If a user > opens three shells (in any fashion) and then successively types "exit" > in each, it's to be expected that

Re: History file clobbered by multiple simultaneous exits

2013-07-19 Thread Linda Walsh
Geoff Kuenning wrote: > But right now, if all three of those shells exit simultaneously--for > whatever reason--there is a significant probability that the history > file will end up zero-length. That's not theoretical; I've experienced > it multiple times. And that's a bug, plain and simple.

Re: History file clobbered by multiple simultaneous exits

2013-07-19 Thread Geoff Kuenning
I have to apologize; it's clear that we're not connecting. I must also apologize for misunderstanding your (Linda's) role; I DO appreciate getting suggestions and help from a bash fan regardless of whether you're personally responsible for the code. It's perhaps also worth mentioning that the und