Debian bug report logs - #1420 , boring messages ----------------------------------------------------------------------- Message sent to debian-devel@pixar.com: Subject: Bug#1420: reboot too eager to reboot Reply-To: Richard Kettlewell , debian-bugs@pixar.com Resent-From: Richard Kettlewell Resent-To: debian-devel@pixar.com Resent-Date: Thu, 21 Sep 1995 18:03:06 GMT Resent-Message-ID: Resent-Sender: iwj10@cus.cam.ac.uk X-Debian-PR-Package: sysvinit X-Debian-PR-Keywords: Received: via spool for debian-bugs; Thu, 21 Sep 1995 18:03:06 GMT Received: with rfc822 via encapsulated-mail; Thu, 21 Sep 1995 17:48:53 GMT Received: from pixar.com by mongo.pixar.com with smtp (Smail3.1.28.1 #15) id m0svpij-0005lcC; Thu, 21 Sep 95 10:47 PDT Received: from muskogee.elmail.co.uk by pixar.com with SMTP id AA20047 (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Thu, 21 Sep 1995 10:47:16 -0700 Received: from sfere.elmail.co.uk ([193.116.29.15]) by muskogee.elmail.co.uk with smtp id (Debian /\oo/\ Smail3.1.29.1 #29.33); Thu, 21 Sep 95 18:47 BST Received: by sfere.elmail.co.uk id (Debian /\oo/\ Smail3.1.29.1 #29.33); Wed, 20 Sep 95 20:38 BST Message-Id: <8Mo6T23B2@sfere.elmail.co.uk> Date: Wed, 20 Sep 95 20:38:42 +0100 (BST) From: Richard Kettlewell To: debian-bugs@pixar.com Package: sysvinit Version: 2.56-5 Rebooting my work machine after three weeks uptime I did what I almost invariably do at home and typed `reboot'. At home this calls shutdown, and tidies everything up nicely. (I have the same version of sysvinit both at home and at work.) At work, however, the effect was to briefly print a message saying something to the effect of ``cannot determine runlevel, doing a hard reboot''. It then rebooted immediately, in particular without umounting anything. The reboot man page notes that shutdown will be called if the system is not in runlevel 0 or 6; I don't know what condition it is that causes reboot to be unable to determine the runlevel but it seems to be to be highly unreasonable to just assume that it's OK to reboot if it can't work out whether or not it is. More sensible semantics in this situation would be to only carry out the reboot if the -f flag is present. -- Richard Kettlewell Work+home: Home only: ----------------------------------------------------------------------- Message sent: From: iwj10@thor.cam.ac.uk (Ian Jackson) To: Richard Kettlewell Subject: Bug#1420: Acknowledgement (was: reboot too eager to reboot) In-Reply-To: <8Mo6T23B2@sfere.elmail.co.uk> References: <8Mo6T23B2@sfere.elmail.co.uk> Thank you for the problem report you have sent regarding Debian GNU/Linux. This is an automatically generated reply, to let you know your message has been received. It is being forwarded to the developers' mailing list for their attention; they will reply in due course. If you wish to submit further information on your problem, please send it to debian-bugs@pixar.com, but please ensure that the Subject line of your message starts with "Bug#1420" or "Re: Bug#1420" so that we can identify it as relating to the same problem. Please do not reply to the address at the top of this message, unless you wish to report a problem with the bug-tracking system. Ian Jackson (maintainer, debian-bugs) ----------------------------------------------------------------------- Ian Jackson / iwj10@thor.cam.ac.uk , with the debian-bugs tracking mechanism This page last modified 07:43:01 GMT Wed 01 Nov