| 2014-12-21 08:53:33 |
John Hall |
bug |
|
|
added bug |
| 2014-12-21 08:54:16 |
John Hall |
description |
# man init
Brings up the documentation for systemd but systemd is not being used as init.
This confuses users about which system is being used as "init", and how to manage services on the system.
You can see that this is still upstart with:
# sudo readlink /sbin/init
or
# ls -l /sbin/init
# man init
Should still result in the same thing as
# man upstart
Until systemd is used for init.
This effects 14.10 as of Dec 21, 2012
The solution would be for systemd to register it's init man page as, for example, systemd-init .
Users that have installed systemd as init will no what they are doing. Ubuntu should document the default int. |
# man init
Brings up the documentation for systemd but systemd is not being used as init.
This confuses users about which system is being used as "init", and how to manage services on the system.
You can see that this is still upstart with:
# sudo readlink /sbin/init
or
# ls -l /sbin/init
# man init
Should still result in the same thing as
# man upstart
Until systemd is used for init.
This effects 14.10 as of Dec 21, 2014
The solution would be for systemd to register it's init man page as, for example, systemd-init .
Users that have installed systemd as init will no what they are doing. Ubuntu should document the default int. |
|
| 2014-12-21 08:56:10 |
John Hall |
description |
# man init
Brings up the documentation for systemd but systemd is not being used as init.
This confuses users about which system is being used as "init", and how to manage services on the system.
You can see that this is still upstart with:
# sudo readlink /sbin/init
or
# ls -l /sbin/init
# man init
Should still result in the same thing as
# man upstart
Until systemd is used for init.
This effects 14.10 as of Dec 21, 2014
The solution would be for systemd to register it's init man page as, for example, systemd-init .
Users that have installed systemd as init will no what they are doing. Ubuntu should document the default int. |
# man init
Brings up the documentation for systemd but systemd is not being used as init.
This confuses users about which system is being used as "init", and how to manage services on the system.
You can see that this is still upstart with:
# sudo readlink /sbin/init
or
# ls -l /sbin/init
# man init
Should still result in the same thing as
# man upstart
Until systemd is used for init.
This effects 14.10 as of Dec 21, 2014
One solution would be to rename this systemd man page to, for example, "systemd-init"
Users that have installed systemd as init will know what they are doing and will be able to find that page.
Ubuntu should document the default init in manpages. |
|
| 2014-12-21 11:07:32 |
Gunnar Hjalmarsson |
affects |
ubuntu-docs (Ubuntu) |
systemd (Ubuntu) |
|
| 2015-01-06 08:51:13 |
Martin Pitt |
systemd (Ubuntu): status |
New |
Triaged |
|
| 2015-01-06 08:51:15 |
Martin Pitt |
systemd (Ubuntu): importance |
Undecided |
Low |
|
| 2015-01-07 20:26:05 |
Brian Murray |
tags |
|
utopic vivid |
|
| 2015-03-10 12:02:16 |
Martin Pitt |
systemd (Ubuntu): status |
Triaged |
Invalid |
|
