FS#864 - rsync rc.d script doesn't work well.

Attached to Project: Arch Linux
Opened by Dale Blount (dale) - Friday, 30 April 2004, 21:24 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity Very Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

rsync's rc.d script sometimes fails to stop, or fails to start. rsync needs killed manually and /var/run/daemons/rsyncd needs deleted before it will start again.
This task depends upon

Closed by  Dale Blount (dale)
Monday, 13 December 2004, 18:27 GMT
Reason for closing:  Fixed
Additional comments about closing:  fixed in 2.6.3-1 (not sure if upstream or in Arch).
Comment by Judd Vinet (judd) - Monday, 03 May 2004, 18:15 GMT
Actually, I can't even get rsync to run as --daemon, except from (x)inetd.
When I run "rsync --daemon" from the commandline, it comes back right away with a 0 return code (which indicates success to the rc.d script), but there's nothing in the process table.

An strace shows this:

getsockopt(0, SOL_SOCKET, SO_TYPE, 0xbffff960, 0xbffff964) = -1 ENOTSOCK (Socket operation on non-socket)
fork() = 29572
--- SIGCHLD (Child exited) @ 0 (0) ---
wait4(-1, [WIFEXITED(s) && WEXITSTATUS(s) == 10], WNOHANG, NULL) = 29572
wait4(-1, 0xbffff644, WNOHANG, NULL) = -1 ECHILD (No child processes)
sigreturn() = ? (mask now [])
exit_group(0) = ?


Can you get it to run at all, Dale?
Comment by Dale Blount (dale) - Monday, 03 May 2004, 18:21 GMT
Hrm, I was running 2.6.0 that way... and no, my 2.6.1 refuses to run like that also. 2.6.2 has been released, maybe we should try it before digging into this any more.
Comment by Judd Vinet (judd) - Monday, 03 May 2004, 18:44 GMT
Yea, I tried 2.6.2. It does this as well. :(
Comment by Dale Blount (dale) - Monday, 03 May 2004, 19:12 GMT
There's a huge difference in socket.c right around the area that's failing for us between 2.6.0 and 2.6.1. I think one of us should report this to the rsync crew for a fix.

Loading...