Re^2: Net::FTP wildcard delete?

Looks like the server does it. According to man ftp:

            For mdelete and mget,  each  remote  file  name  is
expanded separately on the remote machine and the lists are not
merged.
[download]

Of course, if you really want to know how it's done (and you have root access), a packet sniffer is your friend.

Comment on Re^2: Net::FTP wildcard delete? Select or Download Code

Replies are listed 'Best First'.
Re^3: Net::FTP wildcard delete? by ikegami (Patriarch) on Jun 09, 2006 at 22:19 UTC
~~No,~~ "The file list is expanded on the remote machine" does not imply "`MDEL` is an FTP command". The list is expanded remotely by issuing an `NLST` command (as shown below). `MDEL` is not an FTP command. `ftp> prompt Interactive mode off. ftp> debug <-- Don't need a packet sniffer Debugging on (debug=1). ftp> quote MDEL yoink* <-- remote MDEL ---> MDEL yoink* 500 MDEL yoink: command not understood. ftp> mdel yoink <-- local MDEL ---> EPSV ---> NLST yoink* <-- remote expantion ---> DELE yoink <-- individual deletes 250 DELE command successful. ---> DELE yoinks 250 DELE command successful.` [download]	[reply] [d/l] [select]
Re^4: Net::FTP wildcard delete? by dsheroh (Monsignor) on Jun 09, 2006 at 23:04 UTC
Don't forget the context of my post, namely that I was replying to someone saying they were unsure of whether the wildcard is handled by the client or the server. I didn't mean to imply that MDEL was an FTP command, only that it "Looks like the server does [the wildcard expansion]." And thanks for the fuller explanation that NLST is the method by which the wildcard expansion is passed off to the server. I was kind of wondering how the client managed to put in the prompts for each file if the server handled the expansion.	[reply]