Bug#894762: cups-daemon: with IdleExitTimeout 60, correctly exits when idle for 60 s, but immediately respawns [regression]
forcemerge 894762 898745 thanks On Sun 20 May 2018 at 12:01:04 +0200, Francesco Poli wrote: > On Fri, 18 May 2018 18:58:21 +0100 Brian Potkin wrote: > > > On Wed 04 Apr 2018 at 22:29:07 +0200, Francesco Poli wrote: > > > > > Looking forward to hearing back from you. > > > Thanks for your time and patience! > > > > Not too long a wait, I hope, Francesco. > > > > Please try the technique in #898745 > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898745 > > > > and see how you go on. > > Hello, > I have just given cups-daemon/2.2.7-5 a try with socket activation > re-enabled. > > I really seems to work as intended. > The bug fix appears to solve the issue! > Thank you so much. > > I think this bug report may be forcemerged with #898745 (and thus > closed). Please do so, if you agree Doing as you suggest. Thanks for the update. Cheers, Brian.
Bug#894762: cups-daemon: with IdleExitTimeout 60, correctly exits when idle for 60 s, but immediately respawns [regression]
On Fri, 18 May 2018 18:58:21 +0100 Brian Potkin wrote: > On Wed 04 Apr 2018 at 22:29:07 +0200, Francesco Poli wrote: > > > Looking forward to hearing back from you. > > Thanks for your time and patience! > > Not too long a wait, I hope, Francesco. > > Please try the technique in #898745 > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898745 > > and see how you go on. Hello, I have just given cups-daemon/2.2.7-5 a try with socket activation re-enabled. I really seems to work as intended. The bug fix appears to solve the issue! Thank you so much. I think this bug report may be forcemerged with #898745 (and thus closed). Please do so, if you agree. -- 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 pgp3oOH1SSNcD.pgp Description: PGP signature
Bug#894762: cups-daemon: with IdleExitTimeout 60, correctly exits when idle for 60 s, but immediately respawns [regression]
On Wed 04 Apr 2018 at 22:29:07 +0200, Francesco Poli wrote: > Looking forward to hearing back from you. > Thanks for your time and patience! Not too long a wait, I hope, Francesco. Please try the technique in #898745 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898745 and see how you go on. Cheers, Brian.
Bug#894762: cups-daemon: with IdleExitTimeout 60, correctly exits when idle for 60 s, but immediately respawns [regression]
Control: reopen -1 On Wed, 04 Apr 2018 21:06:26 +0200 Didier 'OdyX' Raboud wrote: > 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. Hello Brian and Didier! Thanks to both of you for your kind and prompt replies. > > You can configure this by creating a /etc/systemd/system/cups.service with > [Service] > Restart=no Do I understand correctly that /etc/systemd/system/cups.service should be a (modified) copy of /lib/systemd/system/cups.service ? Or the two above quoted lines are enough as the content of /etc/systemd/system/cups.service ? > > As that's an upstream decision, I'm hereby closing this bugreport. Please > reopen if you think a Debian-specific patch could make sense. Well, I am afraid I do not understand this upstream decision. I mean: what's the point of socket activation, if the daemon is automatically re-spawned anyway? A Debian-specific patch could probably make sense, otherwise countless users who want socket activation will need to create their (modified) version of cups.service to be placed into /etc/systemd/system/ Moreover, I think that the documentation in README.Debian.gz is no longer accurate, as it talks about SystemdIdleExit, which is no longer supported, and, above all, it says nothing about this Restart=no directive, which is now needed in order to enable socket activation... I am reopening the bug report, since, at the very least, copying /usr/share/doc/cups-daemon/examples/cups-socket.localhost.conf into /etc/systemd/system/cups.socket.d/ is no longer enough to enable socket activation. Hence the documentation is outdated, as I said. Looking forward to hearing back from you. Thanks for your time and patience! -- 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 pgpY5aFEwEUJ2.pgp Description: PGP signature
Bug#894762: cups-daemon: with IdleExitTimeout 60, correctly exits when idle for 60 s, but immediately respawns [regression]
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.
Bug#894762: cups-daemon: with IdleExitTimeout 60, correctly exits when idle for 60 s, but immediately respawns [regression]
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 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! Bye. -- 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 bc1.07.1-2 ii dpkg 1.19.0.5 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 procps2:3.3.12-4 ii ssl-cert 1.0.39 Versions of packages cups-daemon recommends: pn avahi-daemon ii colord1.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 ii cups-ppdc2.2.7-1 ii cups-server-common 2.2.7-1 ii foomatic-db 20180210-1 ii ghostscript 9.22~dfsg-2 pn hplip ii poppler-utils0.62.0-2 ii printer-driver-gutenprint5.2.13-2 ii printer-driver-hpcups3.17.10+repack0-5 pn smbclient ii udev 238-3 -- no debconf information
