BrowseTimeout broke?

angelb angelb at bugarin.us
Fri Mar 30 07:17:51 PDT 2007


> > angelb wrote:
> > > ...
> > > Can anyone else try and duplicate this? Or is this already a known issue?
> >
> > I am unable to duplicate this myself, and it isn't a known issue.
> >
> > Can you provide a debug2 log from the 1.2 CUPS client that shows the
> > browse packets?
> >
>
> aha...it didn't like my 15-seconds timeout. btw, this client is running
> cups 1.2.4.
>
> ROOT @ SAPTI02F # grep -i time error_log
> A [29/Mar/2007:08:42:15 +0600] Invalid BrowseTimeout value 15!
> A [29/Mar/2007:08:42:15 +0600] Reset BrowseTimeout to 7200!
> d [29/Mar/2007:08:42:52 +0600] [cups-polld stlam506:631] Sending 3056 3 ipp://st
> ...
>

Why did the BrowseTimeout function changed from 1.1 to 1.2? I think it
should have been left to the user to define its own value instead of
providing a default value(2x BrowseInteval).


btw, the ad-hoc cups-polld restart thing leaves a client unstable.

ROOT @ SAPTI01F # ps -ef|grep -i cups
    root  938010       1   0   Mar 27      - 43:03 /opt/TWWfsw/cups124/sbin/cups
d -c /etc/opt/TWWfsw/cups124/cupsd.conf
    cups 1028222  938010 120   Mar 27      - 539:57 cups-polld stlam506 631 3600
 631

This client has been running for more than two days since I manually restarted cups-polld. Now its CPU usage spiked to the roof.


Thanks,
Angel




More information about the cups mailing list