Your message dated Wed, 04 Apr 2018 21:06:26 +0200
with message-id <>
and subject line Re: Bug#894762: cups-daemon: with IdleExitTimeout 60, 
correctly exits when idle for 60 s, but immediately respawns [regression]
has caused the Debian Bug report #894762,
regarding cups-daemon: with IdleExitTimeout 60, correctly exits when idle for 
60 s, but immediately respawns [regression]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
Package: cups-daemon
Version: 2.2.7-1
Severity: normal

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

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (800, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cups-daemon depends on:
ii  adduser           3.117
ii  bc                1.07.1-2
ii  dpkg    
ii  libavahi-client3  0.7-3.1
ii  libavahi-common3  0.7-3.1
ii  libc6             2.27-2
ii  libcups2          2.2.7-1
ii  libcupsmime1      2.2.7-1
ii  libdbus-1-3       1.12.6-2
ii  libgssapi-krb5-2  1.16-2
ii  libpam0g          1.1.8-3.7
ii  libpaper1         1.1.24+nmu5
ii  libsystemd0       238-3
ii  lsb-base          9.20170808
ii  procps            2:3.3.12-4
ii  ssl-cert          1.0.39

Versions of packages cups-daemon recommends:
pn  avahi-daemon  <none>
ii  colord        1.3.3-2
ii  cups-browsed  1.20.1-1+b1

Versions of packages cups-daemon suggests:
ii  cups                             2.2.7-1
ii  cups-bsd                         2.2.7-1
ii  cups-client                      2.2.7-1
ii  cups-common                      2.2.7-1
ii  cups-filters [foomatic-filters]  1.20.1-1+b1
pn  cups-pdf                         <none>
ii  cups-ppdc                        2.2.7-1
ii  cups-server-common               2.2.7-1
ii  foomatic-db                      20180210-1
ii  ghostscript                      9.22~dfsg-2
pn  hplip                            <none>
ii  poppler-utils                    0.62.0-2
ii  printer-driver-gutenprint        5.2.13-2
ii  printer-driver-hpcups            3.17.10+repack0-5
pn  smbclient                        <none>
ii  udev                             238-3

-- no debconf information

--- End Message ---
--- Begin Message ---
Le mercredi, 4 avril 2018, 12.59:07 h CEST Brian Potkin a écrit :
> This means cups.service has acquired an extra directive
> "Restart=always".

Indeed. That's to make sure CUPS is restarted even when exiting normally (such 
as configuration changes.

You can configure this by creating a /etc/systemd/system/cups.service with

As that's an upstream decision, I'm hereby closing this bugreport. Please 
reopen if you think a Debian-specific patch could make sense.


--- End Message ---

Reply via email to