[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Too Frequently Asked Question of info-cvs mailing list
From: |
Anders Knudsen |
Subject: |
Re: Too Frequently Asked Question of info-cvs mailing list |
Date: |
Mon, 29 Jan 2001 10:34:13 -0700 |
This may be worth putting into the FAQ (I leave it up to you.):
If you are using xinetd you can use the "passenv" attribute.
"man xinetd.conf" explains this attribute.
FYI, following is my cvspserver file for xinetd. It works great, and I
avoid the $HOME problem.
By putting nothing for "passenv" cvs is started without any env.
I don't think that "inetd" has an equivalent attribute, but I'm not sure.
$ cat xinetd.d/cvspserver
service cvspserver
{
socket_type = stream
protocol = tcp
wait = no
user = root
passenv =
group = cvsroot
only_from = 192.168.200.0
log_type = FILE /var/log/xinetdlog
server = /usr/bin/cvs
server_args = -f --allow-root=/home/cvsroot pserver
log_on_success += USERID DURATION
log_on_failure += HOST USERID
disable = no
}
-Anders.
At 01:19 PM 1/28/2001 -0500, Larry wrote:
Alexey Mahotkin writes:
>
> A: Workaround: You could create small .sh-file:
That may not work -- the problem might well be that there's no -f global
option on the pserver line in inetd.conf rather than that $HOME is set
in the environment.
> This is caused by misfeature in CVS. :pserver: does not have home
> directory and should not try to use it. There exist patches that fix
> that behaviour, if you wish to get rid of that problem once and for
> all.
This is misleading -- the user pserver is running on behalf of has a
home directory and pserver may well want to use it. And note that the
current development version ignores $HOME when running as a server.