Bug#814340: marked as done (CUPS won't start at boot (systemd))
Your message dated Mon, 1 Jan 2018 16:23:40 +0000
with message-id <01012018161417.8089674dea42@desktop.copernicus.org.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: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814340
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: CUPS won't start at boot (systemd)
- From: Cédric Dufour - Idiap Research Institute <cedric.dufour@idiap.ch>
- Date: Wed, 10 Feb 2016 15:50:53 +0100
- Message-id: <56BB4E4D.6080306@idiap.ch>
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 ---
- To: 814340-done@bugs.debian.org
- Subject: Re: Bug#814340: CUPS won't start at boot (systemd)
- From: Brian Potkin <claremont102@gmail.com>
- Date: Mon, 1 Jan 2018 16:23:40 +0000
- Message-id: <01012018161417.8089674dea42@desktop.copernicus.org.uk>
- In-reply-to: <13022016131319.216514c8f149@desktop.copernicus.demon.co.uk>
- References: <56BB4E4D.6080306@idiap.ch> <20160212231947.GC1373@copernicus.demon.co.uk> <56BEEF78.9070205@idiap.ch> <13022016131319.216514c8f149@desktop.copernicus.demon.co.uk>
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 ---
Reply to: