[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: acquiring wrong home directory
From: |
Larry Jones |
Subject: |
Re: acquiring wrong home directory |
Date: |
Thu, 29 Oct 2009 12:27:18 -0400 |
Thomas Wolff writes:
>
> in src/sanity.sh, it says explicitly:
> # CVS looks at the home dir from getpwuid, not HOME (is that correct
> # behavior?), so this is hard to test and we won't try.
Don't trust comments in the sanity check, use the source, Luke!
> In src/filesubr.c, function get_homedir, using $HOME depends on the flag
> !server_active -
> while I didn't dig into this deeper and don't know when exactly this
> flag is set, it does not look proper and I suspect this to be the cause
> of the problem
That flag is only set when CVS is running as a server (e.g., pserver).
In that case, the very idea of a "home" directory is pretty nebulous.
Like I said, it works fine on other Unix and Unix-like systems:
bash-2.02$ export HOME=/tmp/foo
bash-2.02$ cvs login
Logging in to :pserver:scjones@thor:2401/public/CVS
CVS password:
cvs login: warning: failed to open /tmp/foo/.cvspass for reading: No
such file or directory
cvs [login aborted]: could not open /tmp/foo/.cvspass for writing: No
such file or directory
It seems that cygwin is somehow special-casing getenv("HOME") rather
than just returning the value set in the environment like one would
expect.
--
Larry Jones
I take it there's no qualifying exam to be a Dad. -- Calvin