Hi Jay.
Try rsync from samba.org. Treat the primary as the source, make your changes
only there, and copy everything to the secondary at regular intervals.
The first copy takes a (relatively) long time, subsequent "copies" move only
the differences across the wire. The nicest thing about it is that it uses a
channel you set up - such as ssh, which will encrypt the lot, and which
doesn't require having rcp/rsh holes on either server. It doesn't even
require root access on the source machine.
Depending on your setup, you might want to weave a "stop radiator/stop
database" in there at the critical moments, otherwise you might copy
inconsistent data.
Regards, K.
Am 22-Mar-99 schrieb Jay West:
> Greetings!
>
> We have two radiator servers, each is independent but the configurations
> and
> user files are identical. Our NAS is setup to query the first, and if there
> is no reply to query the second. In this way, if one server fails the other
> is available to respond.
>
> Is there a slick neato way to sync up the users file between the two? It's
> a
> pain to have to add new users in two places. We'd prefer to not have one
> spot (like a remote SQL database, etc.) because this introduces a single
> point of failure. The first method that comes to mind is setting up a cron
> job to rcp or ftp the users file on one machine or the other. We're not
> crazy about allowing rcp or ftp into our radius servers though... Is there
> another method anyone has found?
>
> Jay West
>
>
> ===
> To unsubscribe, email '[EMAIL PROTECTED]' with
> 'unsubscribe radiator' in the body of the message.
---
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer ([EMAIL PROTECTED]) Geschaeft/work +41-1-6327531
Kommunikation, ETHZ RZ Privat/home +41-1-4517941
Clausiusstrasse 59 Fax +41-1-6321225
CH-8092 ZUERICH Switzerland
===
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
