I've got a puzzling issue, thought I'd ask to see if anyone else has had
a similar problem.
We have two machines that are synchronizing directories one way - the
data files are being pushed from the source to the destination. On the
destination system, I have multiple (6) modules set up to receive
On Fri, Sep 10, 2004 at 12:05:37PM +0200, Kick Claus wrote:
> rsync stream tcp nowait publish /usr/bin/rsync rsyncd --daemon --port 1234 .
As indicated in the rsyncd.conf man page, the command should be this:
rsync stream tcp nowait publish /usr/bin/rsync rsyncd --daemon
(I changed "ro
On Fri, Sep 10, 2004 at 02:47:28PM +0200, Paul Slootman wrote:
> Yes, I just checked out what -a does exactly.
> Why oh why does -a not preserve hard links?
Because it used to be horribly inefficient in memory usage and in extra
bytes transferred over the wire (it bloated memory use in the receive
I almost always use "-u" with rsync so that I don't overwrite remote
files that have changed. The only way to get rsync to tell me which
remote files are "newer" is to use a double-v (-vv), which produces way
more output than I care to see. (In true Unix fashion, I don't care to
see what was done
Date: Fri, 10 Sep 2004 13:35:30 +0200
From: Paul Slootman <[EMAIL PROTECTED]>
Hello Paul,
>> we would like to use rsync (2.6.2 manualy patched and recompiled) in
daemon
>> mode spawned by inetd (Solaris 5.8 Environment).
>Hmm, I don't know whether this is supported...
Hm, then lets simply wait
On Fri 10 Sep 2004, John Van Essen wrote:
> >
> > rsync -avz --bwlimit=5000 /extra/pub/ 192.168.1.73::pub
>
> To preserve hardlinks, you need to include the -H option (it's
> not implied in the -a option).
Yes, I just checked out what -a does exactly.
Why oh why does -a not preserve hard lin
I am needing to know what files were transferred. However in the log it is not showing me. I am only getting the --status log section at the end.
Here is my command:
${RSYNC} -a --delete -vv -z --stats ${SOURCE}/ ${BASEDIR}${SVR}/${BUID}/ >> ${LOG}/${BUID}_${DATE}.txt
now one would thin
On Fri, 10 Sep 2004, Paul Slootman <[EMAIL PROTECTED]> wrote:
>
> I'm using 2.6.3pre1 to transfer a rather large Debian archive
> (126GB, more than 30 million files). It contains about 450 daily
> snapshots, where unchanged files are hardlinked between the snapshots
> (so many files have hunderds o
On Fri 10 Sep 2004, Kick Claus wrote:
>
> we would like to use rsync (2.6.2 manualy patched and recompiled) in daemon
> mode spawned by inetd (Solaris 5.8 Environment).
Hmm, I don't know whether this is supported...
> rsync stream tcp nowait publish /usr/bin/rsync rsyncd --daemon --port 1234 .
Hello,
we would like to use rsync (2.6.2 manualy patched and recompiled) in daemon
mode spawned by inetd (Solaris 5.8 Environment).
/etc/services:
rsync 1234/tcp#RSYNC daemon
/etc/inet/inetd.conf:
rsync stream tcp nowait publish /usr/bin/rsync rsyncd --daemon -
I'm using 2.6.3pre1 to transfer a rather large Debian archive
(126GB, more than 30 million files). It contains about 450 daily
snapshots, where unchanged files are hardlinked between the snapshots
(so many files have hunderds of links).
It's been running for some time now, and I found that while i
On Thu, Sep 09, 2004 at 11:46:48AM +0200, Essyug wrote:
Why does the rsync running on the client must be root ? It just has to
send the name of the owner of the file to the server which will chown
it.
I misread it as the receiver at first glance, thus the confusion.
You're right that the sender
12 matches
Mail list logo
