tramp-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: error 500 problem


From: Christian Lynbech
Subject: Re: error 500 problem
Date: Tue, 05 Feb 2013 20:34:29 +0100
User-agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.3.50 (darwin)

I apologize for not responding to this earlier. Unfortunately, something
happened at the ftp server, perhaps a software update, which means it
has changed behaviour.

Before, I could trigger the "500 ...not impl..." report if I called ftp
on the command line with the -n option. Now, it happily starts up with
no 500 reports no matter how I call it.

However, it now fails in a new way. I think what happens is that it
starts up in passive mode which seems to confuse ange-ftp. At least when
one does an "ls", nothing seems to happen, ftp just hangs. If I then
execute an "passive off", ls starts to produce output as I am used to.

Ange-ftp has some support for passive mode, but it expects that it
should turn it on and this fails somehow (at least in the eyes of
ange-ftp) and there is no way to actively turn passive off, as far as I
can tell from them code. The documentation of `ange-ftp-passive-host-alist'
seems to suggest one can control it in either direction.

This is no big deal, adding the hook below fixes the problem for me, I
just thought I would mention it.

    (add-hook 'ange-ftp-process-startup-hook 'ftp-configure)

    (defun ftp-configure ()
      "Configure ftp session."
      (when (string-match "xxx" ange-ftp-this-host)
        ;;proc is dynamically bound when hooks are called
        (ange-ftp-raw-send-cmd proc "passive off")))


Thanks for the looking into it.

------------------------+-----------------------------------------------------
Christian Lynbech       | christian #\@ defun #\. dk
------------------------+-----------------------------------------------------
Hit the philistines three times over the head with the Elisp reference manual.
                                        - address@hidden (Michael A. Petonic)



reply via email to

[Prev in Thread] Current Thread [Next in Thread]