From owner-cvs-all Tue Mar 20 21: 8: 6 2001 Delivered-To: cvs-all@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id CFCC537B71E; Tue, 20 Mar 2001 21:07:58 -0800 (PST) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f2L57rs76820; Tue, 20 Mar 2001 22:07:53 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200103210507.f2L57rs76820@aslan.scsiguy.com> To: Ian Dowse Cc: Robert Watson , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sbin/reboot reboot.c In-Reply-To: Your message of "Tue, 20 Mar 2001 18:57:57 GMT." <200103201857.aa69023@salmon.maths.tcd.ie> Date: Tue, 20 Mar 2001 22:07:53 -0700 From: "Justin T. Gibbs" Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Good point. It seems that there are just two implementations... Why not put an implementation in libutil or some other place where they can be shared. >I could implement a similar dynamic delay in init I suppose. On my >laptop I was seeing page-ins occurring for about 20 seconds after >the SIGTERM, so 10 seconds isn't always enough. Is there any portion of the process state that the shutdown code could monitor to see if this is the reason for the delay? Picking an arbitrary number feels wrong. It would be nice if processes could provide some type of status that, if left unchanged for a period of time, indicated they were stuck and waranted a shot through the head. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message