[CYGWIN] Re: SIGTERM does not stop backend postgres processes immediately

egor duda deo@logos-m.ru
Fri May 18 12:05:00 GMT 2001


Friday, 18 May, 2001 Christopher Faylor cgf@redhat.com wrote:

CF> On Fri, May 18, 2001 at 11:23:30AM -0700, Randall R Schulz wrote:
>>Here's a snippet from the Linux section 2 manual page:
>>int  select(int  n,  fd_set  *readfds,  fd_set  *writefds, fd_set 
>>*exceptfds, struct timeval *timeout));
>>timeout  is  an  upper bound on the amount of time elapsed before select 
>>returns. It may be zero, causing  select  to return  immediately. 
>>If  timeout  is  NULL  (no timeout), select can block indefinitely.
>>Does the indefinite-timeout variant of select exist and work under Cygwin 
>>(or Windows, as the case may be) compatibly with the Linux API spec?

CF> I was actually wrong about polling in the case of sockets.  You don't
CF> have to poll but, if you use the current method, you would have to
CF> create a separate thread.  That's pretty expensive, too.

i was thinking of making this socket-select thread persistent. is it
worth doing? this'll probably speed select() a bit.

Egor.            mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19

More information about the Cygwin-developers mailing list