Timeline for Systemd service: Restart unit not found unless stopped first
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 13, 2020 at 13:54 | vote | accept | Jacob | ||
| Feb 13, 2020 at 13:53 | answer | added | Jacob | timeline score: 0 | |
| Jul 9, 2019 at 17:53 | comment | added | rogerdpack | journalctl say anything about it? | |
| May 22, 2018 at 17:09 | history | edited | filbranden | CC BY-SA 4.0 |
format command output
|
| May 22, 2018 at 6:47 | comment | added | Jacob | @MarkStosberg same behavior if calling with merlind instead of merlind.service unfortunately. | |
| May 21, 2018 at 17:37 | comment | added | Mark Stosberg |
Just guessing, what happens if you use restart merlind instead of restart merlind.service
|
|
| May 21, 2018 at 12:48 | history | edited | Jacob | CC BY-SA 4.0 |
added 44 characters in body
|
| May 21, 2018 at 12:47 | comment | added | Jacob | @Patrick sorry! Actually the .service file is at /usr/lib/systemd/system/merlind.service and symlinked at: /etc/systemd/system/multi-user.target.wants. Updated the question. | |
| May 21, 2018 at 12:33 | comment | added | phemmer |
How did the unit file get into a .wants directory? That's not how systemd unit files are supposed to work. It should be in /etc/systemd/system and symlinked into the .wants directory. And better yet would be to use the tools such as systemctl enable.
|
|
| May 21, 2018 at 12:23 | review | First posts | |||
| May 21, 2018 at 12:24 | |||||
| May 21, 2018 at 12:19 | history | asked | Jacob | CC BY-SA 4.0 |