Bug#758284: cups-daemon: IdleExitTimeout aappears to be unreliable

[Brian Potkin <claremont102@gmail.com>]

retitle 758284 cups-daemon: IdleExitTimeout appears to be unreliable
thanks



Retitled because IdleExitTimeout behaves exactly as intended.


On Mon 15 Sep 2014 at 23:47:49 +0100, Brian Potkin wrote:

> Again we see the 30 second delay at the lines marked **. However, the
> line to concentrate on is the one immediately prior to these two.
> 
>     d [15/Sep/2014:22:31:38 +0100] select_timeout(0): 30 seconds to write dirty config/state files
> 
> I have no idea what it means and do not know whether the 30 seconds is
> fixed within cups or dynamically generated. I also do not understand
> coding in C. But I am ace at fiddling. :)

The time to write dirty config/state files is generated from

  DirtyCleanTime = time(NULL) + DirtyCleanInterval

Putting

  DirtyCleanInterval 0

in cupsd.conf sees cupsd becoming idle after a time t, where

  t = (time to print) + IdleExitTimeout

> We'll change
> 
> 		timeout >= IdleExitTimeout
> 
> to
> 
> 		timeout <= IdleExitTimeout
> 
> in scheduler/main.c, refresh the patch and rebuild cups.

The significance of 'timeout >= IdleExitTimeout' still escapes me. I'm
now very unsure about what origin the bug has.

Regards,

Brian.