[CentOS] CentOS6 xinetd failure

2013-12-10 Thread Lars Hecking
One thing I have noticed on CentOS6 is that rsync via xinetd never works after a reboot. It always takes an additional, post-reboot service xinetd restart to get it going. That has been the same for all revisions up to and including 6.5, and I've seen it on more than just machine. While I

Re: [CentOS] CentOS6 xinetd failure

2013-12-10 Thread John Doe
From: Lars Hecking lheck...@users.sourceforge.net One thing I have noticed on CentOS6 is that rsync via xinetd never works after a reboot. It always takes an additional, post-reboot service xinetd restart to get it going. That has been the same for all revisions up to and including 6.5, and

Re: [CentOS] CentOS6 xinetd failure

2013-12-10 Thread Helmut Drodofsky
see http://lists.centos.org/pipermail/centos/2013-July/135847.html I have had the same problem and I will never understand, why this is unchanged up to now. Alternative: - erase nfs - change sequence number in /etc/rc3.d best regards Helmut Viele Grüße Helmut Drodofsky Internet XS Service

Re: [CentOS] CentOS6 xinetd failure

2013-12-10 Thread Lars Hecking
Is there any way to debug this? I suspect it needs to be debugged during reboot since the service starts up fine later. Address already in use = check what is listening on port 873? In the rsync xinetd conf it says IPv6 here... service rsync { disable = no flags

Re: [CentOS] CentOS6 xinetd failure

2013-12-10 Thread Lars Hecking
Helmut Drodofsky writes: see http://lists.centos.org/pipermail/centos/2013-July/135847.html I have had the same problem and I will never understand, why this is unchanged up to now. Excellent, thanks! Now I know how to work around it. I've seen this happening before, on CentOS5, when