Frantisek Sumsal
22e31655f3
It's pulled in by one of the udev rules (63-md-raid-arrays.rules) and it fails every time, because there's no valid email address in /etc/mdadm.conf: [ 5.778153] testsuite-64.sh[403]: mdadm: array /dev/md/mdmirror started. [ 5.819137] kernel: md/raid1:md127: not clean -- starting background reconstruction [ 5.819141] kernel: md/raid1:md127: active with 2 out of 2 mirrors [ 5.819159] kernel: md127: detected capacity change from 0 to 129024 [ 5.821950] kernel: md: resync of RAID array md127 ... [ 5.887192] mdadm[424]: mdadm: No mail address or alert command - not monitoring. [ 5.890772] systemd[1]: Starting mdmonitor.service... [ 5.891718] systemd[1]: Started mdmonitor.service. [ 5.892570] systemd[1]: mdmonitor.service: Main process exited, code=exited, status=1/FAILURE [ 5.892618] systemd[1]: mdmonitor.service: Failed with result 'exit-code'. And as we (re)assemble the MD devices multiple times, this gets quite noisy, especially since we later start hitting the service start rate limit. Fedora has the mdmonitor.service patched, so it won't start without /etc/mdadm.conf being present, but Arch uses the upstream unit which doesn't have such guard. Let's just mask the service completely, which replaces all that noise with one warning: [ 6.553583] testsuite-64.sh[294]: + udevadm wait --settle ... [ 6.580700] systemd[1]: sys-devices-virtual-block-md127.device: Failed to enqueue SYSTEMD_WANTS job, ignoring: Unit mdmonitor.service is masked.
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.