[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] Using cron job to manipulate START expression


condor_config_val does only show the configuration (i.e. config files), not the daemon state. This the information used for startup. Once running, the startd (any daemon, actually) is free to deviate from the initial state.
If condor_status, especially with the -direct flag, shows the proper state then everything worked fine.


> Am 09.10.2017 um 19:33 schrieb Sveinung Rundhovde <svrundh@xxxxxx>:
> Hi,
> I am attempting to use a startd cron job to manipulate the START expression. The machine ClassAd is updated and sent to the Collector as expected (as shown by the condor_status command). However, the START value in the setting of the startd daemon remains unchanged (as shown by the condor_config_val command). 
> This leads to the odd behavior that setting START = False through the cron job works as expected, but setting START = True through the cron job if it is set to false in the configuration does not work.
> Is there setting having the START value updated in the startd configuration as well?
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/htcondor-users/

Attachment: smime.p7s
Description: S/MIME cryptographic signature