[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
job-control warning message that maybe shouldn't be printed
From: |
Peter Cordes |
Subject: |
job-control warning message that maybe shouldn't be printed |
Date: |
Thu, 28 Nov 2013 08:23:01 -0400 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
I submitted this on savannah a couple days ago:
https://savannah.gnu.org/support/?108450
As I said there, the warning message for bash re-using a PID that
it's tracking for exitted processes in suspended pipelines or w/e has
an off-by-one error (jobs.c:892).
To summarize what I wrote on savannah:
The real question is whether there's any point in printing this
warning, or in continuing to track the PIDs of processes that have
long since exitted. (in a foo | grep | less, suspend less use case,
you have bash remembering the PID for foo and grep, even after they
exit). And bash prints a warning if you happen to run a command that
re-uses one of those PIDs. I don't see how this is of any use. It
just confused my dad, and me until I found the source code that
printed it.
Thanks for making such a nice shell, this is probably the first time
I've had it do something weird that wasn't my fault.
Oh, also, the online bug-bash archive has a bad habbit of replacing
code with address@hidden. There was a whole thread about setting
PS1=whatever that is now a complete mystery to non-subscribers!
--
#define X(x,y) x##y
Peter Cordes ; e-mail: X(peter@cor , des.ca)
"The gods confound the man who first found out how to distinguish the hours!
Confound him, too, who in this place set up a sundial, to cut and hack
my day so wretchedly into small pieces!" -- Plautus, 200 BC