Carlos E. R. said the following on 12/16/2011 06:24 PM:
On Friday, 2011-12-16 at 18:48 -0300, Cristian Rodríguez wrote:
On 16/12/11 18:16, James Knott wrote:
Systemd is clearly not ready for prime time.
The bug was not in systemd but in the postfix package, which update has been released today, blaming the wrong component here.
Postfix has worked for years, and only fails when a new ingredient is added to the recipe: systemd. Ergo, the culprit is systemd, even if the solution involves changing another component.
Even more when several independent components fail, and the common ingredient in all cases is systemd.
Yes/no/maybe. I recall reading somewhere that the interface between SystemD and the old Nit scripts was limited. Some of those script had more that stop, start, status, and that tended to mess things up. I'll see if I can find the page in my browser history; it was something about writing or converting scripts to use with SystemD ... Well there's http://www.freedesktop.org/wiki/Software/systemd/Incompatibilities which says
Additional verbs for init scripts are not supported. If your init script traditionally supported additional verbs for your init script simply move them to an auxiliary script. Additional parameters to the standard verbs (i.e. to "start", "stop" and "status") are not supported. This was an extension of SysV that never was standardized officially, and is not supported in systemd.
but that wasn't what I recall ... maybe something more. I recall reading that systemd takes some of the stuff that's in the script headers very literally even if its wrong. The stuff like
# Provides: postfix # Required-Start: $network # Required-Stop: $network # Should-Start: $named mysqld postgresql ldap saslauthd # Should-Stop: $named mysqld postgresql ldap saslauthd
Personally I think all that sysinit compatibility is a kludge and you should write a proper Unit file (target & service) for Postfix. Something simple like http://en.gentoo-wiki.com/wiki/Systemd#Postfix -- This is a general discussion intended for use only by qualified professionals. It should not be taken or used as a recommendation for any specific business, application, or environment. Said recommendations can be made only in a specific context and will be made only for a professional fee. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org