From:	dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de
Subject:	Re: ITIMER Implimentation???
4 Dec 1996 17:01:47 -0800 :
Sender:	daemon AT cygnus DOT com
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<009AC5D4.6C8D9E00.5616.cygnus.gnu-win32@ifk20.mach.uni-karlsruhe.de>
Original-To:	jra AT cygnus DOT com
Original-CC:	gnu-win32 AT cygnus DOT com, dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

Hi Jeremy, you wrote:

: Timers are not implemented yet in cygwin32 (Not even in
: the mythical beta17 :-). The reason is that asynchronous
: signals are not available in NT/95 (for reasons see the VMS
: source code or any other of Dave Cutlers work, ie. it's a
: religious thing :-).
: 
: I have some ideas on how to do this but involves a complete
: re-write of the I/O code in Cygwin32 so don't expect it anytime
: soon...

I need timers urgent, too.

I have good knowledge of VMS and was forced to unix and now partially to NT.
VMS is not the culprit, there it's called AST (Asynchronous System Trap),
which you can think of two threads at the user level. I used them much.

Now I rely on alarm(60) for a timeout on fgets() working on a socket via
fdopen(), then in the signal handler I close() the underlying socket...
May not be portable to all unixes, but works on hp-ux, DEC Unix/Alpha and
Linux/x86.


Bye, Heribert (dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de)
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -