Public bug reported:
Accidentally ran `/sbin/restart` (symlink to `/sbin/initctl`) without
arguments as my regular user, and unity was restarted (possibly amongst
other things). I would expect it to exit immediately with an error code,
given its usage and manpage (initctl (8)).
Easy to reproduce.
~$ dpkg -S `which restart`
upstart: /sbin/restart
~$ restart --help
Usage: restart [OPTION]... JOB [KEY=VALUE]...
Restart job.
...
~$ restart
unity7 start/killed, process 12622
== Environment ==
~$ lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04
~$ apt-cache policy upstart
upstart:
Installed: 1.13.2-0ubuntu21
Candidate: 1.13.2-0ubuntu21.1
Version table:
1.13.2-0ubuntu21.1 500
500 http://ca.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
*** 1.13.2-0ubuntu21 500
500 http://ca.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status
** Affects: upstart (Ubuntu)
Importance: Undecided
Status: New
** Tags: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1622025
Title:
running /sbin/restart with no arguments restarts services
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1622025/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
