Date: 06 Feb 2001 12:25:28 -0500 From: Randell Jesup <rjesup@wgate.com> To: current@FreeBSD.ORG Subject: Re: Please review sh SIGSTOP fix Message-ID: <ybud7cvn2pj.fsf@jesup.eng.tvol.net.jesup.eng.tvol.net> In-Reply-To: Martin Cracauer's message of "Fri, 2 Feb 2001 11:50:41 %2B0100"
next in thread | raw e-mail | index | archive | help
Martin Cracauer <cracauer@cons.org> writes:
>would you please have a look at the following sh fix? My brain is a
>bit rusty and maybe I overlook a drawback.
>
>When a child is receiving SIGSTOP, eval continues with the next
>command. While that is correct for the interactive case (Control-Z
>and you get the prompt back), it is wrong for a shellscript, which
>just continues with the next command, never again waiting for the
>stopped child. Noted when childs from cronjobs were stopped, just to
>make more processes (by wosch).
Careful - is this behavior used as a feature during boot when
starting services? I.e. you can ^Z and it will continue with the next
service; effectively backgrounding the service that's waiting. I.e. is
this a feature (perhaps accidental) that people assume and rely on? And
if so, is there another way to get the functionality, and is it important
to people?
Perhaps I'm totally wrong here and misunderstood the issue.
--
Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94)
rjesup@wgate.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ybud7cvn2pj.fsf>