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
/dev/null.
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
accounts?
Thanks,
Matt
-----Original Message-----
From: Derek Price [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 3 August 2005 4:32 AM
To: Matthew Herrmann
Cc: [email protected]
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
directory?
Derek
Get CVS Support at <http://ximbiot.com>!
_______________________________________________
Info-cvs mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/info-cvs
