svcadm(8)을 검색하려면 섹션에서 8 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
minherit(2)
The system call changes the specified pages to have the inheri‐
tance characteristic Not all implementations will guarantee that
the inheritance characteristic can be set on a page basis; the
granularity of changes may be as large as an entire region. is
capable of adjusting inheritance characteristics on a page basis.
Inheritance only effects children created by It has no effect on
exec'd processes replace their address space entirely. This sys‐
tem call also has no effect on the parent's address space (other
than to potentially share the address space with its children).
Inheritance is a rather esoteric feature largely superseded by
the feature of However, it is possible to use to share a block of
memory between parent and child that has been mapped That is,
modifications made by parent or child are shared but the original
underlying file is left untouched. This option causes the ad‐
dress space in question to be shared between parent and child.
It has no effect on how the original underlying backing store was
mapped. This option prevents the address space in question from
being inherited at all. The address space will be unmapped in
the child. This option causes the child to inherit the address
space as copy-on-write. This option also has an unfortunate side
effect of causing the parent address space to become copy-on-
write when the parent forks. If the original mapping was it will
no longer be shared in the parent after the parent forks and
there is no way to get the previous shared-backing-store mapping
without unmapping and remapping the address space in the parent.
This option causes the address space in question to be mapped as
new anonymous pages, which would be initialized to all zero
bytes, in the child process. The system call will fail if: The
virtual address range specified by the and arguments is not
valid. The flags specified by the argument were not valid for
the pages specified by the and arguments. The system call first
appeared in and then in The support first appeared in and then in
Once you set inheritance to or there is no way to recover the
original copy-on-write semantics short of unmapping and remapping
the area.