Re: Curl output file not created when used with external tool
Date: Wed, 8 Jan 2020 11:33:39 +0530
Thanks for the suggestion. I'll look into it. As of now we're already using
3 different tools for this simple webAPI access (our mapping tool, curl and
batch files) so we shud try to minimize that and batch file wrapper did the
trick (also, its native to windows so no setup overhead). Will get familiar
with the script utility for future.
On Tue, Jan 7, 2020 at 11:47 PM Paul Gilmartin <PaulGBoulder_at_aim.com> wrote:
> On 2020-01-07, at 01:17:57, Hemant Tank wrote:
> > Thank you for your reply, yes we verified many such scenarios, it wasn't
> related path accessibiliy. Here's the workaround -
> > There was nothing to be rectified in curl command options, we suspect
> that our mapping tool was somehow preventing the console output all
> together (thus the output file might also have not been created because no
> output was allowed).
> Where it's supported, I've sometimes found "script" useful for this.
> -- gil