[Top][All Lists]

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

FW: still having problems

From: Hanser, Kevin
Subject: FW: still having problems
Date: Fri, 1 Dec 2000 14:05:23 -0500

I found the common answer.

I think this needs to be in the docs somewhere... since everyone is asking
it, and just about every answer I had read in the archives was something to
the effect of "put -f in inetd.conf".
Well, that doesn't do it.

I finally found an archive message that related:

Yes, its a bug (IMHO).  If you restart inetd from the command prompt it
inherits your environmental variables.  CVS gloms onto them and tries to
read the defaults in the home directory of the user you started inetd as...

So the solution is to restart, and/or not run inetd from the command line.
Shouldn't that be in the FAQ or docs somewhere?



-----Original Message-----
From: Hanser, Kevin [mailto:address@hidden
Sent: Friday, December 01, 2000 1:15 PM
To: 'address@hidden'
Subject: still having problems

Well, I looked at the archives, I looked at the FAQ, but it's still doing
I mispoke before apparently... I'm still getting the /root/.cvsignore error.

I have the -f in inetd.conf

So, according to the FAQ, this means the HOME variable is being set, right?
So what's the easiest way to fix that?  The FAQ is pretty vague, and my
first attempt at creating a shell script didn't work too well... so
specifics would be nice :)

Sorry if I'm asking some common problems, but I haven't seemed to be able to
find the common solution :)

Kevin Hanser
System Administrator

Info-cvs mailing list

reply via email to

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