| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
initially suggested by mdoc(7) style, but was broken over the years
|
|
|
|
|
|
|
|
|
|
|
| |
. use real function names as `.Nm' macro argument in NAME section. It allows
them to appear in apropos(1) or whatis(1) output.
. replace empty lines with `.Pp' macro.
. replace hardcoded standard names with their `.St' macro equivalents.
. sort cross references in SEE ALSO section
|
|
|
|
|
|
| |
error return values. Implement pthread_mutexattr_gettype().
PR: docs/16537, docs/17538
|
|
|
|
|
| |
PR: docs/18214
Submitted by: Ben Smithurst <ben@scientia.demon.co.uk>
|
|
|
|
| |
Submitted by: allenc@verinet.com
|
| |
|
|
|
|
|
| |
bit of work (and is stylistically probably the worst manual page
I've ever written).
|
|
|
|
| |
More libraries manpages updates following.
|
| |
|
| |
|
|
|
|
|
|
| |
reflect the fact that aio_cancel() works now.
Submitted by: Christopher Sedore <cmsedore@maxwell.syr.edu>
|
| |
|
|
|
|
|
| |
of the typeset output, tend to make diffs harder to read and provide
bad examples for new-comers to mdoc.
|
|
|
|
|
|
|
|
|
|
|
|
| |
This
This feature allows you to specify if mmap'd data is included in
an application's corefile.
Change the type of eflags in struct vm_map_entry from u_char to
vm_eflags_t (an unsigned int).
Reviewed by: dillon,jdp,alfred
Approved by: jkh
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
run out of KVM through a mmap()/fork() bomb that allocates hundreds
of thousands of vm_map_entry structures.
Add panic to make null-pointer dereference crash a little more verbose.
Add a new sysctl, vm.max_proc_mmap, which specifies the maximum number
of mmap()'d spaces (discrete vm_map_entry's in the process). The value
defaults to around 9000 for a 128MB machine. The test is scaled for the
number of processes sharing a vmspace (aka linux threads). Setting
the value to 0 disables the feature.
PR: kern/16573
Approved by: jkh
|
|
|
|
| |
happens to be the correct macro to use in this situation.
|
|
|
|
|
|
| |
ix86 platform which allows for hardware watchpoints, etc...
Submitted by: Brian Dean <brdean@unx.sas.com>
|
|
|
|
| |
Reviewed by: Matthew Dillon <dillon@apollo.backplane.com>
|
|
|
|
| |
Split timeval options into 3 paragraphs, it's easier on my eyes.
|
|
|
|
| |
Submitted by: obrien
|
|
|
|
| |
4 commits and 2 world breakages so far.
|
|
|
|
| |
way, unbroke world).
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
example of section 2 and section 3 interfaces sharing a man page. It's
probably a bad example.
|
|
|
|
|
|
| |
about 6-7 times prior to commit.
Reported by: sheldonh
|
|
|
|
|
|
|
|
| |
Fix some spelling mistakes and typo's inspired by Nicholas' initial
PR submission.
PR: docs/15597
Submitted by: Nicholas Esborn <nick@flatlan.net>
|
|
|
|
| |
Reviewed by: Sheldon Hearn <sheldonh@uunet.co.za>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
madvise().
This feature prevents the update daemon from gratuitously flushing
dirty pages associated with a mapped file-backed region of memory. The
system pager will still page the memory as necessary and the VM system
will still be fully coherent with the filesystem. Modifications made
by other means to the same area of memory, for example by write(), are
unaffected. The feature works on a page-granularity basis.
MAP_NOSYNC allows one to use mmap() to share memory between processes
without incuring any significant filesystem overhead, putting it in
the same performance category as SysV Shared memory and anonymous memory.
Reviewed by: julian, alc, dg
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
with NetBSD and the Single Unix Specification v2.
This updates some structures with other, almost equivalent types and
effort is under way to get the whole more consistent.
Also removes a double definition of INET6 and some other clean-ups.
Reviewed by: green, bde, phk
Some part obtained from: NetBSD, SUSv2 specification
|
| |
|
|
|
|
|
|
| |
PR: docs/14173 docs/14181
Submitted by: Charles Randall <crandall@matchlogic.com>
Submitted by: Kelly Yancey <kbyanc@posi.net>
|
|
|
|
|
|
|
|
| |
the code, which seems to implement the POSIX requirements, and
have described the behavior here. Basically, it behaves the same
as select(2).
Noticed by: John Polstra
|
|
|
|
| |
Spotted by: John Polstra <jdp@polstra.com> (again)
|
|
|
|
|
|
|
| |
Also spelled out the return values and conditions a little
better.
Noticed by: John Polstra <jdp@polstra.com>
|
|
|
|
| |
can be handled intelligently.
|
|
|
|
| |
Pointed out by: obrien
|
| |
|
|
|
|
| |
Obtained from: NetBSD
|
| |
|
|
|
|
|
| |
Submitted by: Dan Nelson <dnelson@emsphone.com>
Forgotten by: mpp
|
|
|
|
| |
Reviewed by: mpp
|
|
|
|
|
|
|
|
| |
Style and punctuation errors fixes.
ERRORS section included to RETURN VALUES because it's
describing return values instead of errors and their handling.
Reviewed by: mpp
|
|
|
|
|
|
| |
Correct RB_* values list bounds.
Reviewed by: mpp
|