touch-packages team mailing list archive

[god <1429938@xxxxxxxxxxxxxxxxxx>]

I think mentioning this "bug" in release notes would only confuse users:
the bug here is in the person who relied on undocumented racy behavior -
this have nothing to do with systemd or ubuntu or sshd.

-- 
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/1429938

Title:
  reboot does not return under systemd

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  If you send a shutdown or reboot command over SSH to a Trusty or
  Utopic host, the command will consistently finish successfully prior
  to the SSH connection being closed, meaning your SSH client will exit
  with a return-code of zero:

  For example:

  $ ssh root@myhost shutdown -h now
  $ echo $?
  0

  Or

  $ ssh root@myhost reboot
  $ echo $?
  0

  However, on Vivid now that the switch-over to systemd has happened,
  running the same consistently results in the abrupt closure of the SSH
  connection prior to the command finishing, meaning your SSH client
  will exit with a return-code of 255:

  $ ssh root@my_vivid_host shutdown -h now
  Connection to localhost closed by remote host.
  $ echo $?
  255

  Although in retrospect is was a bit naive for me to rely on this
  (actually quite fragile) behavior, it had at least been consistent in
  Ubuntu for some time (back to at least Raring from my personal
  experience, but likely back even farther).

  This isn't technically a systemd bug, but I still think it's something
  worth mentioning in the release notes as I bet I'm not the only person
  who built some "clever" hacks around the previous behavior :P

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