More information: Problem with cygserver (LookupAccountSid()) -- interlocking with its clients

[Corinna Vinschen]

On Feb 13 21:56, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote:
> I was trying to figure out what SID cygserver was trying to access...
> 
> When I run ipcs without cygserver running, I see this SID is being retrieved successfully:
> 
>   359 2451151 [main] ipcs 10404 pwdgrp::fetch_account_from_windows:
>   line: <CurrentSession:S-1-5-5-0-82109179:4095:>

This is the output from ipcs process startup where Cygwin fetches
all token info.  ipcs is fetching its own logon SID which is
always translated into the above group entry with gid 4095.

> When I run ipcs with cygserver, the SID, which looks very similar,
> gives the errors and delays (it appears in the same order of
> successful retrievals w/o cygserver, among other SIDs):
> 
> 5760469 59211317 [unknown (0x14F8)] cygserver 6848 pwdgrp::fetch_account_from_windows: LookupAccountSid(S-1-5-5-0-82109179), Win32 error 1332

Cygserver is running as service here and is not part of that
session, so it doesn't know the login SID.  However, the code
inside pwdgrp::fetch_account_from_windows should translate this
into

  line: <OtherSession:S-1-5-5-0-82109179:4094:>

But even if that doesn't work as desired, it doesn't explain the 5secs
delay on these machines.  I don't se any clue here, sorry.


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin/attachments/20190214/b0309af0/attachment.sig>