Description of problem: https://fedoraproject.org/wiki/Features/SysVtoSystemd Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 512859 [details] New /etc/sysconfig/exim
Created attachment 512860 [details] Exim Cert generator
Created attachment 512862 [details] Native systemd service file exim
Created attachment 513244 [details] Native systemd service file clamd.exim
Created attachment 513245 [details] Native systemd service file clamd.exim socket
https://fedoraproject.org/wiki/Packaging:Guidelines:Systemd https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd https://fedoraproject.org/wiki/Packaging:Tmpfiles.d
Created attachment 513248 [details] Spec file patch I think I got this one right but you might consider adding a tmpfile for clamd.exim
Created attachment 546918 [details] Native systemd service file for exim Updated to reflect the current status in systemd Dropped /etc/sysconfig file since it's Red Hat specific and users really should copy the unit file to /etc/systemd/system and add/edit any option to it there..
Created attachment 546920 [details] Native systemd service file for clamd.exim Updated to reflect the current state of systemd drop /etc/sysconfig environment file
Ping
Hi Jóhann, thanks for your help. I became exim co-maintainer. I will give it deeper look and testing, ETA probably one week.
Created attachment 550994 [details] Native systemd service file for clamd exim Apparently the socket unit should not be created...
It passed my simple testing and I pushed it with some mods. I think there is a room for improvement regarding the clamav support and we could unify this across other clamav enabled packages. I would like to hear opinions from other maintainers, thus some BZ tracker would be probably helpful for this.