Re: cygwin 3.6.6-1

On Jan 15 07:30, Marco Atzeri via Cygwin wrote:
> I was able to reproduce the glitch
> 
> 1) REBOOT the Laptop
> 
> 2) Starting automatically the Services
>    /usr/sbin/cygserver
>    /usr/sbin/sshd -D
> 
> 3) open a Terminal

Through ssh or local?

> $ id
> uid=197608(Marco) gid=197121(NESSUNO)
> groups=197121(NESSUNO),545(Users),4(INTERACTIVE),66049(ACCESSO
> CONSOLE),11(Authenticated Users),15(Questa organizzazione),113(Account
> locale),4095(CurrentSession),66048(LOCALE),262154(Autenticazione
> NTLM),401408(Livello obbligatorio medio)
> Marco@DESKTOP-L2T1NQ9:~
> 
> 4) Shutdown the services, and close all processes
> 
> 5) open a Terminal
> 
> $ id
> uid=197608(Marco) gid=545(Users)
> groups=545(Users),197121(NESSUNO),4(INTERACTIVE),66049(ACCESSO
> CONSOLE),11(Authenticated Users),15(Questa organizzazione),113(Account
> locale),4095(CurrentSession),66048(LOCALE),262154(Autenticazione
> NTLM),401408(Livello obbligatorio medio)
> 
> 
> Maybe Cygserver start earlier than some Windows process that should properly
> identify the User ?

Maybe, but your user info is created from /etc/passwd, not from the
local SAM or AD.  How would a service order problem influence the
/etc/passwd info?

If you stop all Cygwin processes and restart cygserver, is the primary
group still as expected?


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