touch-packages team mailing list archive

[Steve Langasek <steve.langasek@xxxxxxxxxxxxx>]

Ok.  I don't have a theory as to what would be short-circuiting the tail
end of /etc/rc0.d for this case.  As far as I can see, logind just calls
'poweroff', which should do the right thing - and certainly, sendsigs
should always be followed by umountnfs.sh, networking, umountfs,
umountroot, and {halt,reboot}.  If these scripts are not being called
(as opposed to their output simply not being shown on the console), then
that can only be due to something force-halting the system.

Is there any chance you could capture the output of 'udevadm monitor -e'
in this situation?  I would like to verify that the udev events are what
we expect.

It might also be helpful to locally divert /sbin/reboot with a wrapper
that records the args, and the details about the calling process, for
later analysis.

** Changed in: systemd (Ubuntu)
     Assignee: (unassigned) => Steve Langasek (vorlon)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1349566

Title:
  systemd-logind triggered poweroffs ignore upstart services

Status in “systemd” package in Ubuntu:
  Incomplete

Bug description:
  systemd-logind has a facility to detect non-ACPI power-off events
  (e.g. a power button push) and initiate a system shutdown. This
  facility works in Ubuntu - it manages to shutdown the sysvinit
  services, but upstart services do not appear to be cleanly shutdown.
  Among other things, it means that local filesystems don't get properly
  unmounted.

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