I’ve found two problems with condor_condor_val. They both seem to involve colons.
The first issue is strange behaviour:
[acanis@ttc-abcdev log]# condor_config_val -set "A = bbb"
Successfully set configuration "A = bbb" on master ttc-abcdev.altera.com <137.57.176.244:55450>.
[acanis@ttc-abcdev log]# condor_config_val -set "A = ::"
condor_config_val: Error: Configuration variable names cannot contain spaces
[acanis@ttc-abcdev log]# condor_config_val -set "A=::"
Successfully set configuration "A=::" on master ttc-abcdev.altera.com <137.57.176.244:55450>.
I only notice this error when I have a colon in the value I'm trying to set.
The second issue seems to be an actual bug.
[acanis@ttc-ichesal-lnx ttc-ichesal-lnx]$ condor_config_val -set "S=/:"
Attempt to set configuration "S=/:" on master ttc-ichesal-lnx.altera.com <137.57.142.163:33406> failed.
Inspecting the MasterLog gives:
7/7 16:07:01 DaemonCore: Command received via TCP from host <137.57.176.244:58071>
7/7 16:07:01 DaemonCore: received command 60002 (DC_CONFIG_PERSIST), calling handler (handle_config())
7/7 16:07:01 open(/build/condor/log/.config.MASTER.s=/.tmp) returned -1 'No such file or directory' (errno 2) in set_persistent_config()
All tests were done on a dual-Xeon 1 GHz Dell 2000-series server with 2 GB of RAM running FC3 and the 6.7.20 binaries.
Thanks,
Andrew