On 12 Jun 2001, Dave Dykstra <[EMAIL PROTECTED]> wrote:
> > 2001/06/11 12:09:46 [20857] rsyncd version 2.4.6 starting
> > 2001/06/11 12:09:46 [20857] bind failed on port 873
Incidentally, this message now shows strerror(), so it should be more
obvious in 2.4.7 whether the problem is EACCES (not root) or EINVAL
(in use).
> > 2001/06/11 12:09:46 [20857] transfer interrupted (code 10) at
> > socket.c(254)
> >
> > It's odd cause I can actually start rsync without adding it to
> > services or inetd.conf, just by tiping rsync --daemon at the prompt.
> >
> > Any guesses??
If you're running from inetd, then rsync should not be trying to bind
to a port itself! inetd should bind the socket for you. How
strange...
Can you please post the relevant line from inetd.conf?
>
> You don't mention if you've eliminated the obvious guesses:
> Guess 1: something else is already listening on the port. Could be you
> had it in inetd.conf, then deleted it, but didn't send a kill
> signal to inetd. Check netstat.
> Guess 2: you're not running as root.
--
Martin
PGP signature
