Carlos E. R. wrote:
On 2016-10-03 14:32, Per Jessen wrote:
Carlos E. R. wrote:
I don't have (big) problems with systemd. I think. In general, I'm happy. Well, perhaps that if there is a problem I can not edit an script and solve it. I have to wait for the devs to solve and distribute it. Ie, little problems are now more difficult to hack or solve for the administrator.
Can you come up with an example of that, Carlos? I think you're wrong. systemd has better options than editing the script - a service unit is easily overridden etc.
Yes, sure.
I had problems with umounting some filesystem and systemd instantly remounting it on my back. Or the other way round.
One that is hard to reproduce: during halt, network was disconnected, then the process decided to umount an nfs mount. Obviously, it could not, and got stuck. On the end, I had to hit the power button.
I'm sure that is/was a genuine problem, but allow me to count it as an exception to prove the rule. I think it is very far from your example to your general suggestion that "... that if there is a problem I can not edit an script and solve it. I have to wait for the devs to solve and distribute it".
It's most likely in the man page(s), but I agree they can be a bit long and not always easy to grok.
What you need to look at are the After, Requires, and Wants directives.
Yes, I know, but I'm talking about a FAQ that I can read and point people to. I do not want to study a long documentation in order to figure out what to do.
Yes, I suppose there's room for some of that. Speaking for myself, I find it is acceptable to work with the man-page, existing examples and google. -- Per Jessen, Zürich (15.8°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org