Hi Andrey, On Jan 17 19:48, Andrey Repin via Cygwin wrote: > Greetings, Corinna Vinschen via Cygwin! > > > On Jan 15 20:14, Takashi Yano via Cygwin wrote: > >> Hi Corinna, > >> > >> I also could reproduce the issue. > >> [...] > >> Local. In the mintty terminal opened after > >> cygserver is started. In the mintty terminal opened > >> after cygserver is stopped, the gid is as expected. > >> > >> The terminal already opened at the time cygserver is > >> started/stopped is not affected. > >> [...] > >> > If you stop all Cygwin processes and restart cygserver, is the primary > >> > group still as expected? > >> > >> No. > > > So running cygserver suppresses changing the primary group? That's > > weird, because the effect seems so arbitrary. > > Probably related, I have the following configuration in /etc/fstab : > > >> none /mnt cygdrive noacl,binary,nouser,posix=0 0 0 > >> W:/ /run ntfs acl,binary,nouser,posix=0 0 0 > >> none /tmp usertemp binary,user,posix=0 0 0 > > (Eyes on the last entry - the user-specific /tmp.) > > After some random reboot, the user's mount point is not %LocalAppData%\Temp, > as you would expect, but %SystemRoot%\Temp. > > Stopping and restarting cygserver solves the issue for all subsequent logons.
I tried this multiple times, but I can't reproduce this issue. I doubt that this is in any way related to the primary group issue. cygserver caches account info, but it doesn't cache mount points. Actually, mount points are stored in a user account specific shared memory. Cygserver, running under the SYSTEM account, is storing its own mount points in its own share mem for the user SYSTEM, and it doesn't cache this for any other user. There's no mechanism to exchange mount point info between cygserver and user Cygwin processes. Corinna -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
