[Pkg-systemd-maintainers] Bug#742322: backtrace for systemd crash

Michael Biebl biebl at debian.org
Thu Mar 27 01:32:58 GMT 2014


Am 27.03.2014 02:29, schrieb Michael Biebl:
> Am 26.03.2014 17:39, schrieb Andreas Cadhalpun:

> The sequence of events is
> a/ make sure cups.socket is running and correctly setup
> b/ make sure cups.service is not running
> c/ make /etc/systemd/system/cups.socket.d/cupsd-listen.conf a dangling
> symlink
> d/ trigger a daemon-reload
> e/ trigger activity on the cups socket, e.g. via lpq
>    → You get the abort

OdyX, I took the liberty to CC you.
So this issue is indeed triggered by CUPS and the way it sets up the
socket configuration.

It's certainly a bug in systemd and it shouldn't crash, but maybe you
can fix cups-daemon to not trigger this issue by not creating a time
window where /etc/systemd/system/cups.socket.d/cupsd-listen.conf is a
dangling symlink





-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 884 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140327/5c653ec3/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list