Bug#814340: CUPS won't start at boot (systemd)
Hello Brian,
Thank you for your follow up.
There something I don't understand and maybe you can clarifiy it for me (see below)
On 13/02/16 00:19, Brian Potkin wrote:
> On Wed 10 Feb 2016 at 15:50:53 +0100, Cédric Dufour - Idiap Research Institute wrote:
>
>
>> 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.
>
Unless there is something that I miss entirely, listening on localhost:631 (the all LAN in my case; cf. campus print servers) implies a daemon (cupsd):
* root@cups01.idiap.ch:~
# netstat -tpan | fgrep :631
tcp 0 0 0.0.0.0:631 0.0.0.0:* LISTEN 4560/cupsd
tcp6 0 0 :::631 :::* LISTEN 4560/cupsd
When I said CUPS won't start, maybe I should have said that it is not listening on port 631 after boot (because cupsd did not start during boot).
Again, unless there is something that I miss entirely, no amount of trying to reach the CUPS server (cupsd) on port 631 (from the LAN) will make it start.
So I'm afraid there IS a bug in there: the CUPS daemon (cupsd) must start at boot for a LAN (*:631) CUPS server to serve its purpose.
Best regards,
Cédric
Reply to: