On 22 Jun 2007, at 15:57, Kris Deugau wrote:
> Jeremy Pereira wrote:
>> On 21 Jun 2007, at 01:36, Wesley Hobbie wrote:
>>> Xinetd is not running. I tried to invoke 'service xinetd start'
>>> and I get
>>> an error xinetd/bin/bash: xinetd: command not found :-(.
>> You are trying to run xinetd with xinetd by doing this :-)
>
> Er, what? "service <blah> start" is nominally equivalent to "/etc/
> init.d/<blah> start" on most Linux distros I've met. Depending on
> the age of the distro, you may need to use /etc/rc.d/init.d/<blah>
> instead - although that *won't* work at all on some - recent
> Debians, for instance. >:( Actually, the error sounds like xinetd
> isn't installed at all.
I made the mistake of going by the copy of service on my Mac OS X box
which looks to see if there is an xinetd version of the service and
starts that if it's there. I didn't bother to scroll down to what it
does if it cannot find an xinetd service because the OP was talking
about xinetd configs etc. I've just checked it again and it does fall
back to /etc/rc.d scripts after checking for an xinetd service. The
OP seemed to suggest that his service does the same thing (of
checking for an xinetd.d service first).
>
>
>
>> By typing
>> service svn start
>> you are telling xinetd to start monitoring the svn port (3690).
>
> Not quite; as I note above, this is equivalent to "/etc/init.d/svn
> start". Which won't do much more than error out if you don't have
> an init script called svn...
See above.
>
> From one of the OP's messages, I recall seeing that the Subversion
> package he installed shipped an xinetd configuration fragment,
> sensibly disabled by default. He's made the change to that file
> necessary to enable svn as an xinetd service, but xinetd itself
> seems to be misbehaving (or missing) now.
See above. The service script on my box actually seds the xinetd
file for the service you are starting and then sends a HUP to xinetd.
Anyway, judging by subsequent posts, this is definitely an xinetd
issue and the subversion list is probably not the place to trouble
shoot it.
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 26 09:50:13 2007