Unexpected behavior of HOME value

Unexpected behavior of HOME value

[Joseph L. Casale]

Looking at /etc/profile, I see the following:

  # Here is how HOME is set, in order of priority, when starting from Windows
  #  1) From existing HOME in the Windows environment, translated to a Posix path
  #  2) from /etc/passwd, if there is an entry with a non empty directory field
  #  3) from HOMEDRIVE/HOMEPATH
  #  4) / (root)
  # If the home directory doesn't exist, create it.

From a command shell:

C:\Users\jcasale>set h
HOMEDRIVE=C:
HOMEPATH=\Users\jcasale

C:\Users\jcasale>type \cygwin64\etc\nsswitch.conf
...
db_home: windows

Yet my home is generated as /home/jcasale and the directory is created
when launching a terminal. I have countless installs of Cygwin where this works
as expected and the HOME variable is constructed as expected using the
HOMEDRIVE/HOMEPATH convention.

Does anybody have an idea what could be different on this one system that
I could check?

Thanks,
jlc

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Unexpected behavior of HOME value

[Joseph L. Casale]

> Does anybody have an idea what could be different on this one system that
> I could check?

The system in question is a laptop and the behavior works as expected when
the laptop is connected to the domain, however it breaks when not. Starting
a vpn session when remote brings the behavior back to what is expected.

What does cygwin do that requires an active connection to the domain in
addition to the logic outlined in /etc/profile?

Thanks,
jlc
--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple