On Wednesday 28 of December 2011 14:54EN, Cristian Rodríguez wrote:
After been working for years in distro packaging, this is exactly what we need, conforming to one scheme.
This might work if we developed all projects included in the distribution ourselves. But we don't. There are projects that are not written primarily for Linux and there are projects that are not developed with Linux in mind at all. These are not going to conform to "We decided daemons are bad, please rewrite your daemons not to be daemons."
Systemd units can even be checked with rpmlint to verify if they really do what the say or what the packager wanted to do try to do that with shell scripts.
I don't understand. If a systemd unit doesn't do what it says, it's a bug in systemd. The same for a shell script and bash. As for checking whether the unit file says what its author wanted it to say, I seriously doubt it is possible.
The shell is not a debugger is it ? I am missing something ?
If I want to know what is going on in an init script, I just add "-x" to the interpreter specification. I can add diagnostic commands (print a value, check whether a process is running or whether a file exists...) anywhere inside a script. I don't want to trade this convenience for few seconds of boot time. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org