>If you could explain a bit more in detail it would be a lot clearer on >what you really want. The drawback is if you cron job it on every node >you must have a precise time server for ntp on the local subnet or your >effectively PPPing in the wind. John, They all mirror to this one file server based on a snapshot they take at that time as the data is constantly changing. Once they all complete their mirror to this file server, that file server is then instructed by ssh with key auth to rsync that data set remotely. The file server can handle any number of local dumps on to it, but if more than 1 local machine instructs it to rsync remotely, that is where the trouble starts. Dropping the jobs via ssh into 'at' for example would be nice if only 'at' sequentially executed the job queue. Batch still might execute more than one job at a time, correct? The qjob script looks promising... Thanks guys! jlc _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos