Doug, you might have figured some of this out already but I want to make
sure you are fully informed:
On Fri, 2007-12-07 at 14:29 -0500, Doug Lochart wrote:
> I am going to take this approach and mix it with something else I
> thought of but I still have a few questions. I am playing with am
> rs
On Mon, 2007-12-10 at 21:53 +, Chris G wrote:
> I am using rsync version 2.6.9 protocol version 29 on a Fedora 7
> system to backup files to a network drive.
>
> rsync is getting I/O errors when copying maildir files (I'm not sure
> if the error is happening with other files but these are th
I am using rsync version 2.6.9 protocol version 29 on a Fedora 7
system to backup files to a network drive.
rsync is getting I/O errors when copying maildir files (I'm not sure
if the error is happening with other files but these are the only ones
I have found so far).
I have done some tests on
On Mon, 2007-12-10 at 22:20 +0100, Olivier Thauvin wrote:
> I don't how to really fix into rsync,
> except checking uname to get the running kernel's version.
It would seem much more direct to simply attempt the lutimes and ignore
an error of ENOSYS (Function not implemented). I don't think it's
Le lundi 10 décembre 2007, Matt McCutchen a écrit :
> On Mon, 2007-12-10 at 21:20 +0100, Paul Slootman wrote:
> > It seems that people running the Debian 2.6.9-5.1 version which has this
> > patch applied. are running into problems where rsync wants to set
> > permissions on symlinks.
>
> In the re
On Mon, 2007-12-10 at 21:20 +0100, Paul Slootman wrote:
> It seems that people running the Debian 2.6.9-5.1 version which has this
> patch applied. are running into problems where rsync wants to set
> permissions on symlinks.
In the report rsync seems to want to set mtimes, not permissions.
> The
On Tue 27 Nov 2007, Wayne Davison wrote:
>
> Starting with the 3.0.0-pre6 release, there will be a new daemon option
> available: "munge symlinks". This will allow an rsync daemon to accept
> symlinks and return them intact (with even a leading slash still there,
> which is new for a non-chroot d
On Mon, 2007-12-10 at 14:32 +0100, Eduardo Juan wrote:
> Exactly the same command shows different rsync results depending on the
> user executing the rsync.
> If I execute rsync as root I get a proper result but if I execute as
> user_x there seems to be many files that require updating.
>
> Here
Matt McCutchen wrote:
>
> If a file has vanished and there is also an error that affects the
> correctness of the transfer, the code 23 takes precedence over the code
> 24. Check rsync's output for any error messages. If there are none,
>
Indeed that is the case. I did not realize at first
On Sat 08 Dec 2007, Wayne Davison wrote:
> On Thu, Dec 06, 2007 at 07:31:44PM +0100, Olivier Thauvin wrote:
> >14366 100% 16.94kB/s0:00:00 (xfer#2357808,
> > to-check=-481/5079231)
> > Notice the negative number after "to-check".
>
> Were you using either --hard-link (-H) or --iconv
Hi
Exactly the same command shows different rsync results depending on the
user executing the rsync.
If I execute rsync as root I get a proper result but if I execute as
user_x there seems to be many files that require updating.
Here is the command I execute
/opt/local/bin/rsync -avuzhn --relati
11 matches
Mail list logo
