The classad debug() function prints debugging information to the
log when the classad is evaluated.Â So, if you want to debug a
slot's START _expression_, you can append to the start _expression_
START = debug($(START))
in the startd's config file.
To debug a job's requirements, you could write in the submit file
requirements = debug(whatever the requirements were..)
I am trying to understand how to use theÂ
AnyTypeÂdebug(AnyTypeÂ_expression_)feature documented atÂhttps://htcondor.readthedocs.io/en/latest/misc-concepts/classad-mechanism.html.
I have added the following to a file in /etc/condor/config.d:
ALL_DEBUG = D_FULLDEBUG D_COMMAND
SCHED_DEBUG = D_FULLDEBUG
DString = debug(Requirements)
DString2 = debug("unimarker")
andÂcondor_config_val -schedd DStringÂ(and DString2) shows the expected results. Iâve submitted jobs and grepped the files in /var/log/condor for âunimarkerâ but am not getting any results.
Gerard WeatherbyÂ| ApplicationÂArchitect
NMRbox | Department of MolecularÂBiology and Biophysics | UConn Health
263 Farmington Avenue, Farmington,ÂCT 06030-6406
_______________________________________________ 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/