-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Aliases do not work in systemd service scripts #9618
Comments
I can’t reproduce what you had described on
|
That's good news, but this bug exists in v12.0.1.
|
12 is running 255.4 current is https://github.com/systemd/systemd-stable/releases/tag/v255.16 whereas 13 is running 257.1. Does updating to 255.16 fix your issue in LE12? If yes, and if you can identify the require patch, then it could be included in an LE12, probably not keen on updating to 255.16 in LE12 stable. |
Can confirm both of you: I've noticed too systemd aliases stopped working some time ago (in LE11 according to my quick test today) but do work again in LE13 (good news for me). |
LE11 was running 252.6. So issue looks to have been across quiet a few systemd releases |
It seems this was the fix for the issue: systemd/systemd#31816 |
I started an LE12 build for the RPi4 adding this patch. If it is successful, I will submit it in a PR. |
The patch above really works, but a dependent patch was also needed, and the affected service had to be disabled and re-enabled afterwards. (For a fresh installation, the latter is obviously not necessary.) |
Aliases in the
[Install]
section of systemd service scripts do not work on LE12.(I haven't tried another version yet, but I can say with certainty that it still worked under 9.2.)
For example:
LibreELEC.tv/packages/addons/service/docker/source/system.d/service.system.docker.service
Line 26 in 8d27a69
systemctl stop docker
doesn't work. It doesn't show any error, it just has no effect.However,
systemctl stop service.system.docker
works flawlessly.The strange part is that if I start it with
systemctl start docker
, thensystemctl stop docker
works.However, if I start it with the alias name and try to stop it with the full service name, it also does not work.
From what I've seen, the symlinks created at startup point to a good path, so there might be some deeper issue behind it.
The text was updated successfully, but these errors were encountered: