RE: cvs with xinetd

[Gianni Mariani]

I don't remember my reasoning behind using env = HOME= vs passenv = but a
guess is that you specifically want to unset the HOME environment variable.
"passenv" (at another guess) is very restrictive ( passing only the tne
variables listed ) and "env" can explicitly set (or unset i.e. HOME=)
variables.

So, at another guess, using "passenv=" agessively unsets all environment
variables.


-----Original Message-----
From: address@hidden [mailto:address@hidden Behalf Of
Adam W. Montville
Sent: Thursday, May 03, 2001 5:55 AM
To: Info-Cvs; Larry Jones
Subject: RE: cvs with xinetd


What I found on http://www.xinetd.org/ is the following:

service cvspserver
{
        socket_type             = stream
        protocol                = tcp
        wait                    = no
        user                    = root
        passenv         =
        server          = /usr/bin/cvs
        server_args             = --allow-root=/cvs/isaac pserver
}

This configuration works wonderfully, although I'm not entirely sure what
leaving "passenv" null actually does.

Adam


-----Original Message-----
From: Larry Jones [mailto:address@hidden
Sent: Wednesday, May 02, 2001 11:08 PM
To: Gianni Mariani
Cc: Adam W. Montville; Info-Cvs
Subject: Re: cvs with xinetd


Gianni Mariani writes:
>
>         env              = HOME=

Again, it is much better to use:

        passenv = PATH

(plus whatever other environment variables you want to pass to the
server but *not* HOME) instead.

-Larry Jones

In short, open revolt and exile is the only hope for change? -- Calvin