Date: Thu, 13 Nov 1997 10:59:43 -0800 (PST) From: Simon Shapiro <Shimon@i-connect.net> To: Archie Cobbs <archie@whistle.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: unkillable process Message-ID: <XFMail.971113105943.Shimon@i-Connect.Net> In-Reply-To: <199711131848.KAA19595@bubba.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Archie Cobbs; On 13-Nov-97 you wrote: > Simon Shapiro writes: > > Hi Archie Cobbs; On 12-Nov-97 you wrote: > > > Try the following experiment (on 2.2 and mabye 3.0): > > > > > > 1. Create a named pipe > > > 2. Start typing into it using cat > > > 3. Hit control-C as many times as you want > > > > > > You'll see that the process will not die even with kill -9, > > > as it is stuck in uninterrupible disk sleep ("fifo"). > > > > > > But as soon as you read from the other end of the pipe, > > > the process exits. > > > > > > Is there a missing PCATCH flag to tsleep() somewhere? > > > Is this appropriate behavior? (hint: rhetorical question) > > > > From what I remember, this is a typical (if ugly Unix behavior. > > Hmm... does anyone else besides me have the opinion that, > while it may be typical, this behavior is also *broken*? Oh, I agree it is broken. I could never understand why certain syscalls block without PCATCH. --- If Microsoft Built Cars: Every time they repainted the lines on the road, you'd have to buy a new car. Sincerely Yours, Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.799.2313
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.971113105943.Shimon>