On Tue, Feb 15, 2005 at 02:33:56PM +0000, david blunkett wrote: > I don't think my daemon is chrooting but I don't undestand how this is > controlled so I can't be sure,
It uses chroot by default unless "use chroot = no" is placed in the rsyncd.conf file that your daemon is reading (which is often found in the /etc dir). If it was used, you should see a call to it in the system call output you got from the earlier run. Another thing to try (which I thought of while writing the paragraph below) is using --numeric-ids and see if that cures the problem without turning off chroot. I would be very interested in knowing what library file the program is trying to open at that point if it turns out that the chroot is causing the problem. Does the system-call trace mention it a little earlier in the output? If not, you could determine this by copying (or "bind" mounting) the /usr/lib and /lib dirs into the "path" area for the module, turning chroot back on, and using the system-call tracing you used before, note what library file it opens after chroot is called. The only library I can think of at the moment would be something in the interpretation of user IDs into user names. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
