At work, I have to wait 1s~5s for dir completion in iterm2. Same mba, but at home it works instantly.
Asked
Active
Viewed 131 times
0
-
Is there any chance that your work configuration involves something longer latency, like a slow NFS-mounted file system? If this were the case, then you'd see the 1-5s delay on other kinds of file system access too, like running an ls command. – Chris Nauroth Jul 13 '12 at 07:14
-
thanks for suggestion, ls performs instantly, tried netstat and it shows surprisingly large number of connections to ports like 59991 or 65085, hmm, how could I tell which app is using that port? – ptica Jul 13 '12 at 15:30
-
Those are high-numbered ports, so it sounds like those are the ephemeral ports allocated on the client side on connection initiation. It might be interesting to check the corresponding "Foreign Address" reported for each one by netstat. You can tell which process opened the socket by running "lsof -i" or "lsof -i -n" (which may run faster by skipping reverse DNS lookups). – Chris Nauroth Jul 14 '12 at 04:08
-
its all chrome, didn't recognize the 1e100.net domain on first sight so nope, this was a false direction is there same syscall log file where I could see what is happening when I wait for tab completion of directory? – ptica Jul 18 '12 at 10:32