This is {link: http://www.cs.wisc.edu/condor/manual/v7.6/4_4Hooks.html#sec:daemon-classad-hooks Condor's "Daemon ClassAd Hooks" functionality},
previous known as HawkEye and Condor Cron. This is the route taken by the {link: http://sourceforge.net/projects/condorgpu/ condorgpu project} (Note that the condorgpu project has no affiliation with Condor. We have not tested or reviewed that code and cannot promise anything about it!)
-Such a configuration might look something like this, assuming that each machine had at most one GPU.
+Such a configuration might look something like this, assuming that each machine had at most two GPUs.
{code}
STARTD_CRON_JOBLIST = $(STARTD_CRON_JOBLIST) GPUINFO1
@@ -86,9 +86,18 @@
# which device should get-gpu-info probe?
STARTD_CRON_GPUINFO1_PARAM0 = 0
STARTD_CRON_GPUINFO1_SLOTS = 1
+
+STARTD_CRON_JOBLIST = $(STARTD_CRON_JOBLIST) GPUINFO2
+STARTD_CRON_GPUINFO2_MODE = OneShot
+STARTD_CRON_GPUINFO2_RECONFIG_RERUN = FALSE
+STARTD_CRON_GPUINFO2_PREFIX = GPU_
+STARTD_CRON_GPUINFO2_EXECUTABLE = $(MODULES)/get-gpu-info
+# which device should get-gpu-info probe?
+STARTD_CRON_GPUINFO2_PARAM0 = 1
+STARTD_CRON_GPUINFO2_SLOTS = 2
{endcode}
-This will call $(MODULES)/get-gpu-info with an argument of "0" (indicating that it should check the first GPU device). The output will be prepended with "GPU_" and advertised for slot 1 only. If a machine might have more GPUs, you'll need to repeat this section, changing all the "1" to "2", then "3" and so on, and changing the "0" to "1", then "2" and so on.
+$(MODULES)/get-gpu-info will be invoked twice, once for each of the two possible GPUs. (You can support more by copying the above entries and increasing the integers. #2196, if implemented, may allow for a simpler configuration.) get-gpu-info will be passed the device ID to probe (0 or 1). The output should be a ClassAd; entries will have GPU_ prepended, then they will be added to to slot ClassAds for slots 1 and 2.
get-gpu-info would write output to its standard output that looked something like:
