[Bug 1174272] Re: 'reboot now' reverting to maintenance mode

[Dimitri Pappas]

That is the point though. If retaining conventions of the past is such an important factor, then I wonder why I could (until recently, at least) issue 'shutdown now' or 'reboot now' on any machine running debian/ubuntu, and it would complete a full power-off, or reset, respectively, each time...
If you wish to insist that, well, I was 'doing it wrong' for what could well be 20+ years in my case prior to these changes, then I am happily to concede that. However, if that is the case, then I wish know why it behaved the way I have described until these recent changes. You see, these bugs (1174272 & 1065851) were confirmed by others, implying that others have also experienced the 'unexpected' (unintuivie/'buggy') effects of these changes. If indeed shutdown only powers-off when '-h/-H' is used, and reboot is expected to revert to single-user mode when 'now' is supplied as an argument [who would have thought...?]) then it would seem that the method I've used for the past 20+ years, or to rephrase: 'the way shutdown has worked' for at least the last couple of years, that I can recall, has been recently changed? Surely mere convention is no excuse to obstruct progress to code in any case...

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1174272

Title:
  'reboot now' reverting to maintenance mode

Status in “upstart” package in Ubuntu:
  Invalid

Bug description:
  A forum thread has been opened first, describing the problem. For
  reference, that forum thread can be found here:
  http://ubuntuforums.org/showthread.php?t=2139160&p=12624806

  Problem is described below:

  When the command "reboot now" is issued:

  root at server:~# reboot now
  Broadcast message from root at server
  (/dev/pts/0) at 00:00 ...
  The system is going down to maintenance mode NOW!

  A few moments later.. SSHd is killed, but the box responds to pings
  (Inaccessible remotely unless a hard-reset is performed)

  * Asking all remaining processes to terminate...
  * Killing all remaining processes... [fail]
  * Will now switch to single-user mode
  Give root password for maintenance
  (or type Control-D to continue):

  Just "reboot", and it works fine
  root at server:~# reboot
  Broadcast message from root at server
  (/dev/pts/0) at 00:00 ...
  The system is going down for reboot NOW!

  Some distro's require a time / 'now' as an argument, and thus I became
  accustomed to performing my reboots in this way. Now it seems to be a
  potential trap that causes the machine not to reboot, which is
  especially painful if we're talking about a headless/hosted dedicated
  server. Even if ubuntu doesn't like 'reboot now' syntax, I still can't
  understand why "reboot now" should bring the box to console
  maintenance mode anyway - perhaps it should rather return an error, or
  syntax help

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: upstart 1.8-0ubuntu1
  Uname: Linux 3.9.0-030900rc8-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Mon Apr 29 13:22:02 2013
  InstallationDate: Installed on 2010-12-11 (870 days ago)
  InstallationMedia: Ubuntu-Server 10.10 "Maverick Meerkat" - Release i386 (20101007)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.9.0-030900rc8-generic root=UUID=cde38363-cc5e-4b66-ba3d-f64dd0ed4987 ro quiet
  SourcePackage: upstart
  UpgradeStatus: Upgraded to raring on 2013-04-26 (3 days ago)
  UpstartBugCategory: System

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1174272/+subscriptions