| Summary: | DDClient won't start with systemd | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Arthur Dent <ADent123> |
| Component: | ddclient | Assignee: | Robert Scheck <redhat-bugzilla> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | redhat-bugzilla, thomas |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-07-18 21:39:56 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Whoops... I'm really sorry. I forgot to check for existing bugs (I have no idea why I forgot to do so on this occasion). This has clearly been reported in bug 710673 which is itself a duplicate of Bug 699889. Moreover, a native systemd unit file is being worked on in bug 718756. Sorry for the noise. *** This bug has been marked as a duplicate of bug 699889 *** |
Description of problem: OK - I admit, I still don't really understand systemd and I may have got this wrong... But today I discovered that my DynDNS account had expired (meaning I now have to fork out for a paid account) because I assumed DDClient was working when in fact it was not. Checking the systemd status it showed the service as "active (exited)" whatever that means. # systemctl status ddclient.service ddclient.service - LSB: Client to update dynamic DNS host entries Loaded: loaded (/etc/rc.d/init.d/ddclient) Active: active (exited) since Sat, 02 Jul 2011 09:48:39 +0100; 1 weeks and 5 days ago CGroup: name=systemd:/system/ddclient.service Looking at the /etc/init.d/ddclient script I noticed in the "start" stanza the following: "start() { # Check that networking is up. [ ! -f /var/lock/subsys/network -a ! -f /var/lock/subsys/NetworkManager ] && exit 0 " I don't speak fluent bash, but it looks to me as if it's looking for either of those files in /var/lock/subsys. On my Fedora 15 System I have only /var/lock/subsys/netfs and nfs (beginning with N). Is my system at fault or does the init.d script need to be updated to reflect systemd control? Thanks in advance Mark Version-Release number of selected component (if applicable): ddclient-3.8.0-4.fc15.noarch