#130 Windows Access Control Causing Slow Starts

closed
nobody
MSYS (18)
5
2011-02-25
2011-01-25
Anonymous
No

I understand that MSYS uses Windows file access control mechanisms.
My problem is I'm on a domain machine with the authentication server half-way across the world.
If I have a live network connection to my LOGONSERVER, it takes several seconds to get the shell started (and every command in a make is doing the same).
Looking at the traffic in wireshark, I'm communicating with my remote domain server apparently to get authentication to do anything file related.

I can try to change/delete my LOGONSERVER environment variable...but that doesn't stop anything...just ends up in a bunch of bad NBNS requests and timeouts on the connections....still slowness and pauses.

If I disconnect my network connection...all is good and fast.

I realize this may be more of a windows issue, but is there any way of stopping this domain server access (when network connected) on every command?

Discussion

  • Earnie Boyd

    Earnie Boyd - 2011-01-26
    • milestone: --> Waiting_user_response
    • status: open --> pending
     
  • Earnie Boyd

    Earnie Boyd - 2011-01-26

    The slowness is more likely due to mapped drives than to the logon server. One option is to try make sure that one process remains open during the execution of the build. Also, the anti-virus software may be reporting results back to the remote domain server slowing the result back to MSYS.

     
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 30 days (the time period specified by
    the administrator of this Tracker).

     
  • SourceForge Robot

    • status: pending --> closed
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks