CYGWIN-1.1.0 trouble: 40 to 80 sec delay if no network connection
Wed Apr 26 13:53:00 GMT 2000
Chris Faylor wrote:
> On Tue, Apr 25, 2000 at 07:30:57PM +0200, Ulrich Jakobus wrote:
> >12037 1031293 [main] pwd 1000 internal_getlogin: Domain: DEIHF
> > 3200 1034493 [main] pwd 1000 internal_getlogin: Login Server: IHFBDC
> > 3058 1037551 [main] pwd 1000 internal_getlogin: Windows Username: Jakobus
> > 3083 1040634 [main] pwd 1000 lookup_name: name : Jakobus
> >Does this information help? Even if after 10 minutes I attach the network
> >cable again, the process remains hanging.
> It may help Corinna figure out what's happening. I was hoping that you
> would actually use the command that I indicated and might provide the
> output of the "somefile" which would provide a lot more context than the
lookup_name does nothing magically. It calls LookupAccountName().
If a login server is given, it tries to call it with that login
server first. If that call failes, LookupAccountName() is called
again with login server set to NULL which is equivalent to the
So, if the system hangs that way, it is related to the OS.
I wonder what there can be changed. On one hand there will
be probably no hanging if LookupAccountName() is called only
with NULL server but on the other hand that will disallow
correct security handling of domain users.
Maybe we should use the not NULL login server parameter
only if ntsec is ON...
> >to a network printer), everything else runs fine, also the old CYGWIN-B20.1
> >did run without any trouble this way.
That code wasn't part of b20.1
Want to unsubscribe from this list?
Send a message to email@example.com
More information about the Cygwin