[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svnserve issue

From: Jeremy Pereira <jeremyp_at_jeremyp.net>
Date: 2007-06-21 10:49:47 CEST

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 :-) It won't
work.

xinetd is a Unix daemon (equivalent to a Windows service) that runs
all the time and monitors ports on behalf of other programs. When a
request comes in to connect to a specific port that it knows about
(as defined in the files in /etc/xinetd.d) it accepts the connection
creating a socket and fires up the program associated with that port
and pipes input and output from the socket to/from that program. By
typing

service svn start

you are telling xinetd to start monitoring the svn port (3690).
Svnserve will not actually run until a request comes in.

Type

ps -ef | grep xinetd

at the command line and see if it gives you any output. If not,
xinetd is not running and you must start it. On most Linuxes I know
you would type something like

/etc/rc.d/init.d/xinetd start

to get it going. 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.

If you find xinetd is already running, then the problem must be in
your xinetd config somewhere. You can probably get an idea what it
is by trying to start svnserve and checking the system log for error
messages.

Having said all the above, my real advice is to find somebody who
understands about Linux daemons and xinetd and get them to help you.
Please don't be insulted but, judging by your attempt to start xinetd
as an xinetd service, your level of competence on Linux is probably
not (yet) high enough to be messing about with this stuff on your
own. You could break something quite badly if you are not careful.

>
> -----Original Message-----
> From: Jeremy Pereira [mailto:jeremyp@jeremyp.net]
> Sent: Wednesday, June 20, 2007 2:54 AM
> To: Wesley Hobbie
> Cc: users@subversion.tigris.org
> Subject: Re: svnserve issue
>
>
> On 20 Jun 2007, at 01:01, Wesley Hobbie wrote:
>
>> I have rebooted the server a couple of times.
>> netstat -an|grep 3690 returns nothing.
>
> That means the problem is in the xinetd configuration not svn.
>
> Check that
>
> a) xinetd is running and not just inetd
>
> b) you have put your svnserve xinetd config file in the right place
> (check
> /etc/xinetd.conf for includdir)
>
> c) check that your svnserve xinetd config file has the service enabled
>
> d) look for clues in the syslog file. If xinetd tried to open the
> port for
> listening and couldn't or failed to read the config file, it should
> log an
> error.
>
>>
>> -----Original Message-----
>> From: Kris Deugau [mailto:kdeugau@vianet.ca]
>> Sent: Tuesday, June 19, 2007 11:16 AM
>> To: users@subversion.tigris.org
>> Subject: Re: svnserve issue
>>
>> Wesley Hobbie wrote:
>>> I have Mandriva 2007, the subversion-server RPM package provides the
>>> /etc/xinet.d/svnserve script. By default the disable is set to
>>> 'yes'.
>>> I edited the file to set the disable to 'no' and to set the
>>> server_args to "-i -r /usr/local/repositories".
>>
>> OK, did you restart xinetd? It doesn't automatically pick up on
>> changes to its configuration.
>>
>> To see if something is listening on the right port, run "netstat
>> -an|grep 3690" and see if you get any output.
>>
>> You'll still have to use svnadmin to create repositories under
>> /usr/local/repositories before using anything, and make sure that
>> they're owned by the right user.
>>
>> -kgd
>>
>> ---------------------------------------------------------------------
>> 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
>>
>>
>
> ---------------------------------------------------------------------
> 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
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 21 11:52:19 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.