ad23ff13de
Since we restart systemd-udevd here a couple of times, we might hit the rate limit in later tests: [ 26.028355] testsuite-17.sh[2074]: + udevadm control -e [ 26.028355] testsuite-17.sh[2074]: + udevadm control -l emerg [ 26.126160] systemd[1]: systemd-udevd.service: Start request repeated too quickly. [ 26.126213] systemd[1]: systemd-udevd.service: Failed with result 'start-limit-hit'. [ 26.140310] systemd[1]: Failed to start systemd-udevd.service. [ 26.140897] systemd[1]: systemd-udevd-control.socket: Failed with result 'service-start-limit-hit'. [ 26.141286] systemd[1]: systemd-udevd-kernel.socket: Failed with result 'service-start-limit-hit'. [ 26.142225] testsuite-17.sh[2074]: + udevadm control -l alert [ 26.149206] udevadm[2088]: Failed to send request to set log level: No such file or directory Follow-up to: 6ef512c0bb
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.