Re: [bug-inetutils] already connected when closed

[Alfred M. Szmidt]

   One minor niglet in ftp that has always caught me is that you can't
   reopen a closed connection without an explicit close first.  For
   instance:

   $ ftp ftp.gnu.org
   ...
   # wait a few minutes, so the connection gets closed.
   ftp> open ftp.gnu.org
   Already connected to ftp.gnu.org, use close first.

   Well, I knew that, that's why I wanted to reopen :).  If the
   connection is already closed, is there any harm in just going
   forward?

   I realize it's not exactly trivial, since it means `open' has to
   somehow get the state of the connection before issuing the message,
   but hopefully that's ultimately feasible?

Actually, it should be trivial.  We already store the state, but it
sounds as if the variable that keeps the state isn't getting flipped.

But, despite that, I cannot reproduce it:

ftp> open ftp.gnu.org
Connected to ftp.gnu.org.
220 GNU FTP server ready.
Name (ftp.gnu.org:ams): anonymous
[...]
ftp> ls
200 PORT command successful. Consider using PASV.
[...]
ftp> [waiting a few minutes for the connection to timeout]
ftp> ls
421 Timeout.
ftp> open ftp.gnu.org
Connected to ftp.gnu.org.
[...]

What version of GNU ftp are you using?