Hi! I'm not sure if the "sync" syscall is needed for arpwatch, but "fsync" is, and probably should be added to the service file. Without this exception, arpwatch fails to send notification emails: systemd-coredump[2282]: Process 2280 (sendmail) of user 77 dumped core.#012#012Stack trace of thread 2280:#012#0 0x00007f1df3d29fc7 fsync (libc.so.6 + 0xf7fc7)#012#1 0x000055f5834884d8 collect (sendmail.sendmail + 0x1f4d8)#012#2 0x000055f58347ceaa main (sendmail.sendmail + 0x13eaa)#012#3 0x00007f1df3c59b75 __libc_start_main (libc.so.6 + 0x27b75)#012#4 0x000055f58348128e _start (sendmail.sendmail + 0x1828e)
Thanks for the report! This is not the first time the syscall filter has needed to be expanded. It’s hard to get right—for example, “fsync” is called by the “sendmail” executable and appears nowhere in arpwatch’s source code. Hopefully allowing the @sync group (“Synchronizing files and memory to disk (fsync(2), msync(2), and related calls”) in the service file will be sufficient. If there are other issues, please let me know and I’ll handle them too.
FEDORA-2022-731283251a has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-731283251a
Hmm, it seems odd to me. I'm not sure @sync is enough to include fsync, at least on fedora 34 (this is the version where this bug appears). The error message comes from arpwatch-3.2-1.fc34.x86_64, where the service file already contains "@sync". Replacing "@sync" by "@fsync" seems sufficient to make sendmail work in my case. But as I understand the documentation of systemd, "@" is a notation for syscalls groups description already ? I'll make some more tests.
OK, I missed the meaning of the "~" at the beginning of the SystemCallFilter= option.
FEDORA-2022-72bdec0aa7 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-72bdec0aa7
The updated service file works for me too. Thanks!
FEDORA-2022-731283251a has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
(In reply to Fabrice Bellet from comment #4) > OK, I missed the meaning of the "~" at the beginning of the > SystemCallFilter= option. Exactly right: removing @sync from this line stops excluding it, therefore allows it. I’ll be backporting this fix to stable releases, too.
FEDORA-2022-61fe8850d0 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-61fe8850d0
FEDORA-EPEL-2022-bb65b22de7 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-bb65b22de7
FEDORA-2022-72bdec0aa7 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-72bdec0aa7` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-72bdec0aa7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-61fe8850d0 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-61fe8850d0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-61fe8850d0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-bb65b22de7 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-bb65b22de7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-61fe8850d0 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-72bdec0aa7 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2022-bb65b22de7 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.