Your message dated Mon, 1 Jan 2018 16:23:40 +0000 with message-id <[email protected]> and subject line Re: Bug#814340: CUPS won't start at boot (systemd) has caused the Debian Bug report #814340, regarding CUPS won't start at boot (systemd) 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.) -- 814340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814340 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: cups-daemon Version: 1.7.5-11+deb8u1 Hello, I have found that CUPS will not start at boot if the /var/spool/cups directory contains no d* files (job files). This is the case for a brand new CUPS installation or if "PreserveJobFiles" is set to "No" in /etc/cups/cupsd.conf (eg. for large campus print servers, where keeping job files would require a lot of storage and may be the source of privacy issues). The culprit appears to be /lib/systemd/system/cups.path. If one changes: PathExistsGlob=/var/spool/cups/d* To: PathExists=/var/spool/cups (possible workaround/hack: touch /var/sppol/cups/d) CUPS starts at boot as expected. Thank you for considering this report. Best regards, Cédric -- Cédric Dufour @ Idiap Research Institute
--- End Message ---
--- Begin Message ---fixed 814340 cups-daemon/2.0.2-1 thanks On Sat 13 Feb 2016 at 13:41:31 +0000, Brian Potkin wrote: > The issue doesn't seem to arise in unstable, where cups.path has > > [Path] > PathExists=/var/cache.cups/org.cups.cupsd The line above is from upstream's systemd support and seems to fix the bug. There have also been no adverse reports about it. Hence closing. Cheers, Brian.
--- End Message ---
