howto: CVS server on FC2
miah
jjohnson at sunrise-linux.com
Tue Aug 3 12:30:09 EDT 2004
People that run pserver get owned. I suggest not doing it. You may
want to look into cvsd:
http://tiefighter.et.tudelft.nl/~arthur/cvsd/
"cvsd is a wrapper program for cvs in pserver mode. It will run 'cvs
pserver' under a special uid/gid in a chroot jail.
cvsd is run as a daemon and is controlled through a configuration
file. It is relatively easy to configure and tools are provided for
setting up a rootjail. "
Though seriously, you don't need to run a pserver to use cvs, all my
users who use cvs at work just check in through ssh.
-miah
On Tue, Aug 03, 2004 at 11:29:23AM -0400, Greg Rundlett wrote:
> I'm not a full-time admin, so I miss some of the stuff that a regular
> admin would probably be aware of. My recent upgrade to FC2 caught me by
> surprise in a couple areas. In particular, the former inetd server has
> been superceeded by xinetd in Fedora Core 2 and the configuration file
> format has completely changed. You might not notice this at all, until
> you try to setup a CVS server with remote access using the pserver method.
>
> Even the online docs at cvshome.org mention the 'old' way of doing it.
> So if you want to allow pserver access, you need something like this in
> /etc/xinetd.d/pserver:
>
> service cvspserver
> {
> disable = no
> socket_type = stream
> wait = no
> user = cvs
> group = cvs
> log_type = FILE /var/log/cvspserver
> protocol = tcp
> env = '$HOME=/home/cvsroot'
> log_on_failure += USERID
> port = 2401
> server = /usr/bin/cvs
> server_args = -f --allow-root=/usr/local/cvsrepo pserver
> }
>
> and while I'm at it, I might as well tell you that restarting xinetd is
> as simple as
> /etc/init.d/xinetd restart
> This little command is not mentioned frequently, but saves you from
> having to reboot the machine after changes are made. (I really hate
> tutorials that say: "Then restart xinetd" with no mention of how to do
> that.)
>
> - Greg
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://www.blu.org/mailman/listinfo/discuss
>
More information about the Discuss
mailing list