Date: Fri, 13 Sep 2002 17:59:30 -0400 From: Craig Rodrigues <rodrigc@attbi.com> To: freebsd-standards@freebsd.org Subject: Re: mlockall/munlockall support? Message-ID: <20020913175930.A1762@attbi.com> In-Reply-To: <20020913142801.G84338@espresso.q9media.com>; from mike@FreeBSD.org on Fri, Sep 13, 2002 at 02:28:01PM -0400 References: <20020913115404.A1128@attbi.com> <20020913142801.G84338@espresso.q9media.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 13, 2002 at 02:28:01PM -0400, Mike Barcroft wrote:
> Craig Rodrigues <rodrigc@attbi.com> writes:
> > Are mlockall()/munlockall() calls implemented in FreeBSD-current?
>
> There are stubs, but no implementation. I've removed the prototypes
> in -current.
Thanks for the quick feedback! I encountered the mlockall() problem
while porting some code from Linux.
Would it be possible to put those functions on the
"TODO" list for the FreeBSD C99 and POSIX project web page? It's not a priority
for me, but having a list of unimplemented functions might be useful
to have for people like me who need to port software, and if someone has
the time/inclination later on, they can implement these functions
( I'm not volunteering :)
A few other questions:
- what is the status of following functions in <signal.h>:
sigqueue, sigtimedwait, sigwaitinfo
- 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?
This stuff confused me when 6 months ago when I was trying to port some
other code from Linux, and I was trying to read the header files to
determine what to do.
Thanks.
--
Craig Rodrigues
http://www.gis.net/~craigr
rodrigc@attbi.com
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?20020913175930.A1762>