2

I just tried to access our FTP server via the command-line FTP client on my new M2 Mini.

And it gives an immediate "Killed 9" message.

On my 2017 iMac (Catalina):

(Note that the ftp server domain name "has been changed to protect the innocent")

ftp xxx.com
Connected to xxx.com.
220 (vsFTPd 3.0.2)
Name (xxx.com:foo): yyy
331 Please specify the password.
Password: 
230 Login successful.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp>

On an AS/400 in the cloud:

  Connecting to host XXX.COM at address 35.174.190.169 using port 21.
  220 (vsFTPd 3.0.2)                                                      
> yyy                                                                
  331 Please specify the password.                                        
  230 Login successful.                                                   
  UNIX Type: L8                                                           

On my M2 Mini:

ftp xxx.com
Killed: 9

On my M2 Mini, trying to connect to an FTP server on the same LAN, only one desk over, server name in my host table, that also works just fine from my 2017 iMac, and from a couple of AS/400s in the same room:

ftp europa
Killed: 9

The ftp and telnet commands both fail with Killed 9 on the Mini, even if I don't specify a server. And that doesn't happen on the 2017 iMac.

I'm pretty sure I had to stick both the command line FTP and the command line Telnet back onto the iMac when I updated it to Catalina.

15
  • 1
    What did you enter to access your FTP server?
    – Thinkr
    May 12, 2023 at 16:46
  • 1
    First, use "@user" when replying we won't get notified otherwise. "Killed 9" is a server thing. FTP is ancient (as time passes in IT) and I don't believe it's included with macOS anymore (could be mistaken). Are you using a 3rd party FTP client?
    – Allan
    May 12, 2023 at 17:40
  • 1
    Okay, thanks for having added this additional info. Nice edit! :)
    – Thinkr
    May 12, 2023 at 17:57
  • 4
    Killed 9 is a local issue. Are you running an Intel binary on ARM without Rosetta installed?
    – nohillside
    May 12, 2023 at 18:00
  • 1
    Good catch @nohillside! I keep forgetting about this architecture change.
    – Allan
    May 12, 2023 at 18:08

1 Answer 1

1

I found a solution, on OS X Daily. It's a slightly different FTP client (e.g., it doesn't accept "exit" as a synonym for "quit"), but it solves the overriding problem of no command-line FTP or Telnet.

First, install Homebrew: https://osxdaily.com/2018/03/07/how-install-homebrew-mac-os/

It will most likely finish (at least it did for me) by giving you a pair of rather complicated commands to put Homebrew in your path.

Second, install the "inetutils" homebrew package: https://osxdaily.com/2018/08/07/get-install-ftp-mac-os/

This will give you command-line FTP, command-line Telnet, as well as a few I've never used (or even heard of), dnsdomainname, rcp, rexec, rlogin, and rsh.

If after doing this, you find yourself getting

500 Illegal PORT command.
500 Unknown command.
425 Use PORT or PASV first.

then you've found another difference between this FTP client and the one that used to be included in the OS, namely, it doesn't have passive mode enabled by default. Either enter the pass (not "pasv") command within ftp, or use the -p switch on the ftp command, for example,

ftp -p foo.com

or if you use it a lot, put alias ftp='ftp -p' in your .bash_profile or .bashrc file.

2
  • i rolled back your edit, don‘t think it‘s relevant for the problem stated in the question so it will rather distract from the actual answer.
    – nohillside
    May 16, 2023 at 20:01
  • Uh, anybody else who follows the answer and installs the Homebrew and inetutils is probably going to run into the same problem I did. May 16, 2023 at 21:12

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .