On Fri, 25 May 2018 19:23:20 +0100 Brian Potkin wrote: > On Mon 21 May 2018 at 21:53:38 +0200, Francesco Poli (wintermute) wrote: > > > Dear Debian Printing Team, > > this bug report is a sort of "sequel" of #894762... [...] > > Why does cupsd fail to exit? > > What's wrong? > > > > Please help me. > > > > Thanks for your time! > > Thanks for pursuing the issue. > > It is some time since I last looked at socket activation of cupsd. My > experience wasn't the best then either. My setup: > > 1. 'cupsctl WebInterface=no LogLevel=debug2' > > From https://github.com/apple/cups/issues/4874; > > > Finally, the systemd support code explicitly disables idle > > exit when the web interface is enabled,.......
I have this too:
$ grep WebInterface /etc/cups/cupsd.conf
WebInterface No
>
> 2. cp /usr/share/doc/cups-daemon/examples/cups-socket.localhost.conf \
> /etc/systemd/system/cups.socket.d/
Same here:
$ diff -sq /usr/share/doc/cups-daemon/examples/cups-socket.localhost.conf \
/etc/systemd/system/cups.socket.d/
Files /usr/share/doc/cups-daemon/examples/cups-socket.localhost.conf and
/etc/systemd/system/cups.socket.d/cups-socket.localhost.conf are identical
>
> 3. No IdleExitTimeout in cupsd.conf. The default is 60 seconds.
I have instead:
$ grep IdleExit /etc/cups/cupsd.conf
IdleExitTimeout 60
I can try without this option set, even though I would prefer to have
the opportunity to set a different timeout, should I decide so...
>
> 4. 'systemctl daemon-reload' and 'systemctl restart cups'.
That's what I did after enabling socket activation, too.
>
> a) lpq, lpadmin and lpstat access cupsd and all lead to its becoming
> inactive after the 60 seconds timeout is over. The behaviour is
> reliable and consistent.
[...]
OK, that's more or less consistent with what I saw.
>
> b) Setting up a print queue:
>
> lpadmin -p testq -v file:/dev/null -E -m drv:///sample.drv/generic.ppd
>
> 'lp -d <file>' consistently fails to have cupsd closing the listening
> sockets.
That's what I am currently reporting as bug, yes.
[...]
> c) Using lpadmin or lpq after doing b) sees the scheduler never becoming
> inactive. The commands in c) above return the system to the state in
> a).
>
> My view is that the failure of cupsd to process a printing job and act
> on IdleExitTimeout is the important aspect. I have no explanation for
> cupsd not exiting but would be interested in whether the behaviour is
> widespread.
>
> Yves-Alexis Perez (cc'ed) has an interest in socket activation working. I
> wonder whether he observes the behaviour described in b) when printing?
> Yves-Alexis?
Fine, I am looking forward to reading additional information from
people more knowledgeable than me!
--
http://www.inventati.org/frx/
There's not a second to spare! To the laboratory!
..................................................... Francesco Poli .
GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgp_gAFZ5I340.pgp
Description: PGP signature
