I did some debugging tonight and it appears that this problem is being
caused by "200 PORT command successful" messages coming from the cygwin FTP
client after the get command is issued. EFS was thinking that this
response meant the get command was done when in fact it had only just
started. I fixed it by adding this to my custom.el file:
(quote (("" . "^110 \\|^125 \\|^150 ")
("^ls \\|^put \\|^get \\|^append \\|passive" .
"^500 EPSV not understood")
("^ls \\|^put \\|^get \\|^append " .
"^200 PORT command successful"))) t)
Only the last entry is new. I have no idea what changed in efs or cygwin
to make this start failing since I'm pretty sure it worked until recently.
Mike Alexander <mailto:mta＠arbortext.com>
Arbortext, Inc. +1-734-997-0200
--On Thursday, May 24, 2001 10:10 AM +0200 Jerker Haglund
> I've been having trouble with this on a machine running the
> build of XEmacs (from the current CVS trunk) on Windows NT 4.0 using
> the cygwin ftp client. When I try to open a file on an FTP server
> (I've tried several and it doesn't seem to matter which server) the
> file is truncated at a random location a few thousand bytes into the
> file. If you look at the ftp log everything seems to be ok, but efs
> doesn't seem to wait for the file to be transfered before using the
> result. I've tried to debug this a bit, but haven't learned very
> much. Has anyone else seen problems like this?
I've noticed that EFS says 'Done' long before the result is visible.
That's with an ADSL connection, native 21.4.3 on Win2k. If it
doesn't wait properly, this could explain why the experimental
EFS seems shaky, with both cygwin and windows ftp. Things fail
1st time, try again (when things are cached) and it works.
> I'm connected via an ISDN line so ftp transfers are not too fast.
> This might have something to do with it. I'll try it on other
> machines with faster net connections and see if that affects things.
> If I can provide any more information let me know.