* * * * * /website/config/sync.sh > /dev/null 2>&1
runs like this from crontab on each webserver.
On Thu, 12 Apr 2001, Dan Phoenix wrote:
> Date: Thu, 12 Apr 2001 13:31:24 -0700 (PDT)
> From: Dan Phoenix <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: rsync across nfs
>
>
>
> He
Here is my contribution to rsync.
Attached is my current script that syncs off nfs.
IT works along with cvs checking your commit log for checksum changes.
This is a nice script for small networks that has gotten me by this far...
i will be writing another one for bigger networks shorty pushing d
We went over this about 5 months ago ...pushing data is way slower that
getting itthat is why this approach was taken.
But that is a good idea as server load just gets hit to hard.
On Wed, 11 Apr 2001, Eric Whiting wrote:
> Date: Wed, 11 Apr 2001 21:08:51 -0600
> From: Eric Whiting <[EMA
On Tue, Apr 10, 2001 at 10:53:19PM +1000, Anthony Rumble wrote:
> On Tue, 10 Apr 2001 [EMAIL PROTECTED] wrote:
> > Try it ... rsync does NOT modify files in place, it creates a temporary
> > file and then renames it if the transfer is successful, so the other link
> > (i.e. the old file) will rema
Say you have 6 hosts that need to have a common file or directory (the common
usage for rsync). You find that an update every N hours is good enough and
you want to code a cron job to make it happen. You'd also like any host
that is off-line to 1) not mess up the others, and 2) sync on the way
