-{section: How to insert custom ClassAd attributes into a machine ad} +{section: How to insert custom {quote: ClassAd} attributes into a machine ad} Known to work with Condor version: 7.0 In the following exapmles, a custom ClassAd attribute named _MachineOwner_ is created with the value "chemistry". You can use whatever attribute name you want, but avoid conflicting with attribute names used by Condor. See the manual or run {code}condor_status -long{endcode} on a machine to see the attributes that are there. -{subsection: How to insert custom ClassAd attributes in a machine ad via the config file} +{subsection: How to insert custom {quote: ClassAd} attributes in a machine ad via the config file} {code} MachineOwner = "chemistry" @@ -20,7 +20,7 @@ STARTD_ATTRS = $(STARTD_ATTRS) MachineOwner {endcode} -{subsection: How to insert custom ClassAd attributes in a machine ad via a script} +{subsection: How to insert custom {quote: ClassAd} attributes in a machine ad via a script} You can insert dynamic attributes that are periodically updated from a script. Here's an example of what you put in the condor configuration file to periodically call a script: @@ -46,4 +46,4 @@ hugemem = FALSE {endcode} -Given the configuration above, this would result in ClassAd attributes being added to the machine ClassAd with the following names: kernel_version, kernel_bigmem, and kernel_hugemem. +Given the configuration above, this would result in {quote: ClassAd} attributes being added to the machine {quote: ClassAd} with the following names: kernel_version, kernel_bigmem, and kernel_hugemem.