Red Hat Bugzilla – Bug 548137
TIMEOUT_MULTIPLIER only available in <SUBSYS>_ form
Last modified: 2010-10-14 11:57:39 EDT
All version including 7.4.1-0.7.1 condor_daemon_client/daemon.cpp params for TIMEOUT_MULTIPLIER, but only does so for a specific subsystem, e.g. SUBMIT_TIMEOUT_MULTIPLIER or TOOL_TIMEOUT_MULTIPLIER. It does not allow for a naked TIMEOUT_MULTIPLIER or for the proper <SUBSYSTEM>.TIMEOUT_MULTIPLIER syntax. Upstream: http://condor-wiki.cs.wisc.edu/index.cgi/tktview?tn=1066
Expected behavior: $ env _CONDOR_TOOL_TIMEOUT_MULTIPLIER=10 _CONDOR_TOOL.TIMEOUT_MULTIPLIER=5 condor_q -debug 2>&1 | head -n1 12/18 10:14:07 *** TIMEOUT_MULTIPLIER :: 10 $ env _CONDOR_TOOL_TIMEOUT_MULTIPLIER=10 condor_q -debug 2>&1 | head -n1 12/18 10:14:13 *** TIMEOUT_MULTIPLIER :: 10 $ env _CONDOR_TOOL.TIMEOUT_MULTIPLIER=10 condor_q -debug 2>&1 | head -n1 12/18 10:14:17 *** TIMEOUT_MULTIPLIER :: 10 $ env _CONDOR_TIMEOUT_MULTIPLIER=10 condor_q -debug 2>&1 | head -n1 12/18 10:14:30 *** TIMEOUT_MULTIPLIER :: 10 $ condor_q -debug 2>&1 | head -n1 12/18 10:14:35 *** TIMEOUT_MULTIPLIER :: 0
Upstream: http://condor-wiki.cs.wisc.edu/index.cgi/tktview?tn=1076 commit da11c45c3abd06210afe3f822aaba3259b1ef635 Author: Matthew Farrellee <matt@> Date: Fri Dec 18 10:23:42 2009 -0500 TIMEOUT_MULTIPLIER now available with SUBSYS.PARAM syntax (#1076) diff --git a/src/condor_daemon_client/daemon.cpp b/src/condor_daemon_client/daemon.cpp index 511049f..df3759d 100644 --- a/src/condor_daemon_client/daemon.cpp +++ b/src/condor_daemon_client/daemon.cpp @@ -68,7 +68,8 @@ Daemon::common_init() { m_daemon_ad_ptr = NULL; char buf[200]; sprintf(buf,"%s_TIMEOUT_MULTIPLIER",get_mySubSystem()->getName() ); - Sock::set_timeout_multiplier( param_integer(buf,0) ); + Sock::set_timeout_multiplier( param_integer(buf, param_integer("TIMEOUT_MULTIPLIER", 0)) ); + dprintf(D_DAEMONCORE, "*** TIMEOUT_MULTIPLIER :: %d\n", Sock::get_timeout_multiplier()); m_has_udp_command_port = true; }
D_DAEMONCORE must be enabled to see the output expected in #c1.
Fixed in 7.4.2-0.1
Tested: # env _CONDOR_TOOL_TIMEOUT_MULTIPLIER=10 _CONDOR_TOOL.TIMEOUT_MULTIPLIER=5 condor_q -debug 2>&1 | head -n1 09/15/10 04:56:18 *** TIMEOUT_MULTIPLIER :: 10 # env _CONDOR_TOOL_TIMEOUT_MULTIPLIER=10 condor_q -debug 2>&1 | head -n1 09/15/10 04:56:27 *** TIMEOUT_MULTIPLIER :: 10 # env _CONDOR_TIMEOUT_MULTIPLIER=10 condor_q -debug 2>&1 | head -n1 09/15/10 04:56:36 *** TIMEOUT_MULTIPLIER :: 10 # condor_q -debug 2>&1 | head -n1 09/15/10 04:56:42 *** TIMEOUT_MULTIPLIER :: 0 Tested with (version): condor-7.4.4-0.9 Tested on: RHEL5 x86_64,i386 - passed RHEL4 x86_64,i386 - passed >>> VERIFIED
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2010-0773.html