On Tue, 15 Apr 2014, Yves Dorfsman wrote: > On 2014-04-15 07:47, Dag-Erling Smørgrav wrote: > > Damien Miller <djm@xxxxxxxxxxx> writes: > >> Yves Dorfsman <yves@xxxxxxxxx> writes: > >>> #!/bin/bash > >>> curl -s --compressed http://someurl.example.com/pubkeys/$1 >somefile > >>> cat somefile > >> So curl/wget aren't coping with stdout being non-blocking. Those are > >> bugs in curl and wget. You've got the right workaround, but just > >> don't use a predictable filename (i.e. use mktemp). > > > > Shouldn't 'curl ... | cat' suffice? > > Tried that before, it returns an exit code 141. `man 1 curl' --compressed (HTTP) Request a compressed response using one of the algorithms curl supports, and save the uncompressed document. If this option is used and the server sends an unsupported encoding, curl will report an error. > > Or even 'echo "$(curl ...)"' > Can you completely prevent echo from interpreting $ sign? What do you mean? "$(curl ...)" will first get expanded (curl command executed) and stdout from curl will be echoed. Cheers, -- Cristian _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@xxxxxxxxxxx https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
