| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
------------------------------------------------------------------------
r266285 | bjk | 2014-05-16 23:05:52 -0400 (Fri, 16 May 2014) | 9 lines
Correct documentation of the limit on how much memory can be mlock()ed
vm.max_wired is a system-wide limit, not per-process. Reword the
section to make this more clear.
PR: docs/189214
Submitted by: Lawrence Chen (original text)
Approved by: hrs (mentor)
------------------------------------------------------------------------
r266866 | bjk | 2014-05-29 22:16:28 -0400 (Thu, 29 May 2014) | 5 lines
Minor mdoc fix
Submitted by: hrs
Approved by: hrs (mentor, implicit)
------------------------------------------------------------------------
PR: docs/189214
Approved by: hrs (mentor)
|
|
|
|
|
|
| |
ENOMEM. Clarify this, taking text from SUS.
Reviewed by: kib
|
|
|
|
|
| |
Approved by: kib (mentor)
MFC after: 1 week
|
|
|
|
|
|
|
| |
like the mlock(2) manual page says. Update mlock(2) to say that hitting
RLIMIT_MEMLOCK results in ENOMEM, not EAGAIN.
MFC after: 1 month
|
|
|
|
|
|
| |
clause.
# If I've done so improperly on a file, please let me know.
|
| |
|
| |
|
|
|
|
|
| |
PR: docs/73193
Submitted by: Jilles Tjoelker <jilles at stack.nl>
|
| |
|
|
|
|
|
| |
a case where ENOMEM could be returned by munlock(2), and add possible
system deadlock to the BUGS section.
|
|
|
|
| |
Reminded by: ru@
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Stop calling system calls "function calls".
Use "The .Fn system call" a-la "The .Nm utility".
When referring to a non-BSD implementation in
the HISTORY section, call syscall a function,
to be safe.
|
|
|
|
| |
<sys/mman.h>.
|
| |
|
|
|
|
| |
Submitted by: yar
|
|
|
|
| |
with a trailing zero-width space: `e.g.\&'.
|
| |
|
|
|
|
| |
More libraries manpages updates following.
|
| |
|
|
|
|
|
|
|
| |
caller is not the super-user. Also document that we do not
currently support the per-process RLIMIT_MEMLOCK limit.
PR: doc/11607
|
|
|
|
| |
Obtained from: OpenBSD
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
mlock, mmap, mprotect, msync, munlock, and munmap are defined by
POSIX as taking void *. The const modifier has been added to
mlock, munlock, and mprotect as the standard dictates.
minherit comes from OpenBSD and has been updated to conform with
their recent change to void *.
madvise and mincore are not defined by POSIX, but their arguments
have been modified to be consistent with the POSIX-defined functions.
mincore takes a const pointer, but madvise does not due to the
MADV_FREE case.
Discussed with: bde
|
|
|
|
|
|
|
|
| |
in a bunch of man pages.
Use the correct .Bx (BSD UNIX) or .At (AT&T UNIX) macros
instead of explicitly specifying the version in the text
in a bunch of man pages.
|
|
|