Bug#771172: systemd-sysv-generator does not generate

Salvo Tomaselli tiposchi at tiscali.it
Thu Nov 27 20:06:11 GMT 2014


In data giovedì 27 novembre 2014 15:40:01, Michael Biebl ha scritto:
> Am 27.11.2014 um 12:01 schrieb Salvo Tomaselli:
> > Package: systemd
> > Version: 215-6
> > Severity: critical
> > Justification: breaks unrelated software
> > 
> > Dear Maintainer,
> > I am not providing the additional information that reportbug wants to
> > provide because if I do, the mail will be rejected as spam by bogus
> > filters.
> > 
> > Dear Maintainer,
> > 
> > somehow, after the last upgrade (which included dbus, console-setup,
> > libpolkit-backend, schroot) I was unable to start postfix.
> 
> Was postfix part of the upgrade?
No it wasn't.

> If you remove an init script and "systemctl daemon-reload" is run,
> systemd will re-run the sysv-generator and the generated unit is removed
> as well.
> Since during the upgrade "systemctl daemon-reload" has been triggered
> most likely by e.g. dbus's maintainerscript, it's expected that the
> generated unit for postfix is removed and the error message you get above.
> 
> It doesn't necessarily mean that the postfix process is stopped, unless
> the postfix package was part of the upgrade and the service stopped in
> prerm.
It was not, possibly I had stopped it after I got the error, to try to 
convince dpkg to finish configuring.
I did a few attempts before managing to convince it.

> Running "systemctl daemon-reload" is sufficient to run the generator.
> You don't need to run it by hand and copying the files around.
I wasn't even aware there was such a thing. <rant>I thought systemd was 
supposed to be a drop in replacement. Which clearly is not.</rant>
So I am rather clueless on systemd's usage.

> If you install an init script, you'll need to run "systemctl
> daemon-reload" for systemd to pick it up. The package maintainer scripts
> do that automatically.
This breaks compatibility tho, and also, i tried to run the script manually as 
a script (without service) but it was redirecting to systemd and insisted in 
failing to start. Perhaps the magic wrapper or whatever can be improved to 
detect this case?

It doesn't make much sense when I try to run a shell script and I get a 
failure because apparently the file I'm running doesn't exist. (except if you 
know how systemd works, then I guess it makes sense).

> That's also true for native services fwiw.
Oh this explains why I had to reboot after creating a .service file!

Thanks for your help :-)

-- 
Salvo Tomaselli

"Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di 
senso, ragione ed intelletto intendesse che noi ne facessimo a meno."
                -- Galileo Galilei

                http://ltworf.github.io/ltworf/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20141127/223a4804/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list