I saw this error message before, and I found that the problem was at the
server end where I am sending data. If the module defined in rsyncd.conf has
directory with no write permission or directory doesn't exist,you will get
this error message. There might be other problem also. (keep watching
"rsync.log" file for more info)
-sanjeev
-----Original Message-----
From: Martin Pool [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 25, 2000 2:42 AM
To: Jon Erick Ween
Cc: [EMAIL PROTECTED]
Subject: Re: chroot error
On 24 Oct 2000, Jon Erick Ween <[EMAIL PROTECTED]> wrote:
> Hi
>
> Does anybody know why rsync would quit due to a "chroot failed" error? I
was
> syncing away just fine (clean sync for a virgin tree) and then got a bunch
> of "cant open x, file or directory does not exist" errors and finally the
> "chroot failed" error.
I can't think of anything specific without more information. I'm
going to make that message more specific in future versions. Could it
be a problem in your OS?
--
Martin Pool, Linuxcare, Inc.
+61 2 6262 8990
[EMAIL PROTECTED], http://www.linuxcare.com/
Linuxcare. Support for the revolution.
