thank you those who made suggestions last week when I described the lag I was
experiencing when starting sh and anything that uses it (e.g. make). I
described that whenever I or a program executed "make" or "sh", there was a lag
of ~30 seconds before the programs responded WHEN I was connected to the network
AND not connected to the office's VPN. It happened because sh is
trying/re-trying to do a SAMR thing, which has to do w/ login rights.
It looks like it's trying to find the server registered as the LOGONSERVER in
Windows and fails. It retries several times before giving up and continuing its
It may be dumb and I may yet regret it, but for now, I've figured that I just
have to "set LOGONSERVER=\\MY_MACHINE" at the top of my Windows console session,
overwriting the LOGONSERVER=\\BIG_BOSS I get from Windows. When I do that, sh
just starts w/o delay. BTW, when I "set LOGONSERVER=", the same delay happens,
and then sh sets LOGONSERVER=\\MY_MACHINE...
Thought you might want to know. Also, I'm surprised I can't find references to
this complaint anywhere. Shirley, I'm not the only one who has a corporate
laptop (i.e. w/ centrally controlled access rights, hence the LOGONSERVER
setting) that I take home and connect to the home LAN and continue to develop.
Does this "fix/kludge" belong on the wiki?