I believe that first one is because I already had a daemon running. Since I saw that I have been doing a ps -ef | grep rsync to make sure they are all dead before testing.
I have been doing a "rsync -av localhost::" to see if a daemon is running, is this a valid test? I did do a "strace -f rsync --daemon --no-detach 2>/tmp/rsync-$$.out" but it is about 55K and it is SEGFAULTing and dumping core(but core wasn't where I expected it to be. The core file is about 680k, I am going to attempt to crack the core file open, would anyone else like to take a look(looking at Wayne with very sad eyes) joe -----Original Message----- From: Wayne Davison [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 05, 2004 11:40 AM To: Joe Eiler Cc: [EMAIL PROTECTED] Subject: Re: group change causing failure On Tue, Oct 05, 2004 at 07:29:03AM -0500, Joe Eiler wrote: > Oct 5 06:06:12 localhost rsyncd[22781]: rsyncd version 2.6.3 starting, listening on port 873 > Oct 5 06:06:12 localhost rsyncd[22781]: unable to bind any inbound sockets on port 873 > Oct 5 06:06:12 localhost rsyncd[22781]: rsync error: error in socket IO (code 10) at socket.c(448) These mean that the "rsync --daemon" command did not start, so something else must be accepting daemon connections on your system. You'll need to diagnose that if you want to get a core-dump from the daemon (which must be run from a shell where ulimit allows core-dumps). Your output commands in the client won't tell you anything because it is already reporting that the server goes away, so the important thing is what is happening to the server. If you want to put some print commands into server code, you can run "rsync --daemon --nodetach" to see them (just be sure to output them on stderr). ..wayne.. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
