I have the following configuration:
Server side:
rsync daemon running as suid root, use chroot set to false.
Client side:
rsync client setuid root (so that it can write over other suid root owned
files).
When doing a :: based rsync to the server, I'd like to have the client be
able to create/upd
> DN: You're onto something here...I just did an un-tar of the file
> containing my data (100,000 files) and saw:
>
> Solaris: 11m:28.5s
> Linux:1m26.923s
>
> That's a hell of a difference. Very peculiar how the sun FS can be so
> incredibly slow compared to Linux - and these are
pyxl wrote:
> Hi all,
>
> Tripped over a documentation bug. I'm guessing the behavior I've found
> isn't a bug in itself as it's kind of implied by chroot (unless the
> /etc/passwd db is read *before* you do the chroot call), so I'm calling
> it a documentation bug.
I pointed out the same th
> The option --delete-after does not seem to work.
>
> In a command such as
>
> rysnc -avzSH --progress --stats --delete-after remote::XYZ/dirX /export/home
> files removed from the source are not removed at the destination.
> However subsituting --delete for --delete-after does cause
Took a while to figure this one out:
Since "use chroot" defaults to true, I was having issues of UID/GID's
not mapping between servers. On AIX, if chroot() is called, the
getpwuid() calls fail, no longer being able to find /etc/passwd.
Since the that call doesn't differentiate between a 'fai
