info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Multiple Repos with xinetd (in a seperate file)


From: Jim Hyslop
Subject: Re: Multiple Repos with xinetd (in a seperate file)
Date: Fri, 14 Apr 2006 20:44:38 -0400
User-agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Troubled User wrote:
> I currently have xinetd running with cvspserver.  For each CVSROOT i
> have to edit the xinetd conf file and add another --allow-root flag.
> 
> I have read somewhere that I can tell xinetd (or cvs, i cant
> remember) to look at another file.
> 
> IE. in xinetd i would specify a filename that would contain a list of
> my cvs repos.  the file could look something like this:
> 
> /usr/local/cvs_test /usr/local/cvs_my_repo 
> #/usr/local/cvs_disabled_repo /usr/local/cvs_another_repo
> 
> Does anyone know how to do this, or have another cvs management
> solution?

You haven't said exactly why you find this a pain. I'm guessing that you
have to change the list of supported repositories, and don't want to
have to restart the xinetd daemon each time you change xinetd.conf (I'm
not extremely well-versed in UNIX - am I correct in assuming you have to
restart xinetd whenever you change the .conf file?).

You could use the workaround for xinetd versions that have a very
limited command line: just have xinetd invoke a script which supplies
all the arguments. You will still have to type in '--allow root' for
each repository, but it will be easier to maintain.

- --
Jim Hyslop
Dreampossible: Better software. Simply.     http://www.dreampossible.ca
                 Consulting * Mentoring * Training in
    C/C++ * OOD * SW Development & Practices * Version Management
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEQEHoLdDyDwyJw+MRAqP4AKDhCVPNqZtI4+Nbdzhjotik63ZdaACgs+B1
OBL4nbz1rnvrtUEXSfmBuLg=
=v6+C
-----END PGP SIGNATURE-----





reply via email to

[Prev in Thread] Current Thread [Next in Thread]