From owner-freebsd-hackers Tue Dec 22 06:07:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20687 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 06:07:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA20681 for ; Tue, 22 Dec 1998 06:07:19 -0800 (PST) (envelope-from rivers@dignus.com) Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id GAA17806 for ; Tue, 22 Dec 1998 06:07:12 -0800 (PST) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id JAA28650; Tue, 22 Dec 1998 09:07:19 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.1/8.8.5) with ESMTP id JAA27235; Tue, 22 Dec 1998 09:54:50 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.1/8.6.9) id JAA22681; Tue, 22 Dec 1998 09:08:27 -0500 (EST) Date: Tue, 22 Dec 1998 09:08:27 -0500 (EST) From: Thomas David Rivers Message-Id: <199812221408.JAA22681@lakes.dignus.com> To: cracauer@cons.org, freebsd-hackers@freefall.cdrom.com, rivers@dignus.com Subject: Re: Interesting un-interruptible shell script on 3.0-RELEASE (possible sh bug?) In-Reply-To: <19981222140604.A12246@cons.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In <19981222134641.A12019@cons.org>, Martin Cracauer wrote: > > In <199812220243.VAA21066@lakes.dignus.com>, Thomas David Rivers wrote: > > > > > > Try the following on a 3.0-RELEASE system, under the bourne shell: > > > > > > while true > > > do > > > sleep 2 > > > done > > While you're at it, what does this show? > > which sleep > sleep -? > > This most probable cause of this problem is a sleep binary that > catches SIGINT, but doesn't kill itself with SIGINT afterwards. I > could imagine that some braindead port installs such a thing. Maybe > GNU shellutils or such? > > If it's /bin/sleep, these please send me the full kdump output (of > SIGINTing the above script, not of `which` :-). > > Thanks > Martin Well - it can't be sleep - as the same thing happens if you substitute sync for the sleep command, i.e. while true do sync done can't be interrupted either (although, it can be if you place it in a file and execute the file.) That kinda points to the shell (/bin/sh) as the culprit (or, perhaps the tty driver somehow?) - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message