sigh ... too bad when important projects are a one-man-show.
CUPS lacks a feature that openldap for example implments with LDAP_OPT_NETWORK_TIMEOUT.
You can easily reproduce the problem in CUPS by setting
ServerName some-unused-ip-address-in-your-local-subnet
in /etc/cups/client.conf.
Samba had the same problem and implemented a workaround for the lack of a connect timeout in cups:
http://git.samba.org/?p=samba.git;a=commitdiff;h=765e5d2282959770ea9648e0f2b72e51e5b4cdd8
sigh ... too bad when important projects are a one-man-show.
CUPS lacks a feature that openldap for example implments with LDAP_OPT_ NETWORK_ TIMEOUT.
You can easily reproduce the problem in CUPS by setting
ServerName some-unused- ip-address- in-your- local-subnet
in /etc/cups/ client. conf.
Samba had the same problem and implemented a workaround for the lack of a connect timeout in cups:
http:// git.samba. org/?p= samba.git; a=commitdiff; h=765e5d2282959 770ea9648e0f2b7 2e51e5b4cdd8