From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14136 invoked from network); 3 May 2004 08:30:20 +0000 Received: from smtp.gentoo.org (128.193.0.39) by eagle.gentoo.oregonstate.edu with DES-CBC3-SHA encrypted SMTP; 3 May 2004 08:30:20 +0000 Received: from lists.gentoo.org ([128.193.0.34] helo=eagle.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.24) id 1BKYqC-0002Vg-Ku for arch-gentoo-dev@lists.gentoo.org; Mon, 03 May 2004 08:30:20 +0000 Received: (qmail 31985 invoked by uid 50004); 3 May 2004 08:30:19 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 13790 invoked from network); 3 May 2004 08:30:18 +0000 From: Paul de Vrieze To: gentoo-dev@lists.gentoo.org Date: Mon, 3 May 2004 10:30:16 +0200 User-Agent: KMail/1.6.2 References: <20040502173223.GA7160@linux1.home> <1083561023.5397.42.camel@newkid.milsson.nu> <1083564905.8372.3.camel@TesterTop.tester.ca> In-Reply-To: <1083564905.8372.3.camel@TesterTop.tester.ca> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200405031030.16829.pauldv@gentoo.org> Subject: Re: [gentoo-dev] strange gentoo shutdown sequence X-Archives-Salt: 6e9eea7a-9529-41d9-91e2-fdf98e958bff X-Archives-Hash: 766acb83bd6c48fc9af7e3b2a00abc75 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 03 May 2004 08:15, Olivier Cr=EAte wrote: > On Mon, 2004-05-03 at 07:10, John Nilsson wrote: > > While on the topic: > > Is it resonable to patch gdm so that /etc/init.d/xdm is zapped > > after gdm is killed by selecting reboot/shutdown from the login > > screen? It just annoys me that the script errors while shutting > > down. > > This is imho a misfeature of the current initscripts system. The > started-ness of an application is only checked against a file and not > against the current real status. We should probably add a possible > "status()" function to them (that would default to true) that would > check if the service is still running in a custom way.. And zap it if > it isnt... The problem there is with dependencies, should they be > stopped if the service died? But the current system is clearly > broken.. I agree, I think we should enhance the init scripts with another function=20 that can check the status of a daemon (in some way) and as such also=20 does not complain when a died daemon needs to be started. Paul =2D --=20 Paul de Vrieze Gentoo Developer Mail: pauldv@gentoo.org Homepage: http://www.devrieze.net =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAlgMYbKx5DBjWFdsRAmOTAKDnA9E0PAVsCtMFAFJIkeKbLuJX/ACcDoCK k3gzkzUnrA0n2unCEEpERH0=3D =3D+tIc =2D----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list