Zbigniew Jędrzejewski-Szmek
0b291130e8
If we failed to open the watchdog device for any reason, we'd only log at debug level. This seems iffy: if the user configured a timeout for the watchdog, we should report when we can't set it up. ENOENT is still logged at debug level only, since it's somewhat expected to have a watchdog timeout set up, even for systems which don't have a watchdog, or the device might appear later. If the device doesn't support WDIOC_GETSUPPORT, still log that we opened a device. No change in behaviour, except for the log level threshold. As a side effect, the reason why we failed to open the device is now stored in watchdog_fd (previously it was -1 always), but this isn't used for anything.
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS