#61: httpup timeout may be a conf option -------------------------+-------------------------------------------------- Id: 61 | Status: closed Component: httpup | Modified: Fri Feb 24 11:13:08 2006 Severity: enhancement | Milestone: Priority: normal | Version: Owner: jw | Reporter: centericq@ukr.net -------------------------+-------------------------------------------------- Comment (by jw): Just for completeness: the code used to be: {{{ #!cpp string key = s.substr(0, 10); string val = stripWhiteSpace(s.substr(10)); ... } else if (s.substr(0, 17) == "operation_timeout") { config.operationTimeout = val; } }}} if httpup.conf contains {{{"operation_timeout 300"}}}, {{{val}}} in this case is {{{"timeout 300"}}} since {{{val}}} is the substring starting from position 10. Your {{{atol("timeout 300")}}} call would then silently fail; in my tests, it returned just zero, in which case httpup would pass 0 as timeout to curl, which in turn would use its default timeout of five minutes. So basically you build a binary configuration option (30s httpup default, or 300s curl default), no matter what value one sets in httpup.conf :-) -- Ticket URL: <https://crux.nu/cgi-bin/trac.cgi/ticket/61> CRUX <http://crux.nu/> CRUX