Hi Michael, Le samedi, 15 mars 2014, 19.04:08 Michael Stapelberg a écrit : > Didier 'OdyX' Raboud <o...@debian.org> writes: > > Le jeudi, 13 mars 2014, 19.13:28 Michael Biebl a écrit : > >> Apparently, "unsetting" ListenDatagram= makes systemd believe, that > >> there is no valid Listen directive anymore for the socket, even > >> though Corsac has specified > >> ListenStream=/var/run/cups/cups.sock > >> > >> The error message I'm getting is > >> > >> Mär 13 19:08:18 pluto systemd[1]: cups.socket lacks Listen setting. > >> Refusing. > >> > >> Sounds like a genuine bug in systemd. > > Actually, I don’t think it’s a bug. Quotang systemd.socket(5): > > If the empty string is assigned to any of these options, the list > of addresses to listen on is reset, all prior uses of any of these > options will have no effect. > > So, this is working as intended (specifying ListenDatagram= > effectively unsets Listen*), and the correct way to specify what > Yves-Alexis wanted to do is just: > > [Socket] > ListenStream= > ListenStream=/var/run/cups/cups.sock
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. Cheers, OdyX -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
