From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] curl things
Date: Mon, 05 Jan 2015 16:33:35 -0500 [thread overview]
Message-ID: <20150005163335.eklhad@comcast.net> (raw)
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.
> 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.
Karl Dahlke
next reply other threads:[~2015-01-05 21:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 21:33 Karl Dahlke [this message]
2015-01-06 0:25 ` Chris Brannon
2015-01-06 21:17 ` Adam Thompson
2015-01-06 21:09 ` Adam Thompson
-- 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=20150005163335.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
/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).