Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 13 Sep 2002 18:18:10 -0400 (EDT)
From:      Garrett Wollman <wollman@lcs.mit.edu>
To:        Craig Rodrigues <rodrigc@attbi.com>
Cc:        freebsd-standards@FreeBSD.ORG
Subject:   Re: mlockall/munlockall support?
Message-ID:  <200209132218.g8DMIAhE099932@khavrinen.lcs.mit.edu>
In-Reply-To: <20020913175930.A1762@attbi.com>
References:  <20020913115404.A1128@attbi.com> <20020913142801.G84338@espresso.q9media.com> <20020913175930.A1762@attbi.com>

next in thread | previous in thread | raw e-mail | index | archive | help
<<On Fri, 13 Sep 2002 17:59:30 -0400, Craig Rodrigues <rodrigc@attbi.com> said:

> A few other questions:
> - what is the status of following functions in <signal.h>:
>         sigqueue, sigtimedwait, sigwaitinfo

The POSIX Real Time Signals option is not implemented.  It may be in
the future.

> - is the stuff encapsulated in _P1003_1B_VISIBLE #ifdef/#endif blocks
>   in various header files like <limits.h> <time.h> <sys/signal.h>
>   <sys/unistd.h> still applicable?

If it still uses that symbol, it means nobody has looked at it for
long enough to determine definitively.  In some cases it is probably
used erroneously.

-GAWollman


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-standards" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200209132218.g8DMIAhE099932>