Use of the information contained in this unapproved document is at your own risk.

Last update: 30 March,1998

								1003.1c-95  #21

 _____________________________________________________________________________

	Interpretation Number:	XXXX
	Topic:               timers and SIGEV_THREAD
	Relevant Sections:   14.2.2.2 (P1003.1b)

Interpretation Request: (Defect Report)
-----------------------

	Date: Tue, 16 Jul 1996 16:06:02 -0700
	From: "Scott J. Norton" <sjn@hpwssjn.cup.hp.com>




Section --> None in P1003.1c D10, corresponding section in p1003.1b is
            Section 14.2.2.2

The behavior for timer_create() specifies what happens when a sigevent
structure of type SIGEV_NONE or type SIGEV_SIGNAL is passed to the function.
POSIX.1c does not specify what the behavior of this function is if the
sigevent structure is for SIGEV_THREAD. The most complicated part is
when sigevent specifies SIGEV_THREAD but the timer is a reloading timer
so that it continually expires.

What is supposed to happen with timers and SIGEV_THREAD? A thread is to be
created when the timer expires? What happens with reloading timers which
continually expire? Does only one thread get created and from then on
an overrun count is incremented? Since these threads are detached, you have
no way of knowing this thread terminates in order to stop incrememnting the
count and create a new thread on the next timer expiration.

-------------------------------------------------------------------------------

Interpretation response
------------------------

This is a duplicate.  See PASC P1003.1c Interpretation #3, part 13.


Rationale
-------------
None.
Forwarded to Interpretations group: July 17th 1996
Finalised: Sep 4 1996