El 14/04/13 14:58, Stefan Seyfried escribió:
(maybe we should move the discussion to factory? anyway, I'd think we better let it die soon)
Am 14.04.2013 19:18, schrieb Cristian Rodríguez:
El 14/04/13 06:09, Stefan Seyfried escribió:
Anyway -- debugging this with SysV init was a breeze compared with systemd.
No Stefan, it wasn't a breeze, it was a hack that required debugging shell scripts.
Which is a breeze compared with debugging systemd. As systemd is PID 1, a single mistyped debug-printf in the code will panic my system. If I mistype something in an init script, I boot with init=/bin/bash and fix the typo.
Compared to "#!/bin/bash -x" in the old-style init scripts, it is much harder to debug systemd correctly.
Myth 25 --> http://0pointer.de/blog/projects/the-biggest-myths.html
I'll do that once I gained some confidence that the working syslog is not an accident (means: it survives a few reboots).
If you applied the unit I sent you, ensure things are cool by issuing systemctl reenable syslog-ng.service too (missed that bit in the prev mail) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org