https://bugzilla.novell.com/show_bug.cgi?id=722902
https://bugzilla.novell.com/show_bug.cgi?id=722902#c2
Johannes Meixner changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
InfoProvider| |mat@mshopf.de
--- Comment #2 from Johannes Meixner 2011-10-12 08:39:44 UTC ---
FYI:
Instead of a fixed "ServerName" entry in /etc/cups/client.conf
(the so called "client-only" configuration), you can also set
the CUPS server via the CUPS_SERVER environment variable.
If you do not like a local running cupsd with "BrowsePoll",
perhaps setting the CUPS_SERVER environment variable
depending on which network environment you currently have
works best in your case?
It depends very much how exacty a CUPS server is unaccessible
how long it takes:
------------------------------------------------------------------
# rccups stop
Shutting down cupsd done
# export CUPS_SERVER="localhost"
# time lpstat -p 1>/dev/null
lpstat: Connection refused
real 0m0.008s
user 0m0.000s
sys 0m0.004s
------------------------------------------------------------------
# export CUPS_SERVER="does.not.exist"
# time lpstat -p 1>/dev/null
lpstat: Unable to connect to host.
real 0m0.011s
user 0m0.000s
sys 0m0.004s
------------------------------------------------------------------
# export CUPS_SERVER="www.novell.com"
# time lpstat -p 1>/dev/null
lpstat: Network is unreachable
real 0m42.005s
user 0m0.008s
sys 0m0.000s
# time netcat -z www.novell.com 80 && echo yes || echo no
yes
real 0m0.166s
user 0m0.000s
sys 0m0.000s
# time netcat -z www.novell.com 631 && echo yes || echo no
no
real 0m20.999s
user 0m0.004s
sys 0m0.000s
------------------------------------------------------------------
The long delays in the last case are no DNS timeouts.
It seems the long delays happen when there is firewall
functionality in between which silently drops packages
so that there is no response at all and then applications
can only wait until they give up after a long timeout:
------------------------------------------------------------------
root@server# rccups stop
Shutting down cupsd done
root@client# export CUPS_SERVER="server"
root@client# time lpstat -p 1>/dev/null
lpstat: Connection refused
real 0m0.010s
user 0m0.004s
sys 0m0.000s
root@server# rcSuSEfirewall2 start
Loading firewall rules done
nroot@client# time lpstat -p 1>/dev/null
lpstat: Connection timed out
real 0m42.007s
user 0m0.004s
sys 0m0.000s
------------------------------------------------------------------
Matthias Hopf,
does LibreOffice actually "freeze" in your case
or does it continue after a longer timeout?
Of course if LibreOffice sends many requests to a CUPS server,
the long timeouts of each request could sum up so that
LibreOffice effectively freezes (nobody waits for hours).
LibreOffice should at least detect if a CUPS server
does not respond (e.g. first do what "lpstst -r" does)
and give up after at most one such long timeout
and show a meaningful error message to the user.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.