[fpc-devel]Timing out a syscall?
Mike Ravkin
mike at acidsearch.com
Sun Oct 1 15:45:53 CEST 2000
That works fine after the connect(), but connect() itself is blocking, and
can take as long as it feels like.. this is obviously bad.
----- Original Message -----
From: <pfv at cooldown.demon.nl>
To: <fpc-devel at deadlock.et.tudelft.nl>
Sent: Wednesday, September 20, 2000 2:51 AM
Subject: Re: [fpc-devel]Timing out a syscall?
> > What's the proper way to time out a socket connect function, or another
> > syscall? Putting it in a thread and then terminating the thread after X
> > seconds leaves zombie processes, wich are not good.
> >
>
> use select() to check if there is data before reading data from the
socket.
>
>
>
>
>
> _______________________________________________
> fpc-devel maillist - fpc-devel at lists.freepascal.org
> http://lists.freepascal.org/mailman/listinfo/fpc-devel
>
More information about the fpc-devel
mailing list