There are two things that bring that message. One is the inability to chroot. I think non-chrootable operating systems get their rsync configured so it never tries (and therefore, never fails). If you're on a real OS, you might be initiating the daemon as a non-root user (uid in the module doesn't matter).
The more common cause, though, is an error in the "path = /whatever" entry for a module. You can't chroot to a place that doesn't exist. Tim Conway Unix System Administration Contractor - IBM Global Services desk:3032734776 [EMAIL PROTECTED] 1. @ERROR: chroot failed rsync: connection unexpectedly closed (34 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165) > ... Any ideas? > .... -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
