Antoine Durr wrote:
> Hmmm, I hadn't thought of the problem that I need to rdist the file. I
> optimistically thought that I'd only need to do it in one place. Do I
> need to have *all* the machines have the same info at the same time, or
> is it sufficient for the submitting machine to have the latest hosts
> file?
I wouldn't recommend having a mix across the network;
the rush/etc/* files should all be in sync.
The 'rush -push' command makes this easy; you can update
eg. the rush/etc/hosts file to the entire network with
a single command: 'rush -push hosts +any', but its mainly
meant as an 'interactive use' command.
> Maybe I could have the submit script rewrite it on the fly
> (which is really the only time I need it updated). But that wouldn't
> work if all hosts need to be synchronized.
Definitely keep them synchronized; the daemons will get confused
if each machine has different hosts file data.
That said, there are some exceptions where it can be desireable
to have different contents, but that's rare. As a general rule,
keep all files in the rush/etc/* directory in sync; whenever you
change it on one box, copy it out to the rest with either 'rush -push',
or rdist, or whatever you like (as long as the copy is done atomically)
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
|