On Wed 04 Apr 2018 at 00:46:55 +0200, Francesco Poli (wintermute) wrote: > Dear Debian Printing Team, > I noticed a weird misbehavior of cupsd, which seems to be a regression. > > I had configured /etc/cups/cupsd.conf with the directive > > IdleExitTimeout 60 > > in order to let cupsd exit when idle for 60 s: the feature (with > systemd socket activation) was working correctly. > > However, after upgrading > > [UPGRADE] cups:amd64 2.2.6-5 -> 2.2.7-1 > [UPGRADE] cups-bsd:amd64 2.2.6-5 -> 2.2.7-1 > [UPGRADE] cups-client:amd64 2.2.6-5 -> 2.2.7-1 > [UPGRADE] cups-common:amd64 2.2.6-5 -> 2.2.7-1 > [UPGRADE] cups-core-drivers:amd64 2.2.6-5 -> 2.2.7-1 > [UPGRADE] cups-daemon:amd64 2.2.6-5 -> 2.2.7-1 > [UPGRADE] cups-ipp-utils:amd64 2.2.6-5 -> 2.2.7-1 > [UPGRADE] cups-ppdc:amd64 2.2.6-5 -> 2.2.7-1 > [UPGRADE] cups-server-common:amd64 2.2.6-5 -> 2.2.7-1 > > cupsd exits after 60 s of inactivity, but is mysteriously respawned > immediately. > The net result of all this is that cupsd gets restarted once every > 60 s, which is annoying (especially because of colord verbosity, > see bug #750533). > > The fact is that I cannot understand why cupsd gets respawned, > when nobody is attempting to print anything or to use the web > interface. > And I am pretty sure that cups-daemon/2.2.6-5 did not exhibit > this misbehavior. > > Could you please investigate this issue? > > Thanks for your time and helpfulness!
Thank you for you report, Francesco. The only thing I can think of (I haven't tested) is upstream Issue #5263 mentioned in the Debian changelog. This means cups.service has acquired an extra directive "Restart=always". Regards, Brian.