From 2e32d415c0e7df143b93d6c112ffb88103f51058 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Tue, 6 Nov 2001 19:33:13 +0000 Subject: 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! --- lib/transfer.c | 4 ---- 1 file changed, 4 deletions(-) (limited to 'lib/transfer.c') 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; } -- cgit v1.2.3