Your message dated Thu, 21 Jun 2018 22:07:50 +0100 with message-id <[email protected]> and subject line Re: Bug#899259: cups-daemon: with IdleExitTimeout 60, fails to exit after 60 s of inactivity has caused the Debian Bug report #899259, regarding cups-daemon: with IdleExitTimeout 60, fails to exit after 60 s of inactivity 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 [email protected] immediately.) -- 899259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899259 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: cups-daemon Version: 2.2.7-5 Severity: normal Dear Debian Printing Team, this bug report is a sort of "sequel" of #894762... After some preliminary tests, I concluded that socket activation was working again. Well, I was wrong! :-( After some further testing, I found out the following misbehavior. a) in my preliminary tests, the "lpq" command correctly woke cupsd up, and the daemon correclty exited after 60 s of inactivity (I have set "IdleExitTimeout 60" in /etc/cups/cupsd.conf) b) on the other hand, if I print something with the "lpr" command, cupsd is correctly started, but it seems to never exit for inactivity: $ systemctl status cups.service ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: ena Active: active (running) since Mon 2018-05-21 11:59:07 CEST; 9h ago Docs: man:cupsd(8) Main PID: 15103 (cupsd) Tasks: 1 (limit: 4915) Memory: 6.6M CGroup: /system.slice/cups.service └─15103 /usr/sbin/cupsd -l May 21 11:59:07 HOSTNAME systemd[1]: Started CUPS Scheduler. c) now, after manually quitting cupsd and after re-enabling socket activation: # systemctl stop cups.service # systemctl daemon-reload # systemctl restart cups.socket an "lpq" command correctly starts cupsd (again), but the daemon fails to exit after 60 s of inactivity Why does cupsd fail to exit? What's wrong? Please help me. Thanks for your time! -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (800, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-1-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+b1 ii dpkg 1.19.0.5+b1 ii libavahi-client3 0.7-4 ii libavahi-common3 0.7-4 ii libc6 2.27-3 ii libcups2 2.2.7-5 ii libcupsmime1 2.2.7-5 ii libdbus-1-3 1.12.8-2 ii libgssapi-krb5-2 1.16-2 ii libpam0g 1.1.8-3.7 ii libpaper1 1.1.24+nmu5 ii libsystemd0 238-4 ii lsb-base 9.20170808 ii procps 2:3.3.14-1+b1 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.3-1+b1 Versions of packages cups-daemon suggests: ii cups 2.2.7-5 ii cups-bsd 2.2.7-5 ii cups-client 2.2.7-5 ii cups-common 2.2.7-5 ii cups-filters [foomatic-filters] 1.20.3-1+b1 pn cups-pdf <none> ii cups-ppdc 2.2.7-5 ii cups-server-common 2.2.7-5 ii foomatic-db 20180306-1 ii ghostscript 9.22~dfsg-2.1 pn hplip <none> ii poppler-utils 0.63.0-2 ii printer-driver-gutenprint 5.2.13-2+b1 ii printer-driver-hpcups 3.17.10+repack0-5 pn smbclient <none> ii udev 238-4 -- no debconf information
--- End Message ---
--- Begin Message ---On Thu 21 Jun 2018 at 21:30:58 +0200, Francesco Poli wrote: > On Wed, 20 Jun 2018 15:33:20 +0100 Brian Potkin wrote: > > [...] > > Looking at the debug2 error log lead me to putting > > > > PreserveJobHistory No > > > > in cupsd.conf. This gives reliable and consistent socket activation > > and timing out. How about for you? > > Thanks for the suggestion. > > Now I am trying with the following configuration: > > $ grep -v '^#' /etc/cups/cupsd.conf | head -n 18 > > LogLevel warn > PageLogFormat > > MaxLogSize 0 > > Listen localhost:631 > Listen /var/run/cups/cups.sock > IdleExitTimeout 60 > PreserveJobHistory No > > Browsing No > BrowseLocalProtocols dnssd > > DefaultAuthType Basic > > WebInterface No > > > Judging from the few tests that I could perform (without wiping out the > whole Amazon rainforest, print test after print test!), socket > activation seems to work as intended. > I hope it will go on working correctly... Thank you for the confirmation that "PreserveJobHistory No" works for you. This is a win in my book, irrespective of the inticacies involved in socket activation. You seem happy with the outcome, so let us close this this report and see what the future brings. My appreciation for your co-operation, Brian.
--- End Message ---
