Bug#759348: cups-browsed: May hang for 30 seconds when restarted
On Thu 30 Oct 2014 at 08:50:13 +0100, Didier 'OdyX' Raboud wrote:
> Hi Brian, and thanks for your (as always) detailed and extensive
> bugreport.
Thank you.
> Le mardi, 26 août 2014, 16.46:33 Brian Potkin a écrit :
> > On an up-to-date unstable version 1.0.55-1 of cups-browsed was
> > installed. The journalctl records are shown for three commands.
> > All three commands completed successfully immediately.
> > (…)
> > cups-browsed was updated to the present version. One noticable
> > difference is that the third command hangs. Resisting the temptation
> > to do CTL-C, it eventually completes.
>
> I can't reproduce this since CUPS 1.7.5-7, where CUPS' socket activation
> got disabled. I suspect having CUPS constantly running avoids entering
> this 30 seconds hang in restart, which I think points to CUPS "time-to-
> die".
>
> If you can confirm that this behaviour disappeared, I suggest to leave
> the bug open but to retitle it to something like "cups-browsed may hang
> during restart if CUPS is socket-triggered".
I'm away from home at present but will be able to test and do as you
suggest on this Saturday/Sunday.
Regards,
Brian.
Reply to: