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. One can prepend strace into the ExecStart= line, or `screen -d -m gdb /usr/bin/foo --args whatever`. Basically the same you would do if the program exited silently under initscript context.
When I raised my concern that once sysvinit would be dropped, it would be only matter of time before a check is added pushing maintainers to replace init scripts by systemd unit file, the answer was like "Why would we do that? The init scripts will still work."
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) ;-) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org