It turns out that nodus doesn't know how to NDS2, so I can't run diagAllSUS as a cron job on nodus. To further complicate things, no other machines can run the elog utility, so I am going to have to do something shifty...
Actually in the last 40m meeting we discussed the SUS diagnosis and decided not to post the results on the elog.
Alternatively we will have a summary web page which will contain all the information (sensitivity, UGF monitors, etc.,) and will be updated everyday like GEO.
This will be a place where we should post the SUS results every week.
So we don't need to worry about the cron-elog job, and for running the scripts you can simply use one of the lab machines as a cron host.
Once you get the scripts running on a machine as a cron job, it will be the point where we should quit developing the SUS diagonalizer and pass it to the web summary people.