Antoine Durr wrote:
> I don't need fast dynamic updating. I just wanted to avoid having the
> same lists (or similar, but eventually diverging lists) in two
> different places. I think the solution is to have a cron job
> regenerate the rush hosts list once per day..
Oh, I see.. yes, you can do that with a cron job,
rdisting out the change to the rest of the machines.
Although not intended for 'unattended' use, you can even
use 'rush -push hosts +any'; just be sure to watch stderr
for 'NO RESPONSE FROM' errors, in case some remotes are too
busy to respond, and to retry. (Rdist'ing is better)
You won't need to use rush -reload; the daemons will pick
up the change automatically within 30 secs. (The delay
is to prevent hitting DNS all at once, esp for large sites)
rdist is safer than rcp, because there's no chance of rush
reading a partial file while it is in transit, due to how
rdist copies to a temp file, then renames it into place
as an atomic operation.
> How frequently does Rush check the file for a datestamp change? On
> every queue submit?
Rush checks every 30 secs for date stamp changes on the
rush/etc/rush.conf and rush/etc/hosts file, and reloads
only when it changes.
So even if you rdist the files around with no rush commands
involved, it will get the change within 30 secs.
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
|