...indicates that the initscript was in fact executed, but did fail (even though it's strange that "Job is already running" produces a fail. On my system (14.04) it does not produce an error when I run "invoke-rc.d systemd-logind start" as root, while it is already running).
Btw. I was also surprised at not being able to edit comments. I guess it's because the posts end up in a mailing list.
e.g. http://<email address hidden>/msg4504011.html
@wlraider70
This seems not to be directly related. Same as #16 by @Michael Heuberger.
The issue of this thread is about this message:
invoke-rc.d: unknown initscript, /etc/init. d/systemd- logind.
It can not find the initscript and thus is not able to execute it.
Whereas your message...
invoke-rc.d: initscript systemd-logind, action "start" failed.
...indicates that the initscript was in fact executed, but did fail (even though it's strange that "Job is already running" produces a fail. On my system (14.04) it does not produce an error when I run "invoke-rc.d systemd-logind start" as root, while it is already running).
Maybe this thread helps (specifically #4):
"invoke-rc.d: initscript systemd-logind, action "start" failed." /bugs.launchpad .net/ubuntu/ +source/ systemd/ +bug/1320563
https:/
Btw. I was also surprised at not being able to edit comments. I guess it's because the posts end up in a mailing list. /msg4504011. html
e.g. http://<email address hidden>