Hi,
We have two boxes, a Linux box (kernel 2.2.x, rsync 2.4.6 protocol
version 24) and a Solaris box (Solaris 7, rsync 2.4.6 protocol version
24). Both up to date on patches and rsync, etc.
We use rsync to sync files from the Linux box to the Solaris box.
We use (rsync -vvcWr -e "ssh -l
Does any one have a port for NT Rsync?
> From: Dave Dykstra <[EMAIL PROTECTED]>
> Date: Tue, 19 Dec 2000 10:10:46 -0600
> Subject: Re: rsync daemon
>
> I noticed this same problem on my redhat 6.2 machine last week. Check
> /var/adm/messages. Mine reported
>
> inetd[415]: rsync/tcp server failing (looping or being flooded), ser
The other option is to replace inetd with xinetd. It offers config options
so you can tune the loop termination among other things. If you have a
high-use rsync daemon then standalone is probably best.
-Lee
---begin quoted text---
> From: Dave Dykstra <[EMAIL PROTECTED]>
> Subject: Re: rsync
I remember seeing this happen when I first set up my rsync distribution. It
turned out to be a permissions problem on the remote, though not reported as
such - as Dave suggested below. It just wouldn't delete the file. Fixed the
permissions, and then deletion went fine.
I started with a small set
On Tue, Dec 19, 2000 at 04:39:32PM +1100, Ian Millsom wrote:
> > What's your version of rsync? What's your OS, both client and server?
> > Please post replies to the list.
>
> Sorry forgot to mention, all servers running redhat 6.2 rsync version
> 2.4.1 on all machines
>
> Just after this posti
On Tue, Dec 19, 2000 at 10:02:08AM +0100, Ferran Jorba wrote:
...
> What *did* make a difference is to rsync a single directory, and, thus,
> not using any --exclude directory. Obsolete files (and directories) were
> effectively removed:
>
> rsync \
> --verbose \
> --verbose \
>
I wouldn't recommend that, unless you are maintaining a VERY small directory tree,
across a fast pipe. It takes a while to determine what, if anything, needs to be sent
by rsync. You'll end up with either a continuous reinvocation of rsync, if you wait
for one to finish before starting the ne
check your /etc/rsyncd.conf.
comment out the "pid file" parameter. I assume that will fix it. then, troubleshoot
that line, IF you need to specify it.
as you're running from inetd, you don't really need a quick pid lookup to kill the
rsyncd with for refreshes and such.
Tim Conway
[EMAIL P
> "JR" == Joe Rice <[EMAIL PROTECTED]> writes:
[...]
JR> the problem at hand now is when using cron execute a rsync/ssh2
JR> command i can't figure out how to include the -o 'BatchMode yes'
JR> flag. this is what i'm trying;
JR> rsync -az --rsh="/usr/local/bin/ssh2 -o '
On Fri, Dec 15, 2000 at 09:44:44AM -0800, Dan Phoenix wrote:
> you tried --force at all? or -z?
No, I didn't, as according to the man page (and Dave's message) it
shouldn't affect much. Anyway, now I've tried, and it didn't affect.
OTOH, -z is equivalent to --compress, which I already used.
Da
11 matches
Mail list logo
