[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] MiNTNet: connect timeout?

To: mint@lists.fishpool.fi
Subject: Re: [MiNT] MiNTNet: connect timeout?
From: Jean-François Lemaire <jflemaire@skynet.be>
Date: Fri, 04 Jan 2013 22:32:53 +0100
In-reply-to: <50E64DFF.9060801@club-internet.fr>
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-id: <mint.lists.fishpool.fi>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
References: <50E64DFF.9060801@club-internet.fr>
Sender: mint-bounce@lists.fishpool.fi
User-agent: KMail/4.9.4 (Linux/3.4.11-2.16-desktop; KDE/4.9.4; x86_64; ; )

On Friday 04 January 2013 04:35:27 Pierre Ton-That wrote:

> Is there a way to test an opened port(s) before the connection attempt,
> or use a timeout in the connect function? Or do programs use a separate
> process they can kill if connection is too long?

I'm not sure this answers your question, but isn't select() what you're 
looking for?

http://support.sas.com/documentation/onlinedoc/sasc/doc750/html/lr2/select.htm

Cheers,
JFL
-- 
Jean-François Lemaire

References:
- [MiNT] MiNTNet: connect timeout?
  - From: Pierre Ton-That <ptonthat@club-internet.fr>

Prev by Date: Re: [MiNT] TimerA interrupt handler
Next by Date: Re: [MiNT] Patch: shel_write() did not call the PureC patcher
Previous by thread: [MiNT] MiNTNet: connect timeout?
Next by thread: Re: [MiNT] MiNTNet: connect timeout?
Index(es):
- Date
- Thread