Opened 16 years ago
Last modified 16 years ago
#1315 closed Bug report
v3 hangs or won't load
|Reported by:||warriorwolf||Owned by:|
|Keywords:||Cc:||warriorwolf, Tim Kosse|
|Component version:||Operating system type:|
|Operating system version:|
Bear with me, since I have to give a good context for the problem. I work for a small company that maintains a working copy of it's website on the network (set up as network drive G:), then sends the changes to the live site via FTP. (I recently installed Filezilla 184.108.40.206 and love it.) This company is very closely associated with a university, and we use their network since they have such vast resources, though that means I have no control over the quality/performance of their network.
So, here's the goods: I came in, tried to connect filezilla through the site manager to the ftp, which is configured to bring up the network drive (g:\) on and the public_html on the live site, and it hung. I killed it, figuring the program was just being bitchy, but then when I restarted it, nothing came up except for a running filezilla process. In any case, I found the source of the problem: the office has been having problems accessing the network drive, and it was being entirely non-responsive, and since filezilla goes right back to where I was, it was trying to bring up G:, but stalling (without even loading the interface). My thinking is, this might be easily fixed by adding a timeout function where it just gives up trying to bring up the local directory and defaults to something safe, say "My Computer". Just my thinking, someone else might have a better solution?
Change History (2)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
You're kidding! Go figure... Well, it's a good excuse to start hosting the files locally. *Evil grin* Thanks!
This needs to be fixed in Windows itself since the API functions used to access directories don't have timeout parameters.