On 19-5-2012 5:54, Tim Kientzle wrote: > > On May 18, 2012, at 7:51 AM, Mel Flynn wrote: > >> On 17-5-2012 14:53, Mateusz Guzik wrote: >>> On Wed, May 16, 2012 at 11:37:44PM +0300, tza...@it.teithe.gr wrote: >> >>>> Nice. What about curl over the HTTPS protocol? >>>> >>> >>> curl would be ok, except it's not in the base system. >> >> For this reason, it's probably best to use tar(1) to package up multiple >> files and implement http put support in libfetch(3). You may also need >> to implement 305 Use Proxy support. > > Depends on where the files are coming from. If you > have files on disk, then tar(1) might be a good choice. > If you're going to have to construct the files, then you > can maybe avoid writing them to disk by using libarchive(3) > directly instead of going through the tar command-line > interface.
As I read the original intent is to post crashdumps at a specified remote location through rc(8) using an sh(1) script on the next reboot. tar seemed appropriate. I'm only mentioning extending libfetch(3), because it will be easy for fetch(1) to pick it up, it benefits more than just this project and once integrated into fetch(1) can be used in said script above. Other than openssh we don't really have a good tool in the base system to put local files elsewhere securely. Also, if the BUGS section of fetch(3) is out of date, I'm happy to be corrected :) -- Mel _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
