Bug#750498: cups: server keeps timing out after 30secs idling with no way to change that
Control: clone -1 -2 -3
Control: reassign -2 src:cups 1.7.2-3
Control: retitle -2 src:cups: install README.Debian also in cups-daemon
Control: retitle -1 cups: web interface activity should prevent timeout
Control: reassign -3 colord 1.0.6-1
Control: retitle -3 colord: should cope more quietly with cups respawns
Hi dear Nemo Inis, and thanks for reporting a bug.
Le mardi, 3 juin 2014, 14.41:01 Nemo Inis a écrit :
> Ever since cups 1.7.2-2, which contains a patch for bug #742666, and
> my switch to systemd, the cups server exits after 30 seconds idling
> without a configuration option to prevent that.
That's not entirely accurate: both the Debian NEWS file [0] and the
README.Debian [1] (but that one is installed in a bizarre place,
arguably) contain instructions on how to disable this behaviour, quoting
the first:
> - Automatic exit when idle
> When operated under systemd as init, the CUPS daemon will be
> launched when needed (through socket activation) and exit itself
> after being idle for some time (30 seconds by default). The delay
> before exiting on idle can be configured using 'IdleExitTimeout' in
> /etc/cups/cupsd.conf. CUPS can also be left running continuously
> using 'SystemdIdleExit off' in that same file.
[0] /usr/share/doc/cups-daemon/NEWS.Debian.gz
[1] /usr/share/doc/libcups2/README.Debian.gz
I'm hereby cloning this bug against src:cups to track the wrong place of
this README.Debian file.
> - when I'm using the cups web interface at localhost:631, if I wait
> more than 30 seconds before clicking on anything, my browser reports
> "unable to connect" and I've lost whatever work I was in the middle
> of (for example adding a printer, etc...);
Indeed, that's problematic, retitling this very bug to keep track of
that problem.
> - cups starts/stops throughout the day, and every time, it triggers
> colord (which I also run), which loads all my profiles, etc... and
> fills my syslog telling me so;
Well, that's a colord bug I would argue, reassigning a copy of this bug
there.
> - since I'm running a desktop machine, I'd rather not have settings
> meant for laptops forced down on me; I'd like the option to run cups
> permanently without timeout as it did before.
This is possible and documented (although partially).
Cheers,
OdyX
Reply to: