Bug 1228277
| Summary: | repeated occurrences of Overwriting existing symlink /run/systemd/generator.late/squeezeboxserver.service with real service | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | udo <udovdh> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 22 | CC: | johannbg, jsynacek, lnie, lnykryn, mitchb, msekleta, s, systemd-maint, ufa, zbyszek |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | systemd-219-19.fc22 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-07-14 15:31:54 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
udo
2015-06-04 14:14:48 UTC
This is the same bug as described in the following Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778700 And it was fixed long ago (February) upstream: http://cgit.freedesktop.org/systemd/systemd/commit/?id=4e558983 In short, the problem is that the code to generate symlinks for services that still have SYSV init scripts calls a function is_symlink() to find out whether the symlink it's about to create would interfere with an already-existing symlink. If so, it deletes the existing symlink before proceeding. However, is_symlink() returns a negative value if there's no existing file or symlink with the desired name, and the code was interpreting that negative value as true. Thus, you periodically have that error message spit out for each script in /etc/init.d/ (which obviously depends on which other packages you have installed). I've built 219-18 with this additional patch applied, and verified that it does correct the problem. Thanks. I will be awaiting this update... Where are the updates? (there might be another bug waiting to be fixed in the fc22 release of systemd) systemd-219-19.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/systemd-219-19.fc22 systemd-219-19.fc22 works Package systemd-219-19.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-219-19.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-11332/systemd-219-19.fc22 then log in and leave karma (feedback). systemd-219-19.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. |