![](https://seccdn.libravatar.org/avatar/9435667f7160374bc34a8600b686aecd.jpg?s=120&d=mm&r=g)
On Fri, May 31, 2024 at 3:55 AM Felix Miata <mrmazda@earthlink.net> wrote:
Carlos E. R. composed on 2024-05-30 23:25 (UTC+0200):
Felix Miata wrote:
Andrei Borzenkov composed on 2024-05-30 20:19 (UTC+0300):
Felix Miata wrote:
> I tried changing WantedBy from default to multi-user, but it didn't help.
Explain step by step what you did.
# systemctl edit /etc/systemd/system/issue-generator.service copy [Install] WantedBy=multi-user.target from lower part of file to ~line 3 s/graphical/multi-user/ save/exit # Reboot
I would expect that a user who constantly talks about managing dozens if not hundreds systems knows that to apply [Install] section one needs to enable unit.
Felix Miata composed on 2024-05-29 18:10 (UTC-0400):
# systemctl list-unit-files | grep issue issue-generator.path enabled enabled issue-add-ssh-keys.service disabled disabled issue-generator.service enabled enabled
Looks enabled to me, whether on an installation where it works, or not.
That is a common misunderstanding. The "enable(d)" as used in systemd has nothing to do with the colloquial usage of the English word "enable(d)". "enable" in systemd means exactly that - create links defined by [Install] section. "enabled" in systemd means exactly that - links defined by [Install] section exist. Now you hit a case when some links are present and some links are missing. This unit is neither fully enabled nor completely disabled. systemctl apparently shows "enabled" if any link is present. Showing "disabled" in this case would be just as wrong. Maybe it should show "partially enabled" (or similar) to avoid confusion. That is something you need to bring up with upstream.
works if I run
systemctl start issue-generator.service
on any where it doesn't.
He is saying that if you change the [install] section , you have to do a systemctl enable to activate that change. At least that is what I understand, it is news to me.
Are you two somehow suggesting that if a service override is created, it isn't implemented until the service is first disabled, then enabled;
Quoting "man systemd.unit" Unit files may include an [Install] section, which carries installation information for the unit. This section is not interpreted by systemd(1) during runtime; it is used by the enable and disable commands of the systemctl(1) You do not need to run "systemctl disable" if you just add an additional link. You obviously need to do it if you replace one link with another - and you need to do it *before* changing the [Install] section, otherwise "systemctl disable" will not know what old link to remove.
or issue-generator uninstalled, then installed?
In this case installing the issue-generator would run "systemctl enable".