From: Scott Atwood <atwood@CS.Stanford.EDU>
To: cygwin@cygwin.com
Subject: Re: 30 second startup delay on Cygwin programs from SYSTEM account
Date: Thu, 25 Oct 2001 18:08:00 -0000 [thread overview]
Message-ID: <200110260107.SAA16481@Xenon.Stanford.EDU> (raw)
In-Reply-To: <no.id>
> I am running Cygwin 1.3.3 on Windows 2000 Server, and I have noticed a
> strange problem. Whenever I try to start a Cygwin process from a windows
> cmd shell as the user SYSTEM, there is an approximately 30 second delay
> before the process starts. If I have started a bash process as SYSTEM,
> subesequent processes started from within bash start normally. Cygwin
> processes always start normally for the Administrator user.
>
> I have looked in the FAQ and the documentation, searched Google, and
> searched the Cygwin mailing list archive, and I couldn't find any
> mention of this problem.
I ran "strace bash" as user SYSTEM and here is an excerpt of the output.
2949 226918 [main] bash 1428 internal_getlogin: GetUserName() = SYSTEM
30450200 30677118 [main] bash 1428 internal_getlogin: Domain: (null), Logon Serv
er: CHARON, Windows Username: SYSTEM
The output paused for about 30 seconds after the first line printed, and
before the second line printed.
Here is the same section of "strace bash" for user Administrator:
2980 255639 [main] bash 1708 internal_getlogin: GetUserName() = Administrator
831 256470 [main] bash 1708 internal_getlogin: User: Administrator, Domain: C
HARON, Logon Server: CHARON
305105 561575 [main] bash 1708 internal_getlogin: Domain: CHARON, Logon Server:
CHARON, Windows Username: Administrator
And again as user SYSTEM from within an already running bash process:
1435 282240 [main] bash 1212 internal_getlogin: GetUserName() = SYSTEM
365580 647820 [main] bash 1212 internal_getlogin: Domain: (null), Logon Server:
CHARON, Windows Username: SYSTEM
I downloaded the cygwin 1.3.3 source code, and I was able to isolate these
lines of output as coming from the internal_getlogin method in the
winsup/cygwin/uinfo.cc file, somewhere between line 41 and 114.
I don't know enough about the structure of the cygwin DLL to be able to
isolate the problem any closer than that, since there are many method
calls in this region of the code.
-Scott
--
Scott Atwood
atwood@cs.stanford.edu
PGP key fingerprint: 2852 FAE0 B0BB FE52 7002 1019 4D48 78B3 6FF0 A89F
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2001-10-25 18:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <no.id>
1998-04-06 4:08 ` Problem with new-cygwin.dll.gz ? Geoffrey Noer
1998-04-06 17:20 ` Problem with new-cygwin.dll.gz - Not here there isn't Guy Gascoigne - Piggford
1998-04-08 16:25 ` Problem with new-cygwin.dll.gz Emil Hallin
1999-07-01 23:09 ` A new user of cygwin and unix based system Glenn Spell
1999-07-02 9:06 ` Chris Faylor
1999-07-31 18:34 ` Chris Faylor
1999-07-31 18:34 ` Glenn Spell
1999-07-02 9:45 ` Glenn Spell
1999-07-31 18:34 ` Glenn Spell
2000-04-20 19:03 ` a bug Chris Faylor
2001-09-17 21:40 ` Unwanted compiler warnings with w32api Shayne Steele
2001-09-17 21:56 ` Shayne Steele
2001-10-25 18:08 ` Scott Atwood [this message]
2001-10-29 15:56 ` 30 second startup delay on Cygwin programs from SYSTEM account Robert Collins
2001-11-05 14:39 ` Scott Atwood
2001-11-05 15:04 ` Robert Collins
2001-11-05 15:13 ` Scott Atwood
2001-11-11 8:26 ` Cygwin homepage has problems Shayne Steele
2003-01-16 19:15 ` Command-line email? dmeans
2003-01-17 10:09 ` Dr. Volker Zell
2004-07-16 8:36 ` mmap bug on Windows 9x Anton Ertl
2004-07-16 15:03 ` Corinna Vinschen
2001-10-25 16:15 30 second startup delay on Cygwin programs from SYSTEM account Scott Atwood
2001-10-26 6:47 ` Larry Hall (RFK Partners, Inc)
2001-10-30 13:48 Heribert Dahms
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200110260107.SAA16481@Xenon.Stanford.EDU \
--to=atwood@cs.stanford.edu \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).