...
Automated Process (updated by trscronjob)
reflector.cgi
This is run twice nightly by the trscrontab on pinger@pinger.slac.stanford.edu to ping the target www.slac.stanford.edu. The first time it uses all enabled landmarks. The second time it uses the disabled landmarks.
tulip-tuning.pl
Using the results from the analysis script we can identify the hosts and their success percentages. We opted to disable all the hosts which were having success less than 20%. The above mentioned script is in /afs/slac.stanford.edu/package/pinger/tulip and it performs the listed functions. It uses the LWP package to access the webpage, download the analyzed tulip log file, saves it in a file and then parse parses the output to get the faulty landmarks (i.e. the ones below 20% success rate by default). It is run nightly (see the trscrontab) before the sites.xml is created and specifies using the tulip log file for the last 3 days.
landmark-laundering.pl
After solving the cleaning up process, we need to address another situation and that is whether any of those hosts would come back and if yes how we would know. Should we disable them forever or should we build up some mechanism to bring them back ? To solve this problem we devised a notification process, which can help us in identifying the landmarks which are up. The above mentioned script is in /afs/slac.stanford.edu/package/pinger/tulip
...