diff options
| author | Daniel Stenberg <daniel@haxx.se> | 2001-11-06 19:33:13 +0000 |
|---|---|---|
| committer | Daniel Stenberg <daniel@haxx.se> | 2001-11-06 19:33:13 +0000 |
| commit | 2e32d415c0e7df143b93d6c112ffb88103f51058 (patch) | |
| tree | ecad27e24d0bdeff2ba7172b5483c6c96901c294 /lib/transfer.c | |
| parent | 3dfc509d33d3f0ebc82ac4cc33522ff156d78838 (diff) | |
myalarm() is history, we now use HAVE_ALARM and we now do our very best to
1 - restore the previous sigaction struct as soon as we are about to shut
off our timeout
2 - restore the previous alarm() timeout, in case an application or similar
had it running before we "borrowed" it for a while.
No, this does not fix the multi-thread problem you get with alarm(). This
patch should correct bug report #478780:
//sourceforge.net/tracker/?func=detail&atid=100976&aid=478780&group_id=976
If not, please post details!
Diffstat (limited to 'lib/transfer.c')
| -rw-r--r-- | lib/transfer.c | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/lib/transfer.c b/lib/transfer.c index 449b2e6eb..2d1c90f6a 100644 --- a/lib/transfer.c +++ b/lib/transfer.c @@ -1159,10 +1159,6 @@ CURLcode Curl_perform(struct SessionHandle *data) if(newurl) free(newurl); - /* make absolutely sure the alarm is switched off! */ - if(data->set.timeout || data->set.connecttimeout) - myalarm(0); - return res; } |