On Sun 21 Aug 2016 at 17:50:41 +0200, Heinrich Schuchardt wrote:
> On 08/21/2016 02:20 PM, Brian Potkin wrote:
> > 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 sto
On 08/21/2016 02:20 PM, Brian Potkin wrote:
> 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?
Yes, this h
On Sun, Aug 21, 2016 at 4:27 PM, Brian Potkin
wrote:
> Are you positive cups.service is still running while cups-browsed is
> stopping? 'systemctl status cups' in another terminal would tell you.
>
Yes
> If I use the sequence
>
> systemctl start cups cups-browsed.service
> systemctl stop c
Thank you for the extra information, Roderich.
On Sun 21 Aug 2016 at 14:57:57 +0200, Roderich Schupp wrote:
> I have the same problem as Heinrich Schuchardt (same version of
> cups-browsed, but cups-daemon 2.2~rc1-4 from experimental).
>
> $ sudo systemctl stop cups-browsed.service
>
> takes
I have the same problem as Heinrich Schuchardt (same version of
cups-browsed, but cups-daemon 2.2~rc1-4 from experimental).
$ sudo systemctl stop cups-browsed.service
takes 90 seconds (while avahi-daemon.service and cups.service are still
running). journalctl shows
Aug 21 14:38:52 macarthur sud
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
