> > I get the following immediately after the command:
> >
> > recv_generator: unlink lib: Not privileged
> > recv_generator: unlink lib: Not privileged
>
> That's pretty strange. It should only hit that line when it's
> deleting a file to make way for a directory, and it should never be
> ca
ously
shot .
Oh well, on to the fun stuff that I still remember how to fix...
Todd
> -Original Message-
> From: Martin Pool [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 08, 2000 8:28 PM
> To: Todd Robinson
> Cc: [EMAIL PROTECTED]
> Subject: Re: transfer interrupte
On 8 Nov 2000, Todd Robinson <[EMAIL PROTECTED]> wrote:
> I get the following immediately after the command:
>
> recv_generator: unlink lib: Not privileged
> recv_generator: unlink lib: Not privileged
That's pretty strange. It should only hit that line when it's
deleting a file to make way
On 8 Nov 2000, Todd Robinson <[EMAIL PROTECTED]> wrote:
> Applied the patch and re-built, part way through the make I got these
> errors:
>
> UX:acomp: WARNING: "socket.c", line 221: argument is incompatible with
> prototype: arg #5
> UX:acomp: WARNING: "socket.c", line 264: argument is incom
On 8 Nov 2000, Todd Robinson <[EMAIL PROTECTED]> wrote:
> Applied the patch and re-built, part way through the make I got these
> errors:
>
> UX:acomp: WARNING: "socket.c", line 221: argument is incompatible with
> prototype: arg #5
> UX:acomp: WARNING: "socket.c", line 264: argument is incomp
On 8 Nov 2000, Todd Robinson <[EMAIL PROTECTED]> wrote:
> > That's pretty strange, for two reasons: as far as I knew, everything
> > ought to go to stderr, stdout, or the log file. When you say
> > "console", do you mean it comes out in your current window, or it goes
> > to the actual VGA adapt
> That's pretty strange, for two reasons: as far as I knew, everything
> ought to go to stderr, stdout, or the log file. When you say
> "console", do you mean it comes out in your current window, or it goes
> to the actual VGA adapter/serial console of the server?
In the current window the rsync
On 8 Nov 2000, Martin Pool <[EMAIL PROTECTED]> wrote:
> > The unlink message went to the console not the file, it was:
> >
> > unlink rsync-2.4.6/lib : Not privileged
>
> That's pretty strange, for two reasons: as far as I knew, everything
> ought to go to stderr, stdout, or the log file. Wh
On 16 Oct 2000, Todd Robinson <[EMAIL PROTECTED]> wrote:
> > If so, please do a `ls -l' to show the permissions, and post the
> > results.
>
> The permissions are varied. But, the local machine from where I am getting
> the 'unlink' messages, I am executing rsync as root.
OK, thanks. However
how do i unsubscribe from the list?
thanks!
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Martin Pool
Sent: Wednesday, November 08, 2000 4:35 PM
To: Todd Robinson
Cc: [EMAIL PROTECTED]
Subject: Re: transfer interrupted, and Not privileged errors
On 11 Oct 2000, Martin Pool <[EMAIL PROTECTED]> wrote:
> On Tue, Oct 10, 2000 at 09:39:20AM -0400, Todd Robinson wrote:
> > rsync to marktg from fdops2
> > wrote 32 bytes read 2439031 bytes total size 13862565
> > transfer interrupted (code 102) at main.c(432)
>
> At least on Linux, 102 is
Pardon if this posts twice, sent it to the rsync-admin first...
When doing a 'rsync -avz /tmp fdops3::marktg' I observe the following
behavior:
Sending machine lists files as they are sent, but then towards the end, I
start getting
unlink tmp/fred/spn1 : Not privileged
This occurs for every s
12 matches
Mail list logo