[Top][All Lists]

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

RE: Strange problem /dev/null/.cvsignore

From: Matthew Herrmann
Subject: RE: Strange problem /dev/null/.cvsignore
Date: Wed, 3 Aug 2005 11:12:30 +1000

Thanks Derek, here's some more info on this:

We have isolated it down to the following:

* Successful user account ("faredge") -- only part of the /etc/passwd file
is scanned when we attach a tracing process to the xinetd cvs process.
Following that, /home/faredge/.cvsignore is read.

* Unsuccessful user account ("matthew") -- all of the /etc/passwd file is
scanned. The $HOME value for user "apache" is being used, which is

As I mentioned earlier, the only tangible difference between these two
accounts is the name. My question is: why would cvs use the home drive for a
completely different account for one login, but work correctly for other


-----Original Message-----
From: Derek Price [mailto:address@hidden 
Sent: Wednesday, 3 August 2005 4:32 AM
To: Matthew Herrmann
Cc: address@hidden
Subject: Re: Strange problem /dev/null/.cvsignore

Matthew Herrmann wrote:

>cvs update: cannot open /dev/null/.cvsignore: Not a directory

Whatever account you have logged in as has "/dev/null" set as its home


Get CVS Support at <>!

reply via email to

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