On Sat, Jan 17, 2015 at 12:08:17AM +0100, Jan Engelhardt wrote:
On Friday 2015-01-16 23:50, Michal Kubecek wrote:
About month ago, I installed 13.1 on an e-mail server with amavisd and additional package named amavisd-milter. In amavisd-new package, there is both a systemd unit file [...] The systemd unit file kind of tries to do the same but it's broken somehow so that amavisd-milter is started but once "rcamavis start" finishes, it's not running any more (without any clue in the log). I have no idea why and I have no idea how to debug it
There is no excuse for a daemon to exit with non-zero status and not tell you, through stderr, syslog or a custom logfile (e.g. /var/log/squid/cache.log) why it did so.
All I was able to find out indicated that it didn't really exit but rather was killed. By whom and why... no idea.
An incentive to actually learn working with systemd, and how to debug program startup issues. It will be very much valued in the coming years, as there will be more and more units (outside openSUSE too)
Yes, for completeness, that would be option (d). What I think about it should be clear from the fact that I didn't even mention it. There are too many topics I find much more interesting and much more useful (for me) to learn than this. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org