From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] curl things
Date: Tue, 6 Jan 2015 21:09:08 +0000 [thread overview]
Message-ID: <20150106210908.GD31364@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20150005163335.eklhad@comcast.net>
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
On Mon, Jan 05, 2015 at 04:33:35PM -0500, Karl Dahlke wrote:
> https download example fails consistently for me, on two different machines.
>
> curl 7.32.0
> OpenSSL 1.0.1e-fips 11
>
> curl 7.36.0
> OpenSSL 1.0.1e-fips 11
>
> I upgraded from 1.0.1e-30.fc20 to 1.0.1e-40.fc20 just for grins.
> Probably got rid of heartbleed bug, but didn't fix background download.
> read error right away.
> Well if it works for everyone but me
> then maybe we shouldn't spend a lot of time tracking it down.
> I wasn't asking for the feature in the first place.
True, I'm concerned as to why it's doing this in some, but not all,
versions of curl. What os are you running;
if I get time I'll set up a couple of virtual machines to try and reproduce this.
> > is there any way we could have a command to tell you
> > what downloads are currently in progress?
>
> maintain a dynamic array of background downloads, file name and child pid,
> catch signal 18, signal handler removes child from the list.
> Yes it could be done.
That sounds like a sensible design. How tricky would it be to implement?
Cheers,
Adam.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-01-06 21:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 21:33 Karl Dahlke
2015-01-06 0:25 ` Chris Brannon
2015-01-06 21:17 ` Adam Thompson
2015-01-06 21:09 ` Adam Thompson [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-01-03 15:34 Karl Dahlke
2015-01-05 18:12 ` Chris Brannon
2015-01-05 20:48 ` Adam Thompson
2014-12-28 15:35 Karl Dahlke
2014-12-28 16:04 ` Adam Thompson
2015-01-03 13:19 ` Chris Brannon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150106210908.GD31364@toaster.adamthompson.me.uk \
--to=arthompson1990@gmail.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).