A breaking change was introduced in v4.0.0: https://github.com/ddclient/ddclient/pull/789 ddclient now looks for ddclient.conf in ${sysconfdir}/ddclient/ by default instead of ${sysconfdir}/, but the rpm package still install ddclient.conf to ${sysconfdir}/. ddclient will fail if the configuration file is missing. Reproducible: Always Steps to Reproduce: 1. Run `sudo -u ddclient ddclient -daemon=0 -debug -verbose -noquiet` Actual Results: outputs: ``` WARNING: [file /etc/ddclient/ddclient.conf]> cannot open file: No such file or directory ``` Expected Results: ddclient should run without errors
I wonder if perhaps we should instead rebuild ddclient with sysconfdir set back to /etc, mainly for those who already have their ddclient.conf in /etc?
i am using ddclient-3.9.1-8.el9.noarch.rpm on Alma 9. I see a conflict between entries in /etc/ddclient.conf and /etc/sysconfig/ddclient. Both have a daemon=300. But which file takes precedence? We modify /etc/ddclient.conf via our install scripts. I previously had no idea there was an /etc/sysconfig/ddlient file. Seems a conflict to be setting the same parameter in two places.
Sorry, I thought I was entering a new issue. Please delete if possible.
FEDORA-2025-0a0a04ceb5 (ddclient-4.0.0-3.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-0a0a04ceb5
FEDORA-2025-0a0a04ceb5 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-0a0a04ceb5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-0a0a04ceb5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
*** Bug 2372895 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora Linux 42 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '42'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 42 is 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.