Rsync uses the fork() system call to spawn a process that does most of the
actual work. I believe the first message is from the parent and the second
message is from the fork()'d child. Many of the variables in rsync are
global so they can be copied from the parent to the child process, you may
wi
> never seen a file created with a newline in the filename
> (except, perhaps as a test). The newline in filename issue
And in security exploits :-) Given a newline-based format, one *must*
quote or deny newlines in filenames, not assume they're rare. (No
obvious reason not to use URL-style %
On Mon, Jul 08, 2002 at 05:40:58PM -0400, Lenny Foner wrote:
> Date: Mon, 8 Jul 2002 21:18:18 +0800
> From: Adrian Ho <[EMAIL PROTECTED]>
>
> If the sender's/receiver's cwd is guaranteed to be the root of the
> corresponding rsync'd hierarchies, then yes, relative paths would
>
Looking at this I see a few problems:
> wrote 142 bytes read 1068 bytes 23.05 bytes/sec
This corresponds to about 1 ls, and no data reading.
> total size is 668499968 speedup is 552479.31
The speedup is UNREAL, unless you consider that you may have the wrong
path, and you didn't get ANYTHIN
On Wednesday 03 July 2002 20:10, Eric Ziegast wrote:
> > I am two Linux servers with rsync server running on both. Now I am
> > replicating directories in both servers with the command rsync -avz
> > My requirement is, if I made any changs in the first server, say server
> > A, I want to se
Date: Mon, 8 Jul 2002 21:18:18 +0800
From: Adrian Ho <[EMAIL PROTECTED]>
If the sender's/receiver's cwd is guaranteed to be the root of the
corresponding rsync'd hierarchies, then yes, relative paths would
suffice.
>
> UPDATEfoo/
> CREATEfoo/bar1
> UP
On Mon, Jul 08, 2002 at 05:56:57PM +1000, Martin Pool wrote:
> Any thoughts on whether this should go in? I can see arguments either
> way. It seems like we ought to think about whether it would be better
> to do it as part of a generalized --chmod or --chmod-backup facility.
>
>
>
> On 21 Ju
On Mon, Jul 08, 2002 at 08:52:29AM -0700, Eric Horst wrote:
>
> Hi, I'm new around here and thought I'd join the discussion. Hope that's
> ok.
>
> > I'm inclined to push for more flexibility with:
> >
> > --post-process=
> > Runs on the receiver just before rsync exits.
> > is passe
The idea of the rsync client executing programs has been descussed before
and rejected because it could easily be done by an external program if
rsync simply passes it filenames. The only case I can see for having rsync
execute programs is in the daemon; that was once approved in principle but
no
Hi there,
I've a problem with rsync - see below.
(by the way: I'm using rsync since 2 years now, good work!)
my environment:
- linux, 2.4, Dual-PIII-1.2GHz, 1 GB RAM. more of these machines.
- rsync 2.5.5
- openssh 3.3
the machines are on a lan, so bandwith is not a problem.
I sync large dire
Hi, I'm new around here and thought I'd join the discussion. Hope that's
ok.
> I'm inclined to push for more flexibility with:
>
> --post-process=
> Runs on the receiver just before rsync exits.
> is passed a list of fully-qualified pathnames on
> stdin (one per line) that have
On Mon, Jul 08, 2002 at 09:18:18PM +0800, Adrian Ho wrote:
> On Mon, Jul 08, 2002 at 03:52:16AM -0700, jw schultz wrote:
> > Also the path should not be fully qualified but instead should match
> > that of the commandline with cwd the same as the rsync launch.
>
> If the sender's/receiver's cwd i
On Mon, Jul 08, 2002 at 03:52:16AM -0700, jw schultz wrote:
> However, if it lists created, modified and deleted files it will need
> to differentiate. It should instead list the files and the action.
Well, yeah, that's probably more useful in general. 8-)
> Also the path should not be fully q
On Mon, Jul 08, 2002 at 06:01:48PM +0800, Adrian Ho wrote:
> On Mon, Jul 08, 2002 at 05:37:13PM +0800, Adrian Ho wrote:
> > I'm inclined to push for more flexibility with:
>
> Actually, make that:
>
> --post-send=
> --post-recv=
> Runs on the sender/receiver just before rsync exits.
>
On Mon, Jul 08, 2002 at 05:37:13PM +0800, Adrian Ho wrote:
> I'm inclined to push for more flexibility with:
Actually, make that:
--post-send=
--post-recv=
Runs on the sender/receiver just before rsync exits.
is passed a list of fully-qualified pathnames on
stdin (one per line)
On Mon, Jul 08, 2002 at 05:56:57PM +1000, Martin Pool wrote:
> Any thoughts on whether this should go in? I can see arguments either
> way. It seems like we ought to think about whether it would be better
> to do it as part of a generalized --chmod or --chmod-backup facility.
I'm inclined to pu
Any thoughts on whether this should go in? I can see arguments either
way. It seems like we ought to think about whether it would be better
to do it as part of a generalized --chmod or --chmod-backup facility.
--
Martin
On 21 Jun 2002, Dan Stromberg <[EMAIL PROTECTED]> wrote:
> Included bel
Hello,
I give you a little log format sample that I receive on the
/var/log/rsyncd.log on the master server that receive data from
a client :
2002/07/07 19:48:29 [15226] rsync to cfps from UNKNOWN (153.109.45.20)
2002/07/07 20:17:42 [15257] wrote 32 bytes read 1584410 bytes total size
51681797
18 matches
Mail list logo
