Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   10987 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

datalock(3C)							  datalock(3C)

NAME
       datalock()  -  lock process into memory after allocating data and stack
       space

SYNOPSIS
DESCRIPTION
       allocates at least datsiz bytes of data space and stsiz bytes of	 stack
       space,  then  locks the program in memory.  The data space is allocated
       by (see malloc(3C)).  After  the	 program  is  locked,  this  space  is
       released by (see malloc(3C)), making it available for use.  This allows
       the calling program to use that much space dynamically without  receiv‐
       ing the signal.

       The effective user ID of the calling process must be super-user or be a
       member of or have an effective group ID of a  group  having  PRIV_MLOCK
       access to use this call (see setprivgrp(2) in getprivgrp(2)).

EXAMPLES
       The following call to allocates 4096 bytes of data space and 2048 bytes
       of stack space, then locks the process in memory:

RETURN VALUE
       returns -1 if cannot allocate enough memory or  if  returned  an	 error
       (see plock(2)).

WARNINGS
       Multiple datalocks cannot be the same as one big one.

       Methods for calculating the required size are not yet well developed.

AUTHOR
       was developed by HP.

SEE ALSO
       getprivgrp(2), plock(2), thread_safety(5).

								  datalock(3C)

Vote for polarhome