Bug in rsync-3.2.1 on current
by tadgy from LinuxQuestions.org on (#55A7G)
I think I've discovered a bug in the recent upgrade of rsync in -current.
The bug only seems to show its head when you use the 'transfer logging' option in your rsyncd.conf.
To identify the problem, you can use a very basic rsyncd.conf as a test:
Code:use chroot = true
read only = true
transfer logging = true
log file = /tmp/rsyncd.log
[test]
path = /tmpThen run the daemon:
Code:rsync --daemon --config=</path/to/config>As soon as you try to access the daemon with:
Code:rsync <server-name-or-IP>::test/you get an error:
Code:rsync: didn't get server startup line
rsync error: error starting client-server protocol (code 5) at main.c(1675) [Receiver=3.1.3]When you remove the 'transfer logging' line from the daemon configuration, you can access the rsync module without problem.
I reverted the rsync package back to 3.1.3, the problem goes away.
Can anyone confirm this problem? I've been able to confirm it on slackware.uk and two other -current boxes I have here in VMs.
Cheers :)
The bug only seems to show its head when you use the 'transfer logging' option in your rsyncd.conf.
To identify the problem, you can use a very basic rsyncd.conf as a test:
Code:use chroot = true
read only = true
transfer logging = true
log file = /tmp/rsyncd.log
[test]
path = /tmpThen run the daemon:
Code:rsync --daemon --config=</path/to/config>As soon as you try to access the daemon with:
Code:rsync <server-name-or-IP>::test/you get an error:
Code:rsync: didn't get server startup line
rsync error: error starting client-server protocol (code 5) at main.c(1675) [Receiver=3.1.3]When you remove the 'transfer logging' line from the daemon configuration, you can access the rsync module without problem.
I reverted the rsync package back to 3.1.3, the problem goes away.
Can anyone confirm this problem? I've been able to confirm it on slackware.uk and two other -current boxes I have here in VMs.
Cheers :)