| Summary: | check for /var/lock/subsys/NetworkManager isn't valid if NM is started via systemd | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bill Nottingham <notting> | ||||
| Component: | ddclient | Assignee: | Robert Scheck <redhat-bugzilla> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 15 | CC: | ADent123, ahz001, ajschult784, bugzilla, bugzilla-redhat, jcewing, jj3666, jrowens.fedora, mail, neumann, nojunk311, paul, pcfe, Per.t.Sjoholm, redhat-bugzilla, red, rvokal, stealthcipher, theo148, thomas | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | Type: | --- | |||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
The `status` command that this uses is part of the upstart package. Isn't that exactly what we're trying to get away from, to make this work with systemd? If we do use this, we would have to add 'Requires: upstart' or 'Requires: /sbin/status' (I'm not sure if the rpm req scripts catch stuff in initscripts; seems likely). Alternatively, just switch to native systemd.service, which I'm working on now. . . . That status command comes from /etc/init.d/functions; it's not a command on the filesystem. *** Bug 722202 has been marked as a duplicate of this bug. *** This problem affects ddclient. It uses: [ ! -f /var/lock/subsys/network -a ! -f /var/lock/subsys/NetworkManager ] && exit 0 service ddclient status says it's active (exited) Success. Some backward compatibility is in order I'd say. At least until everyone has migrated to systemd properly subscribing A temporary circumvention I am using on my f15 system for ddclient is to replace the line noted above which is in /etc/init.d/ddclient with: [ ! -f /var/lock/subsys/network -a ! -f /var/lock/subsys/NetworkManager -a `systemctl status NetworkManager.service | grep -c "active (running)"` -eq "0" ] && exit 0 This in effect adds a test compatible with systemd startup of NetworkManager to the older tests. I don't feel qualified to recommend whether this is the best long-term solution for backward compatibility or whether this only works in a f15 environment. Doing this manually requires techniques that preserve the security attributes of /etc/init.d/ddclient . Here is a definition for a systemd service that you could use instead on the old init file: [Unit] Description=ddclient Client to update dynamic DNS host entries After=syslog.target network.target [Service] Type=forking User=ddclient EnvironmentFile=/etc/sysconfig/ddclient ExecStart=/usr/sbin/ddclient Comment #6 and comment #7 fixed my ddclient-3.8.0-4.fc15.noarch on Fedora 16. Thank you. It had stopped working around F15 or F16. Confirming Comment #7 worked for ddclient-3.8.0-4fc15.noarch on F16. It is an either / or between comment #6 & comment #7, both workarounds are not needed together, but #7 makes more sense with the new systemd. Will there be an update in F16? I only noticed it was not working after OpenDNS stopped filtering bad content. Luckily, I noticed it in a pop-up before my students were exposed to anything. Pretty sure others are using it for the same purpose. *** Bug 782212 has been marked as a duplicate of this bug. *** This is still an issue...running F16 This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |
Created attachment 495030 [details] Patch! Description of problem: systemd doesn't populate the /var/lock/subsys directory. Version-Release number of selected component (if applicable): ddclient-3.8.0-4.fc15