Bug#814340: marked as done (CUPS won't start at boot (systemd))
Your message dated Fri, 12 Feb 2016 23:19:47 +0000
with message-id <20160212231947.GC1373@copernicus.demon.co.uk>
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 owner@bugs.debian.org
immediately.)
--
814340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814340
Debian Bug Tracking System
Contact owner@bugs.debian.org 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 ---
On Wed 10 Feb 2016 at 15:50:53 +0100, Cédric Dufour - Idiap Research Institute wrote:
> Hello,
Hello Cédric,
Thank you for your report.
> 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
A brand new CUPS installation has no need of a listening daemon. There
are no local print queues and cupsd listens only on localhost and the
socket file in /var/run/cups. If printing is attempted to either a
created or non-existent queue cups.service will be activated via
cups.socket.
> "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).
As above.
Regards,
Brian.
--- End Message ---
Reply to: