Bug#750533: 'SystemdIdleExit off' stops respawns

2018-04-03 Thread Francesco Poli
On Wed, 4 Apr 2018 00:14:28 +0200 Francesco Poli wrote:

> I had to set
> 
>   SystemdIdleExit off
>   IdleExitTimeout 0
> 
> in /etc/cups/cupsd.conf in order to prevent cupsd from exiting when
> idle.

Sorry, the correct setting is just

  IdleExitTimeout 0

The other directive is no longer supported...


-- 
 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


pgpcPm77FNadl.pgp
Description: PGP signature


Bug#750533: 'SystemdIdleExit off' stops respawns

2018-04-03 Thread Francesco Poli
On Sun, 10 Aug 2014 11:19:57 -0400 Dominique Brazziel wrote:

>   No cups respawns or the attendant 
> colord messages since putting 'SystemdIdleExit off'
> in 'cupsd.conf'. I remain perplexed as to why cups kept waking up
> (on socket activation I reckon) when no jobs were printing 
> and no web interface was active.  I guess I could
> look into the cups scheduler code, but the main thing
> for me was to shut colord up.

Hi,
I am another user bitten by this bug.

I had to set

  SystemdIdleExit off
  IdleExitTimeout 0

in /etc/cups/cupsd.conf in order to prevent cupsd from exiting when
idle.

This is unfortunate, since letting cupsd exit when idle looks like a
good idea to reduce system activity until cupsd is needed again.

If colord were more quiet, I could enable cupsd IdleExitTimeout again...


Dear colord Debian package maintainer(s), is there any progress in
fixing this colord flaw?
Please let me know.

Thanks for your time and helpfulness!
Bye.

-- 
 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


pgpRz650WoCj4.pgp
Description: PGP signature


Bug#750533: 'SystemdIdleExit off' stops respawns

2014-08-10 Thread Dominique Brazziel
No cups respawns or the attendant 
colord messages since putting 'SystemdIdleExit off'
in 'cupsd.conf'. I remain perplexed as to why cups kept waking up
(on socket activation I reckon) when no jobs were printing 
and no web interface was active.  I guess I could
look into the cups scheduler code, but the main thing
for me was to shut colord up.


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