Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <3A0FA4E7.797F9C58@redhat.com>
Date: Mon, 13 Nov 2000 09:23:03 +0100
From: Corinna Vinschen <vinschen@redhat.com>
MIME-Version: 1.0
To: Joe Clark <joeclark@iastate.edu>
CC: cygwin@sourceware.cygnus.com
Subject: Re: clock() and sleep(int) system calls
References: <4.2.0.58.20001113011419.00aab7f0@joeclark.mail.iastate.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Joe Clark wrote:
> 
> Hello there.  I'm trying to build a socket-based program on WinNT 4, and
> I'd like to be able to combine clock() and sleep() in the program, but from
> my preliminary experiments, it appears that the sleep() function
> reinitializes the variable that clock() keeps track of -- so much for
> measuring elapsed time.  Is this documented somewhere?  Is there some good
> explanation for why it works this way?  Is there a way around it?
> 
> While I'm at it, for those who know socket programming, is there a way to
> "kill" a call to the accept(...) function, which normally blocks until a
> connection comes in?  I'd like to declare a maximum time for my server to
> run (say 5 minutes), and then have it exit normally.

You have to use `select' to wait for a connection only a specific
amount of time. When select reports that a connection should be
established only then call `accept'.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                        mailto:cygwin@sources.redhat.com
Red Hat, Inc.
mailto:vinschen@redhat.com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com