xrootd runs on glast01 to serve the root histograms required by the system tests web front-end.

All relevant files can be found in ~glast/xrootd:

• xrootd - The script which runs xrootd
• xrootd.cf - The configuration file for xrootd
• monitor - A program run by cron every 5 minutes to check that xrootd is running, and to start it if not
• crontab - The entry added to crontab to run monitor

xrootd currently runs under account glast, and can serve data (read-only) from /nfs/farm/g/glast.

xrootd currently runs from the Root installation at /nfs/farm/g/glast/u05/GLAST_EXT/rh9_gcc32/ROOT/v4.02.00/root (xrootd has minimal dependence on root, so it might be more robust to simply copy the files required to the ~glast/xrootd directory, so that the service doesn't break when someone eventually deletes the above directory).

Log files from xrootd are written to /tmp/xrootd

xrootd listens for incoming connections on port 1094 (the rootd default)

I wouldn't worry about /nfs/farm/g/glast/u05/GLAST_EXT/rh9_gcc32/ROOT/v4.02.00/root being erased. They'll be around for a long time since that's the offical place of our external libraries. Chances are we will be using a newer version of xrootd way before that directory gets erased. Posted by golpa at Jan 26, 2005 18:05

does anything clean up /tmp/ on glast01? Dan had been writing to glast04's root partition with the pipeline's admittedly verbose logs. He moved it to a big farm nfs partition. Posted by richard at Jan 28, 2005 17:08

xrootd automatically creates a new log file each day. For now at least they should be quite small. I think taylor runs something that deletes old files on /tmp, we can watch and see how long they build up for. Posted by tonyj at Jan 29, 2005 09:54