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.
xinetd services are a special case, you don't start them separately, you
change the xinetd configuration (etc.xinetd.conf and files in
/etc/xinetd.d) and (re)start xinetd. xinetd usually logs information
about active services to /var/log/messages.
Running:
/etc/init.d/xinetd restart;tail -f /var/log/messages
usually helps see any immediate complaints xinetd may have about
configuration for any of the services it's supposedly been told to handle.
(FWIW, I've never really used "service"; it wasn't there when I started
getting paid working on Linux systems, it's not there at *all* on some
current distros (never mind "real" Unixes), and I've never found
anywhere I needed it. Checking a bit further, it's just a thin /bin/sh
wrapper around a call to the init script in /etc/init.d anyway.)
> 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...
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.
> Svnserve will not actually run until a request comes in.
This is correct if you're using xinetd to call svnserve. (Or inetd, or
any one of its other various replacements.)
> You would also need to take steps to make it run at
> boot time which involves putting a symbolic link in /etc/rc.d/rcn.d
> where n is the runlevel you want it to activate under (usually 2 or 3).
> However, there's probably a graphical interface that will manage all
> this for you. Under SuSE you would use yast2, but it will be different
> under Mandriva.
I can't comment on GUI-based tools to manage SysV init symlinks,
(Servers Don't Need GUIs <G>) but on any RedHat-derived systems I've met
(this includes RHEL and its rebuild-from-source clones, Fedora, SuSE,
Mandriva, and probably a few others), this can be done at the command
line with the chkconfig command.
"chkconfig --list" shows which services are to be started and stopped in
which runlevels. "chkconfig <servicename> on" sets that service to be
started according to information embedded in its init script. The only
exceptions are services handled through xinetd, which must be configured
through xinetd's configuration files and xinetd enabled.
-kgd
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 22 16:57:43 2007