HP-UX Reference (11i v1 00/12) - 2 System Calls (vol 5)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man2/!!!intro.2
________________________________________________________________
___ ___
s
shmget(2) shmget(2)
[EINVAL] A shared memory identifier exists for key but is in 64-bit address space and the pro-
cess performing the request has been compiled as a 32-bit executable. In order to
avoid receiving this error, both IPC_SHARE32 and IPC_CREAT must be set in
shmflg by the 64-bit processes upon segment creation.
[EACCES] A shared memory identifier exists for key but operation permission (see glossary(9)) as
specified by the low-order 9 bits of shmflg would not be granted.
[EINVAL] A shared memory identifier exists for key but the size of the segment associated with
it is less than size and size is not equal to zero.
[ENOENT] A shared memory identifier does not exist for key and (shmflg & IPC_CREAT)is
‘‘false’’.
[ENOSPC] A shared memory identifier is to be created but the system-imposed limit on the max-
imum number of allowed shared memory identifiers system wide would be exceeded.
[ENOMEM] A shared memory identifier and associated shared memory segment are to be created,
but the amount of available physical memory is not sufficient to fill the request.
[EEXIST] A shared memory identifier exists for key but ((shmflg &
IPC_CREAT)&&(shmflg &
IPC_EXCL)) is ‘‘true’’.
SEE ALSO
ipcrm(1), ipcs(1), shmctl(2), shmop(2), stdipc(3C).
STANDARDS CONFORMANCE
shmget(): SVID2, SVID3, XPG2, XPG3, XPG4
Section 2−−328 − 2 − HP-UX Release 11i: December 2000
___
___