Got it to work by adding the 'strict modes = false' into the rsyncd.conf file. Works great now. Dave Dykstra said: > Check the log file. Diagnostic information is deliberately not > reported to the client. By default messages go to syslog() on the > server, but you can have it log to your own file instead with "log > file". The most common problem is that it requires the secret file to > not be other or group readable. > > - Dave Dykstra > > On Sat, Jul 27, 2002 at 03:04:34PM -0500, Mike Busse wrote: >> I must be missing something, but not sure what. I've configured the >> rsyncd.conf and rsyncd.secrets files per the examples I've seen and my >> authentication fails everytime. Any ideas on where I should start >> looking? >> @ERROR: auth failed on module test >> rsync: connection unexpectedly closed (88 bytes read so far) >> rsync error: error in rsync protocol data stream (code 12) at >> io.c(151) >> >> - - - - - >> >> rsyncd.conf >> >> [test] >> path = /test >> comment = test directory >> auth users = simpson >> secrets file = /etc/rsyncd.secrets >> >> - - - - - >> >> rsyncd.secrets >> >> simpson:dog >> >> - - - - - >> >> Thanks >> >> >> >> -- >> To unsubscribe or change options: >> http://lists.samba.org/mailman/listinfo/rsync Before posting, read: >> http://www.tuxedo.org/~esr/faqs/smart-questions.html > > -- > To unsubscribe or change options: > http://lists.samba.org/mailman/listinfo/rsync Before posting, read: > http://www.tuxedo.org/~esr/faqs/smart-questions.html
-- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
