Open andypl78 opened 8 years ago
Systemd socket activation seems like a good idea in theory- though I'm afraid it has some problems (aside from being unfamiliar to users) and so we may have done better never to have adopted it. Ripping it out, however, would be painful as users of certain platforms have come to expect certain behaviour- at least upgrade path would need to be addressed. I see no particular reason to be using the init script on Debian Jessie (unless systemd has been uninstalled).
Startup steps for platforms using systemd socket activation are here: https://rspamd.com/doc/quickstart.html#running-rspamd
# Install rspamd + rmilter packages from rspamd.com
for i in rmilter.socket rspamd.socket; do systemctl enable $i; systemctl start $i; done # Enable sockets on startup & start listening
rspamc < /dev/null # (optional) force rspamd to start
socat STDIN UNIX-CONNECT:/var/run/rmilter/rmilter.sock < /dev/null # (optional) force rmilter to start
Edit: see also https://github.com/vstakhov/rspamd-build-scripts
My solution is based on the ports that are used in multi server configuration. Therefore, I turned off the socket and removed the configuration of the system. With this solution we can create a main server rmilter+rspamd+ redis and plug in multiple servers postfix
Please change startup services for rspamd and rmilter to use for only IP configuration. In my configuration, I do not use the socket and services at the IP would not correctly run on Debian Jessie
https://github.com/andypl78/rmilter.git https://github.com/andypl78/rspamd.git
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.