How about SSHFS? http://fuse.sourceforge.net/sshfs.html
On Sun, Dec 6, 2015 at 4:36 AM, Matt Sicker <[email protected]> wrote: > Would definitely like rsync support. > > On 5 December 2015 at 21:21, sebb <[email protected]> wrote: > >> On 6 December 2015 at 02:01, Roman Shaposhnik <[email protected]> >> wrote: >> > On Sat, Dec 5, 2015 at 1:32 PM, sebb <[email protected]> wrote: >> >> However, I have just discovered that although SFTP has a recursive put >> >> command, it does not have a recursive delete. >> >> >> >> Directories can only be removed when they are empty. >> >> >> >> As you can imagine, that makes tidying up after staging a website very >> >> tiresome (especially ones with Javadoc and source xref) >> > >> > I was passively monitoring this thread and dusting off my expect(1) man >> page, >> > but this could be a deal breaker even with automation. >> >> It seems that sftp does not even support recursive listing, so one way >> to automate the process would be to use ls -l to show the directories, >> parse the response to find the subdirs, etc. >> Possible, but pretty tedious, and generates a lot of unnecessary >> network traffic. >> >> Another option is to use rm *;rm */*;rm */*/* etc to the maximum depth >> expected. >> That works for files. >> >> Unfortunately it seems that rmdir * is not supported, so the >> directories have to be done individually >> This will require listing parsing as above, but at least the listings >> will be somewhat shorter. >> >> [Note that sftp supports batch input, so this can all be be done without >> expect] >> >> Having rsync would make it somewhat easier. >> >> > Thanks, >> > Roman. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > -- > Matt Sicker <[email protected]> > -- [image: MagineTV] *Mikael Ståldal* Senior software developer *Magine TV* [email protected] Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com Privileged and/or Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such a person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email.
