On Fri, Dec 12, 2008 at 11:26:03AM -0500, Andrew Schulman wrote: >OK, so for us domain users, the first time we start a login shell after a >reboot, the shell can't set our $HOME correctly and we get an error message. >The >second and subsequent times, there's no error. Other events such as installing >openssh may also cause the problem one time. > >The way I figure it, since the error happens in the first login shell but not >the second, the first shell must be changing something in a file somewhere that >fixes the problem for later shells. To find out what file that might be, >here's >what I did: > >1. Rebooted. >2. Started a Cygwin 1.5 shell, and ran 'touch /tmp/timestamp'. >3. Started a Cygwin 1.7 login shell, and got the error message. >4. Went back to Cygwin 1.5, and ran > >$ find /win/c/cygwin-1.7 -newer /tmp/timestamp >/win/c/cygwin-1.7/tmp >/win/c/cygwin-1.7/var/log/wtmp >/win/c/cygwin-1.7/var/run/utmp > >So, it seems that the first login shell is updating one or more of /tmp, >/var/log/wtmp, and/or /var/run/utmp in a way that fixes the problem for later >shells. And so the cause of the problem would seem to lie in one of those >files. > >Not rock solid, but maybe useful?
I don't think anything should rely on any of those but couldn't you backup the files before starting a 1.7 shell and then restore them to see if you can reproduce the problem at will? cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
