Le lundi, 17 mars 2014, 11.11:12 Michael Stapelberg a écrit :
> Didier 'OdyX' Raboud <o...@debian.org> writes:
> > Well. Although that's what the manpage says, I think it's quite
> > strong for systemd to refuse to finish the socket reloading because
> > of that unclarity, and I tend to think that doing so is still a
> > bug.
> If you think so, please submit a ticket upstream.

Don't you think that the inconsistency pointed by Yves-Alexis in 
<20140315201925.gd10...@scapa.corsac.net> is a bug?

He had a /etc/systemd/system/cups.socket.d/local.conf with:
[Socket]
ListenStream=
ListenStream=/var/run/cups/cups.sock
ListenDatagram=

which worked fine with cups 1.7.1-7, but not with -8, where the -8 
dropped two ListenStream= stanzas (but kept one) in 
/lib/systemd/system/cups.socket . In -7 cups.socket could be reloaded, 
not anymore in -8. How is that systemd working according to its manpage?

Cheers,
OdyX


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to