-
I, too, have a variant of this problem which appears upon the final stages of updating MikTeX.
2009-05-04 10:31:57 UTC in MiKTeX
-
Hi Ulrike,
Thanks again for your time.
Is there any way in which I can help to fix this problem? I'd like to be able to as it does grate on me somewhat.
Cheers,
Christian.
2009-05-04 10:26:33 UTC in MiKTeX
-
Hello!
I, too, have had this same problem appear. With regards to ignoring it, please settle my mind: when I look at the log file of the last fully successful update run, I notice that several things happen after the fc-cache execution which, obviously, do not occur when the fc-cache failure occurs in problematic update runs. There must be some significance to the additional operations...
2009-05-03 12:12:30 UTC in MiKTeX
-
Hi again!
Regardless of the fact that my router stinks, one could imagine being in any number of situations (such as a very remote location) where a connection is poor - I've been there! In that case, it would be beneficial to have the server reset itself. I notice in the client you have an option under "connection" that is called "timeout detection:" If zero bytes are transferred within "xx"...
2007-08-27 15:43:45 UTC in FileZilla
-
Hi,
Thanks for your response. No, the server doesn't register the previous connection as disconnected.
2007-08-27 13:30:27 UTC in FileZilla
-
Hello,
My router reboots a lot, and that's another subject I'm working on elsewhere. Nonetheless, when this happens, and I'm engaged in an upload from my home machine using Client to my work machine running Server, that drop in connection seems to confuse Filezilla server and doesn't let the client side resume transferring that file. All that happens is that the client runs up to the maximum...
2007-08-27 11:01:12 UTC in FileZilla
