Date: Wed, 6 Dec 2000 21:40:25 -0500 From: Ryan Younce <ryan@manunkind.org> To: Cliff Sarginson <cliff@raggedclown.net> Cc: Ryan Younce <ryan@manunkind.org>, Joe Oliveiro <joe@advancewebhosting.com>, Corey Brune <brune@sdf.lonestar.org>, freebsd-questions@freebsd.org Subject: Re: Process wont be killed. Message-ID: <20001206214025.B19885@cheshire.manunkind.org> In-Reply-To: <20001207003053.A5779@buffy.local>; from cliff@raggedclown.net on Thu, Dec 07, 2000 at 12:30:53AM %2B0100 References: <20001206160200.A19885@cheshire.manunkind.org> <Pine.BSF.4.21.0012061635300.86799-100000@joe.pythonvideo.com> <20001206173151.A20117@cheshire.manunkind.org> <20001207003053.A5779@buffy.local>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake Cliff Sarginson <cliff@raggedclown.net>: > I am glad to see something's never change. > All unix type systems seem to have had this problem since > the dawn of time. > A process can get into a certain state, waiting on some > event that never happens and the kernel never wakes it up > from this state. It only goes away after a reboot. Yes, but under FreeBSD you can specify that system calls are to be interruptible by passing the -i option to mount_nfs(8). -- Ryan Younce, Cat Herder / ryan@manunkind.org / http://www.manunkind.org/~ryan "The obvious mathematical breakthrough would be development of an easy way to factor large prime numbers." --Bill Gates, The Road Ahead (Viking Penguin 95) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001206214025.B19885>