Bug#832637: cups-browsed: Shutdown hangs on A stop job runs for Make remote CUPS printers available locally
On Thu 28 Jul 2016 at 02:00:36 +0200, Heinrich Schuchardt wrote:
Thank you for your report, Heinrich.
> every time I shutdown my system I have to wait 90 s for a stop job
> showing the message
Is this consistent behaviour?
> A stop job runs for Make remote CUPS printers available locally
This should not be happening since 1.9.0-1.
> Shutdown should be as fast as possible.
>
> The same job could be run in the background at any time.
>
> Typically systems are shutdown when leaving office and restarting
> the system in another network with other printers.
>
> So looking for remote printers in a shutdown job does not
> make much sense. If the job is needed at all, run it when
> starting the system.
cups-browsed creates local print queues for remote queues when it starts
up. These queues need removing when it closes down. To do this it needs
the cups daemon to be running so that it can communicate with it and
have it adjust the contents of /etc/cups/printer.conf.
Issue the command
systemctl stop cups.service cups-browsed.service
It should complete almost immediately. Does it?
Look at the output of 'journalctl'. It should show cups-browsed stopping
before cups does. This allows communication between the two to continue
and is an indication of what should happen at reboot or poweroff.
Please post the contents of cups-browsed.service and cups.service from
/lib/systemd/system/.
Regards,
Brian.
Reply to: