El 12/04/14 13:26, Lars Müller escribió:
That systemd is a bit fast with starting the daemons and therefore we get in the syslog lines like like the following:
PID file /run/samba/winbindd.pid not readable (yet?)
See https://bugs.freedesktop.org/show_bug.cgi?id=66641 and https://bugzilla.redhat.com/show_bug.cgi?id=911819
Systemd only is a bit fast.
If that's what you have in mind go and file a bugreport and I'm quite sure it will get closed with the reason: it's a feature and not a bug. There are much more broken and important things to work on. But feel free to offer real arguments in bugzilla.
This is a known race condition, present in almost all traditional forking daemons. systemd handles it just fine by watching the PID file and marking the service as failed if it does not show up in a certain amount of time, the message that is emitted is for developers to know this problem exist. -- Cristian "I don't know the key to success, but the key to failure is trying to please everybody." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org