Mechanically kill hard sentence breaks.
This commit is contained in:
ru
parent
47f5e31e2b
commit
01548ace15
@ -196,7 +196,7 @@ mode bit is set.
|
||||
This bit should be set when the packet aliasing host originates network
|
||||
traffic as well as forwards it.
|
||||
When the packet aliasing host is waiting for a connection from an unknown
|
||||
host address or unknown port number (e.g. an FTP data connection), this
|
||||
host address or unknown port number (e.g.\& an FTP data connection), this
|
||||
mode bit specifies that a socket be allocated as a place holder to prevent
|
||||
port conflicts.
|
||||
Once a connection is established, usually within a minute or so, the socket
|
||||
@ -237,7 +237,7 @@ possible to use a hole for another connection.
|
||||
A hole is removed when the connection that uses it dies.
|
||||
To cater to unexpected death of a program using
|
||||
.Nm
|
||||
(e.g. kill -9),
|
||||
(e.g.\& kill -9),
|
||||
changing the state of the flag will clear the entire firewall range
|
||||
allocated for holes.
|
||||
This will also happen on the initial call to
|
||||
@ -560,7 +560,7 @@ For links created with
|
||||
.Fn LibAliasRedirectAddr ,
|
||||
the
|
||||
.Fa port
|
||||
argument is ignored and could have any value, e.g. htons(~0).
|
||||
argument is ignored and could have any value, e.g.\& htons(~0).
|
||||
.Pp
|
||||
This function returns 0 on success, \-1 otherwise.
|
||||
.Ed
|
||||
@ -571,15 +571,15 @@ This function returns 0 on success, \-1 otherwise.
|
||||
This function marks the specified static redirect rule entered by
|
||||
.Fn LibAliasRedirectPort
|
||||
as dynamic.
|
||||
This can be used to e.g. dynamically redirect a single TCP connection,
|
||||
This can be used to e.g.\& dynamically redirect a single TCP connection,
|
||||
after which the rule is removed.
|
||||
Only fully specified links can be made dynamic.
|
||||
(See the
|
||||
.Sx STATIC AND DYNAMIC LINKS
|
||||
and
|
||||
.Sx PARTIALLY SPECIFIED ALIASING LINKS
|
||||
sections below for a definition of static vs. dynamic,
|
||||
and partially vs. fully specified links.)
|
||||
sections below for a definition of static vs.\& dynamic,
|
||||
and partially vs.\& fully specified links.)
|
||||
.Pp
|
||||
This function returns 0 on success, \-1 otherwise.
|
||||
.Ed
|
||||
@ -878,7 +878,7 @@ and
|
||||
.Fa maxpacketsize
|
||||
is provided for error checking purposes.
|
||||
This function can be used if an already-aliased packet needs to have its
|
||||
original IP header restored for further processing (eg. logging).
|
||||
original IP header restored for further processing (e.g.\& logging).
|
||||
.Ed
|
||||
.Sh BUGS
|
||||
PPTP aliasing does not work when more than one internal client
|
||||
|
||||
@ -299,7 +299,8 @@ recognized.
|
||||
.Xr strtofflags 3 ,
|
||||
which stops parsing at the first unrecognized name.)
|
||||
.Ss ACL Handling
|
||||
XXX This needs serious help. XXX
|
||||
XXX This needs serious help.
|
||||
XXX
|
||||
.Pp
|
||||
An
|
||||
.Dq Access Control List
|
||||
|
||||
@ -269,7 +269,8 @@ and
|
||||
objects can be found in the overview manual page for
|
||||
.Xr libarchive 3 .
|
||||
.Sh EXAMPLE
|
||||
The following illustrates basic usage of the library. In this example,
|
||||
The following illustrates basic usage of the library.
|
||||
In this example,
|
||||
the callback functions are simply wrappers around the standard
|
||||
.Xr open 2 ,
|
||||
.Xr read 2 ,
|
||||
|
||||
@ -225,7 +225,8 @@ overview.
|
||||
Compression support is built-in to libarchive, which uses zlib and bzlib
|
||||
to handle gzip and bzip2 compression, respectively.
|
||||
.Sh EXAMPLE
|
||||
The following sketch illustrates basic usage of the library. In this example,
|
||||
The following sketch illustrates basic usage of the library.
|
||||
In this example,
|
||||
the callback functions are simply wrappers around the standard
|
||||
.Xr open 2 ,
|
||||
.Xr write 2 ,
|
||||
|
||||
@ -101,7 +101,7 @@ should point to an address which is
|
||||
.Fa len
|
||||
bytes long,
|
||||
in binary form
|
||||
(i.e. not an Bluetooth BD_ADDR in human readable
|
||||
(i.e., not an Bluetooth BD_ADDR in human readable
|
||||
.Tn ASCII
|
||||
form).
|
||||
The
|
||||
|
||||
@ -135,15 +135,18 @@
|
||||
The
|
||||
.Nm snmp_netgraph
|
||||
module implements a number of tables and scalars that enable remote access to
|
||||
the netgraph subsystem. It also exports a number of global variables and
|
||||
the netgraph subsystem.
|
||||
It also exports a number of global variables and
|
||||
functions, that allow other modules to easily use the netgraph system.
|
||||
.Pp
|
||||
If upon start up of the module the variable
|
||||
.Va begemotNgControlNodeName
|
||||
is not empty the module opens a netgraph socket and names that socket node.
|
||||
If the variable is empty, the socket is created, as soon as the variable is
|
||||
written with a non-empty name. The socket can be closed by writing an empty
|
||||
string to the variable. The socket itself and its name are available in
|
||||
written with a non-empty name.
|
||||
The socket can be closed by writing an empty
|
||||
string to the variable.
|
||||
The socket itself and its name are available in
|
||||
.Va snmp_node
|
||||
and
|
||||
.Va snmp_nodename .
|
||||
@ -169,7 +172,8 @@ is the node specific command cookie,
|
||||
.It Fa opcode
|
||||
is the node specific code for the operation to performa,
|
||||
.It Fa arg
|
||||
is a pointer to the message itself. This message must start with a
|
||||
is a pointer to the message itself.
|
||||
This message must start with a
|
||||
.Vt struct ng_mesg .
|
||||
.It Fa arglen
|
||||
is the overall length of the message (header plus arguments).
|
||||
@ -178,8 +182,10 @@ The functions return the message id that can be used to match incoming responses
|
||||
or -1 if an error occurs.
|
||||
.Pp
|
||||
Another class of functions is used to send a control message and to wait for
|
||||
a matching response. Note, that this operation blocks the daemon, so use it
|
||||
only if you are sure that the response will happen. There is a maximum timeout
|
||||
a matching response.
|
||||
Note, that this operation blocks the daemon, so use it
|
||||
only if you are sure that the response will happen.
|
||||
There is a maximum timeout
|
||||
that is configurable in the MIB variable
|
||||
.Va begemotNgTimeout .
|
||||
Other messages arriving while the functions are waiting for the response are
|
||||
@ -201,9 +207,11 @@ and waits for a matching response.
|
||||
.Pp
|
||||
All three functions take the same arguments as the
|
||||
.Fn ng_output*
|
||||
functions. The functions return the reponse message in a buffer allocated by
|
||||
functions.
|
||||
The functions return the reponse message in a buffer allocated by
|
||||
.Xr malloc 3
|
||||
or NULL in case of an error. The maximum size of the response buffer can be
|
||||
or NULL in case of an error.
|
||||
The maximum size of the response buffer can be
|
||||
configured in the variable
|
||||
.Va begemotNgResBufSiz .
|
||||
.Pp
|
||||
@ -212,16 +220,19 @@ A data message can be send with the function
|
||||
This function takes the name of the
|
||||
.Va snmp_node Ns 's
|
||||
hook through which to send the data, a pointer to the message buffer and
|
||||
the size of the message. It returns -1 if an error happens.
|
||||
the size of the message.
|
||||
It returns -1 if an error happens.
|
||||
.Ss ASYNCHRONOUS CONTROL AND DATA MESSAGES
|
||||
A module can register functions to asynchronuosly receive control and data
|
||||
message.
|
||||
.Pp
|
||||
The function
|
||||
.Fn ng_register_cookie
|
||||
registers a control message receive function. If a control message is
|
||||
registers a control message receive function.
|
||||
If a control message is
|
||||
received, that is not consumed by the dialog functions, the list of registerred
|
||||
control message receive functions is scanned. If the cookie in the received
|
||||
control message receive functions is scanned.
|
||||
If the cookie in the received
|
||||
message is the same as the
|
||||
.Fa cookie
|
||||
argument to the
|
||||
@ -238,7 +249,8 @@ is called with a pointer to the received message, the hook on which the
|
||||
message was received (or NULL if it was received not on a hook), the id
|
||||
of the sender's node and the
|
||||
.Fa uarg
|
||||
argument of the registration call. The handler function should not modify
|
||||
argument of the registration call.
|
||||
The handler function should not modify
|
||||
the contents of the message, because more than one function may be registered
|
||||
to the same cookie and node id.
|
||||
.Pp
|
||||
@ -253,12 +265,14 @@ A module can call
|
||||
.Fn ng_register_hook
|
||||
to register a callback for data messages on one of the
|
||||
.Va snmp_node Ns 's
|
||||
hooks. If a data message is received on that hook, the callback function
|
||||
hooks.
|
||||
If a data message is received on that hook, the callback function
|
||||
.Fa func
|
||||
is called with the hook name, a pointer to the data message, the size of
|
||||
the message and the argument
|
||||
.Fa uarg
|
||||
to the registration function. The message should be treated as read-only.
|
||||
to the registration function.
|
||||
The message should be treated as read-only.
|
||||
A data message registration can be undone by calling
|
||||
.Fn ng_unregister_hook
|
||||
with the return value of the registration call.
|
||||
@ -291,7 +305,8 @@ and writes it to the buffer pointed to by
|
||||
.Fa name .
|
||||
This buffer should be at least
|
||||
.Li NG_NODESIZ
|
||||
bytes long. The function returns the node id or 0 if the
|
||||
bytes long.
|
||||
The function returns the node id or 0 if the
|
||||
node is not found
|
||||
.Pp
|
||||
The function
|
||||
@ -302,7 +317,8 @@ and writes it to the buffer pointed to by
|
||||
.Fa type .
|
||||
This buffer should be at least
|
||||
.Li NG_TYPESIZ
|
||||
bytes long. The function returns the node id or 0 if the
|
||||
bytes long.
|
||||
The function returns the node id or 0 if the
|
||||
node is not found.
|
||||
.Pp
|
||||
The function
|
||||
@ -315,8 +331,10 @@ to the buffer pointed to by
|
||||
.Fa peer_hook .
|
||||
The buffer should be at least
|
||||
.Li NG_HOOKSIZ
|
||||
bytes long. The function returns 0 if the node and the hook is found, -1
|
||||
otherwise. The function skips intermediate tee nodes (see
|
||||
bytes long.
|
||||
The function returns 0 if the node and the hook is found, -1
|
||||
otherwise.
|
||||
The function skips intermediate tee nodes (see
|
||||
.Xr ng_tee 4 ).
|
||||
.Pp
|
||||
The function
|
||||
@ -348,7 +366,8 @@ of node
|
||||
.Fa id .
|
||||
If
|
||||
.Fa name
|
||||
is not NULL the new node is named with this name. The function returns
|
||||
is not NULL the new node is named with this name.
|
||||
The function returns
|
||||
The node id of the new node or 0 if an error happens.
|
||||
.Pp
|
||||
The functions
|
||||
|
||||
@ -53,8 +53,10 @@ The
|
||||
function
|
||||
establishes a 32-bit identifier for the
|
||||
current processor that is intended to be unique among all
|
||||
UNIX systems in existence. This is normally a DARPA Internet
|
||||
address for the local machine. This call is allowed only to the
|
||||
UNIX systems in existence.
|
||||
This is normally a DARPA Internet
|
||||
address for the local machine.
|
||||
This call is allowed only to the
|
||||
super-user and is normally performed at boot time.
|
||||
.Pp
|
||||
The
|
||||
|
||||
@ -60,7 +60,8 @@ This interface is made obsolete by
|
||||
The system defines a set of signals that may be delivered to a process.
|
||||
Signal delivery resembles the occurrence of a hardware interrupt:
|
||||
the signal is blocked from further occurrence, the current process
|
||||
context is saved, and a new one is built. A process may specify a
|
||||
context is saved, and a new one is built.
|
||||
A process may specify a
|
||||
.Em handler
|
||||
to which a signal is delivered, or specify that a signal is to be
|
||||
.Em blocked
|
||||
@ -69,7 +70,8 @@ or
|
||||
A process may also specify that a default action is to be taken
|
||||
by the system when a signal occurs.
|
||||
Normally, signal handlers execute on the current stack
|
||||
of the process. This may be changed, on a per-handler basis,
|
||||
of the process.
|
||||
This may be changed, on a per-handler basis,
|
||||
so that signals are taken on a special
|
||||
.Em "signal stack" .
|
||||
.Pp
|
||||
@ -82,8 +84,10 @@ but other signals may yet occur.
|
||||
A global
|
||||
.Em "signal mask"
|
||||
defines the set of signals currently blocked from delivery
|
||||
to a process. The signal mask for a process is initialized
|
||||
from that of its parent (normally 0). It
|
||||
to a process.
|
||||
The signal mask for a process is initialized
|
||||
from that of its parent (normally 0).
|
||||
It
|
||||
may be changed with a
|
||||
.Xr sigblock 2
|
||||
or
|
||||
@ -92,12 +96,15 @@ call, or when a signal is delivered to the process.
|
||||
.Pp
|
||||
When a signal
|
||||
condition arises for a process, the signal is added to a set of
|
||||
signals pending for the process. If the signal is not currently
|
||||
signals pending for the process.
|
||||
If the signal is not currently
|
||||
.Em blocked
|
||||
by the process then it is delivered to the process. When a signal
|
||||
by the process then it is delivered to the process.
|
||||
When a signal
|
||||
is delivered, the current state of the process is saved,
|
||||
a new signal mask is calculated (as described below),
|
||||
and the signal handler is invoked. The call to the handler
|
||||
and the signal handler is invoked.
|
||||
The call to the handler
|
||||
is arranged so that if the signal handling routine returns
|
||||
normally the process will resume execution in the context
|
||||
from before the signal's delivery.
|
||||
@ -119,7 +126,8 @@ in the signal mask associated with the handler to be invoked.
|
||||
The
|
||||
.Fn sigvec
|
||||
function
|
||||
assigns a handler for a specific signal. If
|
||||
assigns a handler for a specific signal.
|
||||
If
|
||||
.Fa vec
|
||||
is non-zero, it
|
||||
specifies a handler routine and mask
|
||||
|
||||
@ -87,7 +87,7 @@ The flag value is specified by
|
||||
any of the following values:
|
||||
.Bl -tag -width indent
|
||||
.It Dv R_DUP
|
||||
Permit duplicate keys in the tree, i.e. permit insertion if the key to be
|
||||
Permit duplicate keys in the tree, i.e., permit insertion if the key to be
|
||||
inserted already exists in the tree.
|
||||
The default behavior, as described in
|
||||
.Xr dbopen 3 ,
|
||||
@ -145,7 +145,7 @@ Not currently implemented.
|
||||
.It Va minkeypage
|
||||
The minimum number of keys which will be stored on any single page.
|
||||
This value is used to determine which keys will be stored on overflow
|
||||
pages, i.e. if a key or data item is longer than the pagesize divided
|
||||
pages, i.e., if a key or data item is longer than the pagesize divided
|
||||
by the minkeypage value, it will be stored on overflow pages instead
|
||||
of in the page itself.
|
||||
If
|
||||
|
||||
@ -335,7 +335,7 @@ or
|
||||
.Va sync
|
||||
routines.
|
||||
Modifications to the database during a sequential scan will be reflected
|
||||
in the scan, i.e. records inserted behind the cursor will not be returned
|
||||
in the scan, i.e., records inserted behind the cursor will not be returned
|
||||
while records inserted in front of the cursor will be returned.
|
||||
.Pp
|
||||
The
|
||||
|
||||
@ -190,7 +190,7 @@ field of the key should be the size of that type.
|
||||
Because there can be no meta-data associated with the underlying
|
||||
.Nm
|
||||
access method files, any changes made to the default values
|
||||
(e.g. fixed record length or byte separator value) must be explicitly
|
||||
(e.g.\& fixed record length or byte separator value) must be explicitly
|
||||
specified each time the file is opened.
|
||||
.Pp
|
||||
In the interface specified by
|
||||
|
||||
@ -100,4 +100,4 @@ function first appeared in
|
||||
and
|
||||
.Fx 4.2 .
|
||||
.Sh AUTHORS
|
||||
Todd C. Miller <Todd.Miller@courtesan.com>
|
||||
.An "Todd C. Miller" Aq Todd.Miller@courtesan.com
|
||||
|
||||
@ -78,7 +78,8 @@ with it
|
||||
and
|
||||
returns a pointer to be used to identify the
|
||||
.Em directory stream
|
||||
in subsequent operations. The pointer
|
||||
in subsequent operations.
|
||||
The pointer
|
||||
.Dv NULL
|
||||
is returned if
|
||||
.Fa filename
|
||||
@ -89,7 +90,8 @@ enough memory to hold the whole thing.
|
||||
The
|
||||
.Fn readdir
|
||||
function
|
||||
returns a pointer to the next directory entry. It returns
|
||||
returns a pointer to the next directory entry.
|
||||
It returns
|
||||
.Dv NULL
|
||||
upon reaching the end of the directory or detecting an invalid
|
||||
.Fn seekdir
|
||||
@ -102,7 +104,8 @@ provides the same functionality as
|
||||
.Fn readdir ,
|
||||
but the caller must provide a directory
|
||||
.Fa entry
|
||||
buffer to store the results in. If the read succeeds,
|
||||
buffer to store the results in.
|
||||
If the read succeeds,
|
||||
.Fa result
|
||||
is pointed at the
|
||||
.Fa entry ;
|
||||
@ -126,7 +129,8 @@ are good only for the lifetime of the
|
||||
.Dv DIR
|
||||
pointer,
|
||||
.Fa dirp ,
|
||||
from which they are derived. If the directory is closed and then
|
||||
from which they are derived.
|
||||
If the directory is closed and then
|
||||
reopened, prior values returned by
|
||||
.Fn telldir
|
||||
will no longer be valid.
|
||||
|
||||
@ -107,4 +107,4 @@ function first appeared in
|
||||
and
|
||||
.Fx 4.2 .
|
||||
.Sh AUTHORS
|
||||
Todd C. Miller <Todd.Miller@courtesan.com>
|
||||
.An "Todd C. Miller" Aq Todd.Miller@courtesan.com
|
||||
|
||||
@ -93,7 +93,8 @@ The
|
||||
function first appeared in the Solaris operating system.
|
||||
.Sh BUGS
|
||||
This implementation is bug-compatible with the Solaris
|
||||
implementation. In particular, the following bugs are present:
|
||||
implementation.
|
||||
In particular, the following bugs are present:
|
||||
.Bl -bullet
|
||||
.It
|
||||
If
|
||||
@ -101,12 +102,15 @@ If
|
||||
lies in the main executable rather than in a shared library, the
|
||||
pathname returned in
|
||||
.Va dli_fname
|
||||
may not be correct. The pathname is taken directly from
|
||||
may not be correct.
|
||||
The pathname is taken directly from
|
||||
.Va argv[0]
|
||||
of the calling process. When executing a program specified by its
|
||||
of the calling process.
|
||||
When executing a program specified by its
|
||||
full pathname, most shells set
|
||||
.Va argv[0]
|
||||
to the pathname. But this is not required of shells or guaranteed
|
||||
to the pathname.
|
||||
But this is not required of shells or guaranteed
|
||||
by the operating system.
|
||||
.It
|
||||
If
|
||||
@ -115,10 +119,12 @@ is of the form
|
||||
.Va &func ,
|
||||
where
|
||||
.Va func
|
||||
is a global function, its value may be an unpleasant surprise. In
|
||||
is a global function, its value may be an unpleasant surprise.
|
||||
In
|
||||
dynamically linked programs, the address of a global function is
|
||||
considered to point to its program linkage table entry, rather than to
|
||||
the entry point of the function itself. This causes most global
|
||||
the entry point of the function itself.
|
||||
This causes most global
|
||||
functions to appear to be defined within the main executable, rather
|
||||
than in the shared libraries where the actual code resides.
|
||||
.It
|
||||
|
||||
@ -40,22 +40,26 @@
|
||||
.Sh DESCRIPTION
|
||||
.Bf Sy
|
||||
Due to enhancements in the dynamic linker, this interface is no longer
|
||||
needed. It is deprecated and will be removed from future releases.
|
||||
needed.
|
||||
It is deprecated and will be removed from future releases.
|
||||
In current releases it still exists, but only as a stub which does nothing.
|
||||
.Ef
|
||||
.Pp
|
||||
Threads packages can call
|
||||
.Fn dllockinit
|
||||
at initialization time to register locking functions for the dynamic
|
||||
linker to use. This enables the dynamic linker to prevent multiple
|
||||
linker to use.
|
||||
This enables the dynamic linker to prevent multiple
|
||||
threads from entering its critical sections simultaneously.
|
||||
.Pp
|
||||
The
|
||||
.Fa context
|
||||
argument specifies an opaque context for creating locks. The
|
||||
argument specifies an opaque context for creating locks.
|
||||
The
|
||||
dynamic linker will pass it to the
|
||||
.Fa lock_create
|
||||
function when creating the locks it needs. When the dynamic linker
|
||||
function when creating the locks it needs.
|
||||
When the dynamic linker
|
||||
is permanently finished using the locking functions (e.g., if the
|
||||
program makes a subsequent call to
|
||||
.Fn dllockinit
|
||||
@ -65,7 +69,8 @@ to destroy the context.
|
||||
.Pp
|
||||
The
|
||||
.Fa lock_create
|
||||
argument specifies a function for creating a read/write lock. It
|
||||
argument specifies a function for creating a read/write lock.
|
||||
It
|
||||
must return a pointer to the new lock.
|
||||
.Pp
|
||||
The
|
||||
@ -73,18 +78,23 @@ The
|
||||
and
|
||||
.Fa wlock_acquire
|
||||
arguments specify functions which lock a lock for reading or
|
||||
writing, respectively. The
|
||||
writing, respectively.
|
||||
The
|
||||
.Fa lock_release
|
||||
argument specifies a function which unlocks a lock. Each of these
|
||||
argument specifies a function which unlocks a lock.
|
||||
Each of these
|
||||
functions is passed a pointer to the lock.
|
||||
.Pp
|
||||
The
|
||||
.Fa lock_destroy
|
||||
argument specifies a function to destroy a lock. It may be
|
||||
argument specifies a function to destroy a lock.
|
||||
It may be
|
||||
.Dv NULL
|
||||
if locks do not need to be destroyed. The
|
||||
if locks do not need to be destroyed.
|
||||
The
|
||||
.Fa context_destroy
|
||||
argument specifies a function to destroy the context. It may be
|
||||
argument specifies a function to destroy the context.
|
||||
It may be
|
||||
.Dv NULL
|
||||
if the context does not need to be destroyed.
|
||||
.Pp
|
||||
@ -96,9 +106,11 @@ a default locking mechanism which works by blocking the
|
||||
.Dv SIGPROF ,
|
||||
and
|
||||
.Dv SIGALRM
|
||||
signals. This is sufficient for many application level threads
|
||||
signals.
|
||||
This is sufficient for many application level threads
|
||||
packages, which typically use one of these signals to implement
|
||||
preemption. An application which has registered its own locking
|
||||
preemption.
|
||||
An application which has registered its own locking
|
||||
methods with
|
||||
.Fn dllockinit
|
||||
can restore the default locking by calling
|
||||
|
||||
@ -64,7 +64,8 @@ is a valid format string.
|
||||
The
|
||||
.Xr printf 3
|
||||
family of functions cannot verify the types of arguments that they are
|
||||
passed at run-time. In some cases, like
|
||||
passed at run-time.
|
||||
In some cases, like
|
||||
.Xr catgets 3 ,
|
||||
it is useful or necessary to use a user-supplied format string with no
|
||||
guarantee that the format string matches the specified arguments.
|
||||
@ -76,10 +77,11 @@ was designed to be used in these cases, as in:
|
||||
printf(fmtcheck(user_format, standard_format), arg1, arg2);
|
||||
.Ed
|
||||
.Pp
|
||||
In the check, field widths, fillers, precisions, etc. are ignored (unless
|
||||
In the check, field widths, fillers, precisions, etc.\& are ignored (unless
|
||||
the field width or precision is an asterisk
|
||||
.Ql *
|
||||
instead of a digit string). Also, any text other than the format specifiers
|
||||
instead of a digit string).
|
||||
Also, any text other than the format specifiers
|
||||
is completely ignored.
|
||||
.Sh RETURN VALUES
|
||||
If
|
||||
@ -94,7 +96,8 @@ Otherwise, it will return
|
||||
.Fa fmt_default .
|
||||
.Sh SECURITY CONSIDERATIONS
|
||||
Note that the formats may be quite different as long as they accept the
|
||||
same arguments. For example,
|
||||
same arguments.
|
||||
For example,
|
||||
.Qq Li "%p %o %30s %#llx %-10.*e %n"
|
||||
is compatible with
|
||||
.Qq Li "This number %lu %d%% and string %s has %qd numbers and %.*g floats (%n)" .
|
||||
|
||||
@ -53,7 +53,8 @@ of an existing file and a user-selectable
|
||||
The specified
|
||||
.Fa path
|
||||
must specify an existing file that is accessible to the calling process
|
||||
or the call will fail. Also, note that links to files will return the
|
||||
or the call will fail.
|
||||
Also, note that links to files will return the
|
||||
same key, given the same
|
||||
.Fa id .
|
||||
.Sh RETURN VALUES
|
||||
|
||||
@ -202,7 +202,7 @@ A directory being visited in post-order.
|
||||
The contents of the
|
||||
.Vt FTSENT
|
||||
structure will be unchanged from when
|
||||
it was returned in pre-order, i.e. with the
|
||||
it was returned in pre-order, i.e., with the
|
||||
.Fa fts_info
|
||||
field set to
|
||||
.Dv FTS_D .
|
||||
@ -306,7 +306,7 @@ It is initialized to
|
||||
A pointer to the
|
||||
.Vt FTSENT
|
||||
structure referencing the file in the hierarchy
|
||||
immediately above the current file, i.e. the directory of which this
|
||||
immediately above the current file, i.e., the directory of which this
|
||||
file is a member.
|
||||
A parent structure for the initial entry point is provided as well,
|
||||
however, only the
|
||||
@ -601,7 +601,7 @@ has not yet been called for a hierarchy,
|
||||
.Fn fts_children
|
||||
will return a pointer to the files in the logical directory specified to
|
||||
.Fn fts_open ,
|
||||
i.e. the arguments specified to
|
||||
i.e., the arguments specified to
|
||||
.Fn fts_open .
|
||||
Otherwise, if the
|
||||
.Vt FTSENT
|
||||
|
||||
@ -54,7 +54,8 @@ A read/write interface to this information is available via the
|
||||
MIB variable
|
||||
.Dq Li kern.bootfile .
|
||||
.Sh RETURN VALUES
|
||||
If the call succeeds a string giving the pathname is returned. If it
|
||||
If the call succeeds a string giving the pathname is returned.
|
||||
If it
|
||||
fails, a null pointer is returned and an error code is
|
||||
placed in the global location
|
||||
.Va errno .
|
||||
|
||||
@ -135,9 +135,11 @@ is
|
||||
the current entry is removed from the database.
|
||||
A call to
|
||||
.Fn cgetset
|
||||
must precede the database traversal. It must be called before the
|
||||
must precede the database traversal.
|
||||
It must be called before the
|
||||
.Fn cgetent
|
||||
call. If a sequential access is being performed (see below), it must be called
|
||||
call.
|
||||
If a sequential access is being performed (see below), it must be called
|
||||
before the first sequential access call
|
||||
.Fn ( cgetfirst
|
||||
or
|
||||
@ -166,16 +168,19 @@ with type
|
||||
.Fa type .
|
||||
A
|
||||
.Fa type
|
||||
is specified using any single character. If a colon (`:') is used, an
|
||||
is specified using any single character.
|
||||
If a colon (`:') is used, an
|
||||
untyped capability will be searched for (see below for explanation of
|
||||
types). A pointer to the value of
|
||||
types).
|
||||
A pointer to the value of
|
||||
.Fa cap
|
||||
in
|
||||
.Fa buf
|
||||
is returned on success,
|
||||
.Dv NULL
|
||||
if the requested capability couldn't be
|
||||
found. The end of the capability value is signaled by a `:' or
|
||||
found.
|
||||
The end of the capability value is signaled by a `:' or
|
||||
.Tn ASCII
|
||||
.Dv NUL
|
||||
(see below for capability database syntax).
|
||||
@ -240,7 +245,8 @@ record returned by the previous
|
||||
.Fn cgetfirst
|
||||
or
|
||||
.Fn cgetnext
|
||||
call. If there is no such previous call, the first record in the database is
|
||||
call.
|
||||
If there is no such previous call, the first record in the database is
|
||||
returned.
|
||||
Each record is returned in a
|
||||
.Xr malloc 3 Ns \&'d
|
||||
@ -263,27 +269,35 @@ Upon completion of database (0 return) the database is closed.
|
||||
The
|
||||
.Fn cgetclose
|
||||
function closes the sequential access and frees any memory and file descriptors
|
||||
being used. Note that it does not erase the buffer pushed by a call to
|
||||
being used.
|
||||
Note that it does not erase the buffer pushed by a call to
|
||||
.Fn cgetset .
|
||||
.Sh CAPABILITY DATABASE SYNTAX
|
||||
Capability databases are normally
|
||||
.Tn ASCII
|
||||
and may be edited with standard
|
||||
text editors. Blank lines and lines beginning with a `#' are comments
|
||||
and are ignored. Lines ending with a `\|\e' indicate that the next line
|
||||
text editors.
|
||||
Blank lines and lines beginning with a `#' are comments
|
||||
and are ignored.
|
||||
Lines ending with a `\|\e' indicate that the next line
|
||||
is a continuation of the current line; the `\|\e' and following newline
|
||||
are ignored. Long lines are usually continued onto several physical
|
||||
are ignored.
|
||||
Long lines are usually continued onto several physical
|
||||
lines by ending each line except the last with a `\|\e'.
|
||||
.Pp
|
||||
Capability databases consist of a series of records, one per logical
|
||||
line. Each record contains a variable number of `:'-separated fields
|
||||
(capabilities). Empty fields consisting entirely of white space
|
||||
line.
|
||||
Each record contains a variable number of `:'-separated fields
|
||||
(capabilities).
|
||||
Empty fields consisting entirely of white space
|
||||
characters (spaces and tabs) are ignored.
|
||||
.Pp
|
||||
The first capability of each record specifies its names, separated by `|'
|
||||
characters. These names are used to reference records in the database.
|
||||
characters.
|
||||
These names are used to reference records in the database.
|
||||
By convention, the last name is usually a comment and is not intended as
|
||||
a lookup tag. For example, the
|
||||
a lookup tag.
|
||||
For example, the
|
||||
.Em vt100
|
||||
record from the
|
||||
.Xr termcap 5
|
||||
@ -308,16 +322,21 @@ has value
|
||||
does not exist
|
||||
.El
|
||||
.Pp
|
||||
Names consist of one or more characters. Names may contain any character
|
||||
Names consist of one or more characters.
|
||||
Names may contain any character
|
||||
except `:', but it's usually best to restrict them to the printable
|
||||
characters and avoid use of graphics like `#', `=', `%', `@', etc. Types
|
||||
characters and avoid use of graphics like `#', `=', `%', `@', etc.\& Types
|
||||
are single characters used to separate capability names from their
|
||||
associated typed values. Types may be any character except a `:'.
|
||||
Typically, graphics like `#', `=', `%', etc. are used. Values may be any
|
||||
associated typed values.
|
||||
Types may be any character except a `:'.
|
||||
Typically, graphics like `#', `=', `%', etc.\& are used.
|
||||
Values may be any
|
||||
number of characters and may contain any character except `:'.
|
||||
.Sh CAPABILITY DATABASE SEMANTICS
|
||||
Capability records describe a set of (name, value) bindings. Names may
|
||||
have multiple values bound to them. Different values for a name are
|
||||
Capability records describe a set of (name, value) bindings.
|
||||
Names may
|
||||
have multiple values bound to them.
|
||||
Different values for a name are
|
||||
distinguished by their
|
||||
.Fa types .
|
||||
The
|
||||
@ -326,7 +345,8 @@ function will return a pointer to a value of a name given the capability
|
||||
name and the type of the value.
|
||||
.Pp
|
||||
The types `#' and `=' are conventionally used to denote numeric and
|
||||
string typed values, but no restriction on those types is enforced. The
|
||||
string typed values, but no restriction on those types is enforced.
|
||||
The
|
||||
functions
|
||||
.Fn cgetnum
|
||||
and
|
||||
@ -351,7 +371,8 @@ capabilities may interpolate records which also contain
|
||||
.Ic tc
|
||||
capabilities and more than one
|
||||
.Ic tc
|
||||
capability may be used in a record. A
|
||||
capability may be used in a record.
|
||||
A
|
||||
.Ic tc
|
||||
expansion scope (i.e., where the argument is searched for) contains the
|
||||
file in which the
|
||||
@ -359,7 +380,8 @@ file in which the
|
||||
is declared and all subsequent files in the file array.
|
||||
.Pp
|
||||
When a database is searched for a capability record, the first matching
|
||||
record in the search is returned. When a record is scanned for a
|
||||
record in the search is returned.
|
||||
When a record is scanned for a
|
||||
capability, the first matching capability is returned; the capability
|
||||
.Ic :nameT@:
|
||||
will hide any following definition of a value of type
|
||||
@ -386,7 +408,8 @@ example\||\|an example of binding multiple values to names:\e
|
||||
.Ed
|
||||
.Pp
|
||||
The capability foo has two values bound to it (bar of type `%' and blah of
|
||||
type `^') and any other value bindings are hidden. The capability abc
|
||||
type `^') and any other value bindings are hidden.
|
||||
The capability abc
|
||||
also has two values bound but only a value of type `$' is prevented from
|
||||
being defined in the capability record more.
|
||||
.Pp
|
||||
@ -408,7 +431,8 @@ who-cares@ prevents the definition of any who-cares definitions in old
|
||||
from being seen, glork#200 is inherited from old, and blah and anything
|
||||
defined by the record extensions is added to those definitions in old.
|
||||
Note that the position of the fript=bar and who-cares@ definitions before
|
||||
tc=old is important here. If they were after, the definitions in old
|
||||
tc=old is important here.
|
||||
If they were after, the definitions in old
|
||||
would take precedence.
|
||||
.Sh CGETNUM AND CGETSTR SYNTAX AND SEMANTICS
|
||||
Two types are predefined by
|
||||
@ -453,7 +477,8 @@ Otherwise, if the number starts with a
|
||||
it is interpreted as an octal number.
|
||||
Otherwise the number is interpreted as a decimal number.
|
||||
.Pp
|
||||
String capability values may contain any character. Non-printable
|
||||
String capability values may contain any character.
|
||||
Non-printable
|
||||
.Dv ASCII
|
||||
codes, new lines, and colons may be conveniently represented by the use
|
||||
of escape sequences:
|
||||
@ -472,7 +497,8 @@ of escape sequences:
|
||||
.El
|
||||
.Pp
|
||||
A `\|\e' may be followed by up to three octal digits directly specifies
|
||||
the numeric code for a character. The use of
|
||||
the numeric code for a character.
|
||||
The use of
|
||||
.Tn ASCII
|
||||
.Dv NUL Ns s ,
|
||||
while easily
|
||||
|
||||
@ -52,7 +52,8 @@ takes a disk name (e.g.\&
|
||||
.Ql rm03 )
|
||||
and returns a prototype disk label
|
||||
describing its geometry information and the standard
|
||||
disk partition tables. All information is obtained from
|
||||
disk partition tables.
|
||||
All information is obtained from
|
||||
the
|
||||
.Xr disktab 5
|
||||
file.
|
||||
|
||||
@ -59,7 +59,8 @@ The
|
||||
argument
|
||||
specifies the size of the
|
||||
.Fa name
|
||||
array. The returned name is null-terminated unless insufficient
|
||||
array.
|
||||
The returned name is null-terminated unless insufficient
|
||||
space is provided.
|
||||
.Pp
|
||||
The
|
||||
|
||||
@ -96,7 +96,8 @@ search the group database for the given group name pointed to by
|
||||
.Fa name
|
||||
or the group id pointed to by
|
||||
.Fa gid ,
|
||||
respectively, returning the first one encountered. Identical group
|
||||
respectively, returning the first one encountered.
|
||||
Identical group
|
||||
names or group gids may result in undefined behavior.
|
||||
.Pp
|
||||
The
|
||||
@ -139,12 +140,15 @@ These functions will open the group file for reading, if necessary.
|
||||
The
|
||||
.Fn setgroupent
|
||||
function
|
||||
opens the file, or rewinds it if it is already open. If
|
||||
opens the file, or rewinds it if it is already open.
|
||||
If
|
||||
.Fa stayopen
|
||||
is non-zero, file descriptors are left open, significantly speeding
|
||||
functions subsequent calls. This functionality is unnecessary for
|
||||
functions subsequent calls.
|
||||
This functionality is unnecessary for
|
||||
.Fn getgrent
|
||||
as it doesn't close its file descriptors by default. It should also
|
||||
as it doesn't close its file descriptors by default.
|
||||
It should also
|
||||
be noted that it is dangerous for long-running programs to use this
|
||||
functionality as the group file may be updated.
|
||||
.Pp
|
||||
|
||||
@ -43,7 +43,8 @@ function
|
||||
queries several sources to determine the preferred object file
|
||||
format, and copies its name into a buffer provided by the caller.
|
||||
.Pp
|
||||
The object file format is determined as follows. If
|
||||
The object file format is determined as follows.
|
||||
If
|
||||
.Va argv
|
||||
is
|
||||
.No non- Ns Ev NULL
|
||||
@ -70,9 +71,11 @@ Otherwise, a built-in system default object file format is returned.
|
||||
points to a user-supplied buffer into which the name of the object
|
||||
file format is copied.
|
||||
.Va bufsize
|
||||
gives the size of the buffer in bytes. The string placed in
|
||||
gives the size of the buffer in bytes.
|
||||
The string placed in
|
||||
.Va buf
|
||||
is always null-terminated. It is an error if the buffer is too
|
||||
is always null-terminated.
|
||||
It is an error if the buffer is too
|
||||
small to hold the null-terminated name.
|
||||
.Pp
|
||||
.Va argv
|
||||
@ -104,7 +107,8 @@ null terminator.
|
||||
If the supplied buffer is too small to hold the object file format
|
||||
and its null terminator,
|
||||
.Fn getobjformat
|
||||
returns -1. In that case, the contents of the buffer and argument
|
||||
returns -1.
|
||||
In that case, the contents of the buffer and argument
|
||||
vector supplied by the caller are indeterminate.
|
||||
.Sh ENVIRONMENT
|
||||
.Bl -tag -width OBJFORMAT
|
||||
@ -118,7 +122,8 @@ is set, it overrides the default object file format.
|
||||
.Sh FILES
|
||||
.Bl -tag -width /etc/objformat -compact
|
||||
.It Pa /etc/objformat
|
||||
If present, specifies the object file format to use. Syntax is
|
||||
If present, specifies the object file format to use.
|
||||
Syntax is
|
||||
.Ql OBJFORMAT=xxx .
|
||||
.El
|
||||
.Sh SEE ALSO
|
||||
|
||||
@ -102,7 +102,8 @@ unlocked.
|
||||
The section to be locked or unlocked starts at the current
|
||||
offset in the file and extends forward for a positive size or backward
|
||||
for a negative size (the preceding bytes up to but not including the
|
||||
current offset). However, it is not permitted to lock a section that
|
||||
current offset).
|
||||
However, it is not permitted to lock a section that
|
||||
starts or extends before the beginning of the file.
|
||||
If
|
||||
.Fa size
|
||||
@ -142,7 +143,8 @@ controlled by the process.
|
||||
Locked sections will be unlocked starting
|
||||
at the current file offset through
|
||||
.Fa size
|
||||
bytes or to the end of file if size is 0. When all of a locked section
|
||||
bytes or to the end of file if size is 0.
|
||||
When all of a locked section
|
||||
is not released (that is, when the beginning or end of the area to be
|
||||
unlocked falls within a locked section), the remaining portions of
|
||||
that section are still locked by the process.
|
||||
@ -160,13 +162,15 @@ the requested section is the maximum value for an object of type
|
||||
off_t, when the process has an existing lock in which size is 0 and
|
||||
which includes the last byte of the requested section, will be treated
|
||||
as a request to unlock from the start of the requested section with a
|
||||
size equal to 0. Otherwise an
|
||||
size equal to 0.
|
||||
Otherwise an
|
||||
.Dv F_ULOCK
|
||||
request will attempt to unlock only the requested section.
|
||||
.Pp
|
||||
A potential for deadlock occurs if a process controlling a locked
|
||||
region is put to sleep by attempting to lock the locked region of
|
||||
another process. This implementation detects that sleeping until a
|
||||
another process.
|
||||
This implementation detects that sleeping until a
|
||||
locked region is unlocked would cause a deadlock and fails with an
|
||||
.Er EDEADLK
|
||||
error.
|
||||
|
||||
@ -72,19 +72,22 @@ has one of the following meanings:
|
||||
The
|
||||
.Fa msgtyp
|
||||
argument
|
||||
is greater than 0. The first message of type
|
||||
is greater than 0.
|
||||
The first message of type
|
||||
.Fa msgtyp
|
||||
will be received.
|
||||
.It
|
||||
The
|
||||
.Fa msgtyp
|
||||
argument
|
||||
is equal to 0. The first message on the queue will be received.
|
||||
is equal to 0.
|
||||
The first message on the queue will be received.
|
||||
.It
|
||||
The
|
||||
.Fa msgtyp
|
||||
argument
|
||||
is less than 0. The first message of the lowest message type that is
|
||||
is less than 0.
|
||||
The first message of the lowest message type that is
|
||||
less than or equal to the absolute value of
|
||||
.Fa msgtyp
|
||||
will be received.
|
||||
@ -133,7 +136,8 @@ The message queue is removed, in which case -1 will be returned, and
|
||||
set to
|
||||
.Er EINVAL .
|
||||
.It
|
||||
A signal is received and caught. -1 is returned, and
|
||||
A signal is received and caught.
|
||||
-1 is returned, and
|
||||
.Va errno
|
||||
set to
|
||||
.Er EINTR .
|
||||
|
||||
@ -81,7 +81,8 @@ and
|
||||
.Fn nrand48
|
||||
functions
|
||||
return values of type long in the range
|
||||
[0, 2**31-1]. The high-order (31) bits of
|
||||
[0, 2**31-1].
|
||||
The high-order (31) bits of
|
||||
r(n+1) are loaded into the lower bits of the returned value, with
|
||||
the topmost (sign) bit set to zero.
|
||||
.Pp
|
||||
@ -91,7 +92,8 @@ and
|
||||
.Fn jrand48
|
||||
functions
|
||||
return values of type long in the range
|
||||
[-2**31, 2**31-1]. The high-order (32) bits of
|
||||
[-2**31, 2**31-1].
|
||||
The high-order (32) bits of
|
||||
r(n+1) are loaded into the returned value.
|
||||
.Pp
|
||||
The
|
||||
@ -100,7 +102,8 @@ The
|
||||
and
|
||||
.Fn mrand48
|
||||
functions
|
||||
use an internal buffer to store r(n). For these functions
|
||||
use an internal buffer to store r(n).
|
||||
For these functions
|
||||
the initial value of r(0) = 0x1234abcd330e = 20017429951246.
|
||||
.Pp
|
||||
On the other hand,
|
||||
|
||||
@ -90,7 +90,7 @@ call had just returned the value specified by
|
||||
.Fa val ,
|
||||
instead of 0.
|
||||
.Pp
|
||||
Pairs of calls may be intermixed, i.e. both
|
||||
Pairs of calls may be intermixed, i.e., both
|
||||
.Fn sigsetjmp
|
||||
and
|
||||
.Fn siglongjmp
|
||||
@ -99,7 +99,7 @@ and
|
||||
and
|
||||
.Fn longjmp
|
||||
combinations may be used in the same program, however, individual
|
||||
calls may not, e.g. the
|
||||
calls may not, e.g.\& the
|
||||
.Fa env
|
||||
argument to
|
||||
.Fn setjmp
|
||||
|
||||
@ -68,10 +68,12 @@ setproctitle("talking to %s", inet_ntoa(addr));
|
||||
The
|
||||
.Fn setproctitle
|
||||
function
|
||||
is implicitly non-standard. Other methods of causing the
|
||||
is implicitly non-standard.
|
||||
Other methods of causing the
|
||||
.Xr ps 1
|
||||
command line to change, including copying over the argv[0] string are
|
||||
also implicitly non-portable. It is preferable to use an operating system
|
||||
also implicitly non-portable.
|
||||
It is preferable to use an operating system
|
||||
supplied
|
||||
.Fn setproctitle
|
||||
if present.
|
||||
@ -79,7 +81,8 @@ if present.
|
||||
Unfortunately, it is possible that there are other calling conventions
|
||||
to other versions of
|
||||
.Fn setproctitle ,
|
||||
although none have been found by the author as yet. This is believed to be
|
||||
although none have been found by the author as yet.
|
||||
This is believed to be
|
||||
the predominant convention.
|
||||
.Pp
|
||||
It is thought that the implementation is compatible with other systems,
|
||||
|
||||
@ -150,7 +150,8 @@ functions can fail with any error defined for
|
||||
.Fn open
|
||||
and
|
||||
.Fn unlink ,
|
||||
respectively. In addition, the following errors are defined for
|
||||
respectively.
|
||||
In addition, the following errors are defined for
|
||||
.Fn shm_open :
|
||||
.Bl -tag -width Er
|
||||
.It Bq Er EINVAL
|
||||
|
||||
@ -63,7 +63,8 @@ facility.
|
||||
.Pp
|
||||
Signals allow the manipulation of a process from outside its
|
||||
domain as well as allowing the process to manipulate itself or
|
||||
copies of itself (children). There are two general types of signals:
|
||||
copies of itself (children).
|
||||
There are two general types of signals:
|
||||
those that cause termination of a process and those that do not.
|
||||
Signals which cause termination of a program might result from
|
||||
an irrecoverable error or might be the result of a user at a terminal
|
||||
|
||||
@ -66,7 +66,8 @@ and there is no special handling for SIGALRM.
|
||||
If the
|
||||
.Fn sleep
|
||||
function returns because the requested time has elapsed, the value
|
||||
returned will be zero. If the
|
||||
returned will be zero.
|
||||
If the
|
||||
.Fn sleep
|
||||
function returns due to the delivery of a signal, the value returned
|
||||
will be the unslept amount (the requested time minus the time actually
|
||||
|
||||
@ -83,7 +83,8 @@ length array of integers.
|
||||
The
|
||||
.Fn sysctlbyname
|
||||
function accepts an ASCII representation of the name and internally
|
||||
looks up the integer name vector. Apart from that, it behaves the same
|
||||
looks up the integer name vector.
|
||||
Apart from that, it behaves the same
|
||||
as the standard
|
||||
.Fn sysctl
|
||||
function.
|
||||
@ -454,7 +455,7 @@ The third and fourth level names are as follows:
|
||||
.El
|
||||
.Pp
|
||||
If the third level name is KERN_PROC_ARGS then the command line argument
|
||||
array is returned in a flattened form, i.e. zero-terminated arguments
|
||||
array is returned in a flattened form, i.e., zero-terminated arguments
|
||||
follow each other.
|
||||
The total size of array is returned.
|
||||
It is also possible for a process to set its own process title this way.
|
||||
@ -752,12 +753,14 @@ The returned data consists of a
|
||||
0 if the statistics-based page management algorithm is in use
|
||||
or 1 if the near-LRU algorithm is in use.
|
||||
.It Li VM_SWAPPING_ENABLED
|
||||
1 if process swapping is enabled or 0 if disabled. This variable is
|
||||
1 if process swapping is enabled or 0 if disabled.
|
||||
This variable is
|
||||
permanently set to 0 if the kernel was built with swapping disabled.
|
||||
.It Li VM_V_CACHE_MAX
|
||||
Maximum desired size of the cache queue.
|
||||
.It Li VM_V_CACHE_MIN
|
||||
Minimum desired size of the cache queue. If the cache queue size
|
||||
Minimum desired size of the cache queue.
|
||||
If the cache queue size
|
||||
falls very far below this value, the pageout daemon is awakened.
|
||||
.It Li VM_V_FREE_MIN
|
||||
Minimum amount of memory (cache memory plus free memory)
|
||||
@ -771,7 +774,8 @@ The total amount of free memory (including cache memory) that the
|
||||
pageout daemon tries to maintain.
|
||||
.It Li VM_V_INACTIVE_TARGET
|
||||
The desired number of inactive pages that the pageout daemon should
|
||||
achieve when it runs. Inactive pages can be quickly inserted into
|
||||
achieve when it runs.
|
||||
Inactive pages can be quickly inserted into
|
||||
process address space when needed.
|
||||
.It Li VM_V_PAGEOUT_FREE_MIN
|
||||
If the amount of free and cache memory falls below this value, the
|
||||
|
||||
@ -131,12 +131,14 @@ Three or more bytes that are the designation for the standard
|
||||
.Pq Em std
|
||||
or summer
|
||||
.Pq Em dst
|
||||
time zone. Only
|
||||
time zone.
|
||||
Only
|
||||
.Em std
|
||||
is required; if
|
||||
.Em dst
|
||||
is missing, then summer time does not apply in this locale.
|
||||
Upper and lowercase letters are explicitly allowed. Any characters
|
||||
Upper and lowercase letters are explicitly allowed.
|
||||
Any characters
|
||||
except a leading colon
|
||||
.Pq Ql \&: ,
|
||||
digits, comma
|
||||
@ -151,7 +153,8 @@ and
|
||||
are allowed.
|
||||
.It Em offset
|
||||
Indicates the value one must add to the local time to arrive at
|
||||
Coordinated Universal Time. The
|
||||
Coordinated Universal Time.
|
||||
The
|
||||
.Em offset
|
||||
has the form:
|
||||
.Bd -ragged -offset indent
|
||||
@ -167,26 +170,33 @@ The minutes
|
||||
.Pq Em mm
|
||||
and seconds
|
||||
.Pq Em ss
|
||||
are optional. The hour
|
||||
are optional.
|
||||
The hour
|
||||
.Pq Em hh
|
||||
is required and may be a single digit. The
|
||||
is required and may be a single digit.
|
||||
The
|
||||
.Em offset
|
||||
following
|
||||
.Em std
|
||||
is required. If no
|
||||
is required.
|
||||
If no
|
||||
.Em offset
|
||||
follows
|
||||
.Em dst ,
|
||||
summer time is assumed to be one hour ahead of standard time. One or
|
||||
summer time is assumed to be one hour ahead of standard time.
|
||||
One or
|
||||
more digits may be used; the value is always interpreted as a decimal
|
||||
number. The hour must be between zero and 24, and the minutes (and
|
||||
seconds) \(em if present \(em between zero and 59. If preceded by a
|
||||
number.
|
||||
The hour must be between zero and 24, and the minutes (and
|
||||
seconds) \(em if present \(em between zero and 59.
|
||||
If preceded by a
|
||||
.Pq Ql \-
|
||||
the time zone shall be east of the Prime Meridian; otherwise it shall be
|
||||
west (which may be indicated by an optional preceding
|
||||
.Pq Ql + ) .
|
||||
.It Em rule
|
||||
Indicates when to change to and back from summer time. The
|
||||
Indicates when to change to and back from summer time.
|
||||
The
|
||||
.Em rule
|
||||
has the form:
|
||||
.Bd -ragged -offset indent
|
||||
@ -198,7 +208,8 @@ where the first
|
||||
describes when the change from standard to summer time occurs and the
|
||||
second
|
||||
.Em date
|
||||
describes when the change back happens. Each
|
||||
describes when the change back happens.
|
||||
Each
|
||||
.Em time
|
||||
field describes when, in current local time, the change to the other
|
||||
time is made.
|
||||
@ -214,7 +225,8 @@ The Julian day
|
||||
.Em n
|
||||
\*(Le 365).
|
||||
Leap days are not counted; that is, in all years \(em including leap
|
||||
years \(em February 28 is day 59 and March 1 is day 60. It is
|
||||
years \(em February 28 is day 59 and March 1 is day 60.
|
||||
It is
|
||||
impossible to explicitly refer to the occasional February 29.
|
||||
.It Em n
|
||||
The zero-based Julian day
|
||||
@ -246,10 +258,12 @@ the last
|
||||
day in month
|
||||
.Em m
|
||||
.Dc
|
||||
which may occur in either the fourth or the fifth week). Week 1 is the
|
||||
which may occur in either the fourth or the fifth week).
|
||||
Week 1 is the
|
||||
first week in which the
|
||||
.Em d Ns 'th
|
||||
day occurs. Day zero is Sunday.
|
||||
day occurs.
|
||||
Day zero is Sunday.
|
||||
.Pp
|
||||
The
|
||||
.Em time
|
||||
@ -259,7 +273,8 @@ except that no leading sign
|
||||
.Pq Ql \-
|
||||
or
|
||||
.Pq Ql +
|
||||
is allowed. The default, if
|
||||
is allowed.
|
||||
The default, if
|
||||
.Em time
|
||||
is not given, is
|
||||
.Sy 02:00:00 .
|
||||
|
||||
@ -67,7 +67,7 @@ argument is non-zero, the
|
||||
signal will be sent
|
||||
to the process every
|
||||
.Fa interval
|
||||
microseconds after the timer expires (e.g. after
|
||||
microseconds after the timer expires (e.g.\& after
|
||||
.Fa microseconds
|
||||
number of microseconds have passed).
|
||||
.Pp
|
||||
|
||||
@ -60,7 +60,8 @@ are used to decode a visual representation of characters, as produced
|
||||
by the
|
||||
.Xr vis 3
|
||||
function, back into
|
||||
the original form. Unvis is called with successive characters in
|
||||
the original form.
|
||||
Unvis is called with successive characters in
|
||||
.Fa c
|
||||
until a valid
|
||||
sequence is recognized, at which time the decoded character is
|
||||
@ -83,7 +84,8 @@ decoding any escape sequences along the way,
|
||||
and returns the number of characters placed into
|
||||
.Fa dst ,
|
||||
or \-1 if an
|
||||
invalid escape sequence was detected. The size of
|
||||
invalid escape sequence was detected.
|
||||
The size of
|
||||
.Fa dst
|
||||
should be
|
||||
equal to the size of
|
||||
@ -106,20 +108,24 @@ The
|
||||
.Fn unvis
|
||||
function
|
||||
implements a state machine that can be used to decode an arbitrary
|
||||
stream of bytes. All state associated with the bytes being decoded
|
||||
stream of bytes.
|
||||
All state associated with the bytes being decoded
|
||||
is stored outside the
|
||||
.Fn unvis
|
||||
function (that is, a pointer to the state is passed in), so
|
||||
calls decoding different streams can be freely intermixed. To
|
||||
calls decoding different streams can be freely intermixed.
|
||||
To
|
||||
start decoding a stream of bytes, first initialize an integer
|
||||
to zero. Call
|
||||
to zero.
|
||||
Call
|
||||
.Fn unvis
|
||||
with each successive byte, along with a pointer
|
||||
to this integer, and a pointer to a destination character.
|
||||
The
|
||||
.Fn unvis
|
||||
function
|
||||
has several return codes that must be handled properly. They are:
|
||||
has several return codes that must be handled properly.
|
||||
They are:
|
||||
.Bl -tag -width UNVIS_VALIDPUSH
|
||||
.It Li \&0 (zero)
|
||||
Another character is necessary; nothing has been recognized yet.
|
||||
@ -131,11 +137,13 @@ A valid character has been recognized and is available at the location
|
||||
pointed to by cp; however, the character currently passed in should
|
||||
be passed in again.
|
||||
.It Dv UNVIS_NOCHAR
|
||||
A valid sequence was detected, but no character was produced. This
|
||||
A valid sequence was detected, but no character was produced.
|
||||
This
|
||||
return code is necessary to indicate a logical break between characters.
|
||||
.It Dv UNVIS_SYNBAD
|
||||
An invalid escape sequence was detected, or the decoder is in an
|
||||
unknown state. The decoder is placed into the starting state.
|
||||
unknown state.
|
||||
The decoder is placed into the starting state.
|
||||
.El
|
||||
.Pp
|
||||
When all bytes in the stream have been processed, call
|
||||
|
||||
@ -58,9 +58,11 @@ a string which represents the character
|
||||
.Fa c .
|
||||
If
|
||||
.Fa c
|
||||
needs no encoding, it is copied in unaltered. The string is
|
||||
needs no encoding, it is copied in unaltered.
|
||||
The string is
|
||||
null terminated, and a pointer to the end of the string is
|
||||
returned. The maximum length of any encoding is four
|
||||
returned.
|
||||
The maximum length of any encoding is four
|
||||
characters (not including the trailing
|
||||
.Dv NUL ) ;
|
||||
thus, when
|
||||
@ -160,9 +162,11 @@ Synonym for
|
||||
\&|
|
||||
.Dv VIS_NL .
|
||||
.It Dv VIS_SAFE
|
||||
Only encode "unsafe" characters. Unsafe means control
|
||||
Only encode "unsafe" characters.
|
||||
Unsafe means control
|
||||
characters which may cause common terminals to perform
|
||||
unexpected functions. Currently this form allows space,
|
||||
unexpected functions.
|
||||
Currently this form allows space,
|
||||
tab, newline, backspace, bell, and return - in addition
|
||||
to all graphic characters - unencoded.
|
||||
.El
|
||||
@ -259,7 +263,8 @@ where
|
||||
.Ar d
|
||||
represents a hexadecimal digit.
|
||||
.It Dv VIS_OCTAL
|
||||
Use a three digit octal sequence. The form is
|
||||
Use a three digit octal sequence.
|
||||
The form is
|
||||
.Ql \eddd
|
||||
where
|
||||
.Ar d
|
||||
|
||||
@ -45,7 +45,8 @@ The
|
||||
system call
|
||||
will return the permission for the process' I/O port space in the
|
||||
.Fa *enable
|
||||
argument. The port range starts at
|
||||
argument.
|
||||
The port range starts at
|
||||
.Fa start
|
||||
and the number of contiguous entries will be returned in
|
||||
.Fa *length .
|
||||
|
||||
@ -54,11 +54,14 @@ The
|
||||
.Fn i386_set_watch
|
||||
function
|
||||
will set up the specified debug registers as indicated by the
|
||||
arguments. The
|
||||
arguments.
|
||||
The
|
||||
.Fa watchnum
|
||||
argument specifies which watch register is used, 0, 1, 2, 3, or -1. If
|
||||
argument specifies which watch register is used, 0, 1, 2, 3, or -1.
|
||||
If
|
||||
.Fa watchnum
|
||||
is -1, a free watch register is found and used. If there are no free
|
||||
is -1, a free watch register is found and used.
|
||||
If there are no free
|
||||
watch registers, an error code of -1 is returned.
|
||||
The
|
||||
.Fa watchaddr
|
||||
@ -78,7 +81,8 @@ DBREG_DR7_RDWR Break when the watch area is read from or written
|
||||
.Ed
|
||||
.Pp
|
||||
Note that these functions do not actually set or clear breakpoints;
|
||||
they manipulate the indicated debug register set. You must use
|
||||
they manipulate the indicated debug register set.
|
||||
You must use
|
||||
.Xr ptrace 2
|
||||
to retrieve and install the debug register values for a process.
|
||||
.Sh RETURN VALUES
|
||||
@ -96,7 +100,8 @@ will return the
|
||||
.Fa watchnum
|
||||
argument, or the watchnum actually used in the case that
|
||||
.Fa watchnum
|
||||
is -1 on success. On error,
|
||||
is -1 on success.
|
||||
On error,
|
||||
.Fn i386_set_watch
|
||||
will return -1 indicating that the watchpoint could not be set up
|
||||
because either no more watchpoints are available, or
|
||||
|
||||
@ -191,7 +191,8 @@ function operates the same as
|
||||
.Fn sgetrune
|
||||
with the exception that it attempts to read enough bytes from
|
||||
.Fa stream
|
||||
to decode a single rune. It returns either
|
||||
to decode a single rune.
|
||||
It returns either
|
||||
.Dv EOF
|
||||
on end of file,
|
||||
.Dv _INVALID_RUNE
|
||||
|
||||
@ -81,7 +81,8 @@ and
|
||||
functions.
|
||||
This controls recognition of upper and lower case,
|
||||
alphabetic or non-alphabetic characters,
|
||||
and so on. The real work is done by the
|
||||
and so on.
|
||||
The real work is done by the
|
||||
.Fn setrunelocale
|
||||
function.
|
||||
.It Dv LC_MESSAGES
|
||||
|
||||
@ -61,9 +61,11 @@ Unicode Standard.
|
||||
.Pp
|
||||
.Nm UTF2
|
||||
representation is backwards compatible with ASCII, so 0x00-0x7f refer to the
|
||||
ASCII character set. The multibyte encodings of wide characters between
|
||||
ASCII character set.
|
||||
The multibyte encodings of wide characters between
|
||||
0x0080 and 0xffff
|
||||
consist entirely of bytes whose high order bit is set. The actual
|
||||
consist entirely of bytes whose high order bit is set.
|
||||
The actual
|
||||
encoding is represented by the following table:
|
||||
.Bd -literal
|
||||
[0x0000 - 0x007f] [00000000.0bbbbbbb] -> 0bbbbbbb
|
||||
|
||||
@ -52,7 +52,8 @@ The routines
|
||||
and
|
||||
.Fn ascii2addr
|
||||
are used to convert network addresses between binary form and a
|
||||
printable form appropriate to the address family. Both functions take
|
||||
printable form appropriate to the address family.
|
||||
Both functions take
|
||||
an
|
||||
.Fa af
|
||||
argument, specifying the address family to be used in the conversion
|
||||
@ -67,14 +68,17 @@ The
|
||||
.Fn addr2ascii
|
||||
function
|
||||
is used to convert binary, network-format addresses into printable
|
||||
form. In addition to
|
||||
form.
|
||||
In addition to
|
||||
.Fa af ,
|
||||
there are three other arguments. The
|
||||
there are three other arguments.
|
||||
The
|
||||
.Fa addrp
|
||||
argument is a pointer to the network address to be converted.
|
||||
The
|
||||
.Fa len
|
||||
argument is the length of the address. The
|
||||
argument is the length of the address.
|
||||
The
|
||||
.Fa buf
|
||||
argument is an optional pointer to a caller-allocated buffer to hold
|
||||
the result; if a null pointer is passed,
|
||||
@ -94,7 +98,8 @@ and
|
||||
The
|
||||
.Fa ascii
|
||||
argument is a pointer to the string which is to be converted into
|
||||
binary. The
|
||||
binary.
|
||||
The
|
||||
.Fa result
|
||||
argument is a pointer to an appropriate network address structure for
|
||||
the specified family.
|
||||
@ -192,7 +197,8 @@ was improperly formatted for address family
|
||||
.Xr inet 4
|
||||
.Sh HISTORY
|
||||
An interface close to this one was originally suggested by Craig
|
||||
Partridge. This particular interface originally appeared in the
|
||||
Partridge.
|
||||
This particular interface originally appeared in the
|
||||
.Tn INRIA
|
||||
.Tn IPv6
|
||||
implementation.
|
||||
@ -201,8 +207,10 @@ Code and documentation by
|
||||
.An Garrett A. Wollman ,
|
||||
MIT Laboratory for Computer Science.
|
||||
.Sh BUGS
|
||||
The original implementations supported IPv6. This support should
|
||||
eventually be resurrected. The
|
||||
The original implementations supported IPv6.
|
||||
This support should
|
||||
eventually be resurrected.
|
||||
The
|
||||
.Tn NRL
|
||||
implementation also included support for the
|
||||
.Dv AF_ISO
|
||||
@ -210,13 +218,16 @@ and
|
||||
.Dv AF_NS
|
||||
address families.
|
||||
.Pp
|
||||
The genericity of this interface is somewhat questionable. A truly
|
||||
The genericity of this interface is somewhat questionable.
|
||||
A truly
|
||||
generic interface would provide a means for determining the length of
|
||||
the buffer to be used so that it could be dynamically allocated, and
|
||||
would always require a
|
||||
.Dq Li "struct sockaddr"
|
||||
to hold the binary address. Unfortunately, this is incompatible with existing
|
||||
practice. This limitation means that a routine for printing network
|
||||
to hold the binary address.
|
||||
Unfortunately, this is incompatible with existing
|
||||
practice.
|
||||
This limitation means that a routine for printing network
|
||||
addresses from arbitrary address families must still have internal
|
||||
knowledge of the maximum buffer length needed and the appropriate part
|
||||
of the address to use as the binary address.
|
||||
|
||||
@ -85,4 +85,5 @@ functions appeared in
|
||||
On the
|
||||
.Tn VAX
|
||||
bytes are handled backwards from most everyone else in
|
||||
the world. This is not expected to be fixed in the near future.
|
||||
the world.
|
||||
This is not expected to be fixed in the near future.
|
||||
|
||||
@ -107,7 +107,7 @@ should point to an address which is
|
||||
.Fa len
|
||||
bytes long,
|
||||
in binary form
|
||||
(i.e. not an IP address in human readable
|
||||
(i.e., not an IP address in human readable
|
||||
.Tn ASCII
|
||||
form).
|
||||
The
|
||||
|
||||
@ -110,7 +110,8 @@ if one exists, otherwise it is NULL.
|
||||
.Pp
|
||||
The
|
||||
.Li ifa_data
|
||||
field references address family specific data. For
|
||||
field references address family specific data.
|
||||
For
|
||||
.Dv AF_LINK
|
||||
addresses it contains a pointer to the
|
||||
.Fa struct if_data
|
||||
|
||||
@ -217,15 +217,19 @@ flag then the caller wants all addresses: IPv6 and IPv4-mapped IPv6.
|
||||
A query is first made for
|
||||
.Li AAAA
|
||||
records and if successful, the
|
||||
IPv6 addresses are returned. Another query is then made for
|
||||
IPv6 addresses are returned.
|
||||
Another query is then made for
|
||||
.Li A
|
||||
records and any found are returned as IPv4-mapped IPv6 addresses.
|
||||
.Li h_length
|
||||
will be 16. Only if both queries fail does the function
|
||||
will be 16.
|
||||
Only if both queries fail does the function
|
||||
return a
|
||||
.Dv NULL
|
||||
pointer. This flag is ignored unless af equals
|
||||
AF_INET6. If both
|
||||
pointer.
|
||||
This flag is ignored unless af equals
|
||||
AF_INET6.
|
||||
If both
|
||||
.Dv AI_ALL
|
||||
and
|
||||
.Dv AI_V4MAPPED
|
||||
|
||||
@ -72,7 +72,8 @@ broken-out fields of a line in the network data base
|
||||
.Pa /etc/networks ,
|
||||
or entries supplied by the
|
||||
.Xr yp 8
|
||||
system. The order of the lookups is controlled by the
|
||||
system.
|
||||
The order of the lookups is controlled by the
|
||||
`networks' entry in
|
||||
.Xr nsswitch.conf 5 .
|
||||
.Pp
|
||||
@ -94,7 +95,8 @@ A zero terminated list of alternate names for the network.
|
||||
.It Fa n_addrtype
|
||||
The type of the network number returned; currently only AF_INET.
|
||||
.It Fa n_net
|
||||
The network number. Network numbers are returned in machine byte
|
||||
The network number.
|
||||
Network numbers are returned in machine byte
|
||||
order.
|
||||
.El
|
||||
.Pp
|
||||
@ -106,7 +108,8 @@ reads the next line of the file, opening the file if necessary.
|
||||
The
|
||||
.Fn setnetent
|
||||
function
|
||||
opens and rewinds the file. If the
|
||||
opens and rewinds the file.
|
||||
If the
|
||||
.Fa stayopen
|
||||
flag is non-zero,
|
||||
the net data base will not be closed after each call to
|
||||
|
||||
@ -95,7 +95,8 @@ reads the next line of the file, opening the file if necessary.
|
||||
The
|
||||
.Fn setprotoent
|
||||
function
|
||||
opens and rewinds the file. If the
|
||||
opens and rewinds the file.
|
||||
If the
|
||||
.Fa stayopen
|
||||
flag is non-zero,
|
||||
the net data base will not be closed after each call to
|
||||
|
||||
@ -99,7 +99,8 @@ reads the next line of the file, opening the file if necessary.
|
||||
The
|
||||
.Fn setservent
|
||||
function
|
||||
opens and rewinds the file. If the
|
||||
opens and rewinds the file.
|
||||
If the
|
||||
.Fa stayopen
|
||||
flag is non-zero,
|
||||
the net data base will not be closed after each call to
|
||||
|
||||
@ -144,11 +144,13 @@ takes an Internet address and returns an
|
||||
.Tn ASCII
|
||||
string representing the address in
|
||||
.Ql .\&
|
||||
notation. The routine
|
||||
notation.
|
||||
The routine
|
||||
.Fn inet_makeaddr
|
||||
takes an Internet network number and a local
|
||||
network address and constructs an Internet address
|
||||
from it. The routines
|
||||
from it.
|
||||
The routines
|
||||
.Fn inet_netof
|
||||
and
|
||||
.Fn inet_lnaof
|
||||
@ -174,7 +176,8 @@ a
|
||||
.Pp
|
||||
When four parts are specified, each is interpreted
|
||||
as a byte of data and assigned, from left to right,
|
||||
to the four bytes of an Internet address. Note
|
||||
to the four bytes of an Internet address.
|
||||
Note
|
||||
that when an Internet address is viewed as a 32-bit
|
||||
integer quantity on the
|
||||
.Tn VAX
|
||||
@ -220,7 +223,8 @@ and
|
||||
.Fn inet_ntoa
|
||||
functions are semi-deprecated in favor of the
|
||||
.Xr addr2ascii 3
|
||||
family. However, since those functions are not yet widely implemented,
|
||||
family.
|
||||
However, since those functions are not yet widely implemented,
|
||||
portable programs cannot rely on their presence and will continue
|
||||
to use the
|
||||
.Xr inet 3
|
||||
|
||||
@ -66,7 +66,7 @@ complicated.
|
||||
The advanced API therefore defines a set
|
||||
of functions to help applications.
|
||||
These functions assume the
|
||||
formatting rules specified in Appendix B in RFC2460 i.e. that the
|
||||
formatting rules specified in Appendix B in RFC2460 i.e., that the
|
||||
largest field is placed last in the option.
|
||||
The function prototypes for
|
||||
these functions are all in the
|
||||
@ -76,7 +76,7 @@ header.
|
||||
.Ss inet6_opt_init
|
||||
.Fn inet6_opt_init
|
||||
returns the number of bytes needed for the empty
|
||||
extension header i.e. without any options.
|
||||
extension header i.e., without any options.
|
||||
If
|
||||
.Li extbuf
|
||||
is not NULL it also initializes the extension header to have the correct length
|
||||
@ -115,7 +115,7 @@ is the 8-bit option type.
|
||||
.Li len
|
||||
is the length of the option data
|
||||
.Po
|
||||
i.e. excluding the option type and option length fields.
|
||||
i.e., excluding the option type and option length fields.
|
||||
.Pc
|
||||
.Pp
|
||||
Once
|
||||
|
||||
@ -72,7 +72,8 @@
|
||||
.Sh DESCRIPTION
|
||||
RFC2292 IPv6 advanced API defines eight
|
||||
functions that the application calls to build and examine a Routing
|
||||
header. Four functions build a Routing header:
|
||||
header.
|
||||
Four functions build a Routing header:
|
||||
.Bl -hang
|
||||
.It Fn inet6_rthdr_space
|
||||
return #bytes required for ancillary data
|
||||
@ -108,7 +109,8 @@ containing the specified number of
|
||||
.Fa segments
|
||||
(addresses).
|
||||
For an IPv6 Type 0 Routing header, the number
|
||||
of segments must be between 1 and 23, inclusive. The return value
|
||||
of segments must be between 1 and 23, inclusive.
|
||||
The return value
|
||||
includes the size of the cmsghdr structure that precedes the Routing
|
||||
header, and any required padding.
|
||||
.Pp
|
||||
|
||||
@ -191,7 +191,8 @@ This option is enabled by default.
|
||||
.It Dv RES_NOALIASES
|
||||
This option turns off the user level aliasing feature controlled by the
|
||||
.Dq Ev HOSTALIASES
|
||||
environment variable. Network daemons should set this option.
|
||||
environment variable.
|
||||
Network daemons should set this option.
|
||||
.It Dv RES_USE_INET6
|
||||
Enables support for IPv6-only applications.
|
||||
This causes IPv4 addresses to be returned as an IPv4 mapped address.
|
||||
@ -227,7 +228,8 @@ it can be overridden by the environment variable
|
||||
This environment variable may contain several blank-separated
|
||||
tokens if you wish to override the
|
||||
.Em "search list"
|
||||
on a per-process basis. This is similar to the
|
||||
on a per-process basis.
|
||||
This is similar to the
|
||||
.Ic search
|
||||
command in the configuration file.
|
||||
Another environment variable
|
||||
@ -238,7 +240,8 @@ set by changing fields in the
|
||||
.Va _res
|
||||
structure or are inherited from the configuration file's
|
||||
.Ic options
|
||||
command. The syntax of the
|
||||
command.
|
||||
The syntax of the
|
||||
.Dq Ev RES_OPTIONS
|
||||
environment variable is explained in
|
||||
.Xr resolver 5 .
|
||||
|
||||
@ -124,9 +124,11 @@ The file system is read-only.
|
||||
.Xr acl_set 3 ,
|
||||
.Xr posix1e 3
|
||||
.Sh STANDARDS
|
||||
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
|
||||
POSIX.1e is described in IEEE POSIX.1e draft 17.
|
||||
Discussion
|
||||
of the draft continues on the cross-platform POSIX.1e implementation
|
||||
mailing list. To join this list, see the
|
||||
mailing list.
|
||||
To join this list, see the
|
||||
.Fx
|
||||
POSIX.1e implementation
|
||||
page for more information.
|
||||
|
||||
@ -56,7 +56,8 @@ function fails if:
|
||||
.It Bq Er EINVAL
|
||||
Argument
|
||||
.Fa acl
|
||||
does not point to a valid ACL. Argument
|
||||
does not point to a valid ACL.
|
||||
Argument
|
||||
.Fa entry_d
|
||||
is not a valid descriptor for an ACL entry in
|
||||
.Fa acl .
|
||||
|
||||
@ -54,7 +54,8 @@ function fails if:
|
||||
.It Bq Er EINVAL
|
||||
Argument
|
||||
.Fa permset_d
|
||||
is not a valid descriptor for a permission set. Argument
|
||||
is not a valid descriptor for a permission set.
|
||||
Argument
|
||||
.Fa perm
|
||||
does not contain a valid
|
||||
.Vt acl_perm_t
|
||||
|
||||
@ -46,7 +46,8 @@ The
|
||||
function returns a pointer to a copy of the ACL pointed to by the argument
|
||||
.Va acl .
|
||||
.Pp
|
||||
This function may cause memory to be allocated. The caller should free any
|
||||
This function may cause memory to be allocated.
|
||||
The caller should free any
|
||||
releasable memory, when the new ACL is no longer required, by calling
|
||||
.Xr acl_free 3
|
||||
with the
|
||||
@ -62,7 +63,8 @@ support for POSIX.1e interfaces and features is still under
|
||||
development at this time.
|
||||
.Sh RETURN VALUES
|
||||
Upon successful completion, this function shall return a pointer to the
|
||||
duplicate ACL. Otherwise, a value of
|
||||
duplicate ACL.
|
||||
Otherwise, a value of
|
||||
.Va (acl_t)NULL
|
||||
shall be returned, and
|
||||
.Va errno
|
||||
@ -92,9 +94,11 @@ system-imposed memory management constraints.
|
||||
.Xr acl_get 3 ,
|
||||
.Xr posix1e 3
|
||||
.Sh STANDARDS
|
||||
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
|
||||
POSIX.1e is described in IEEE POSIX.1e draft 17.
|
||||
Discussion
|
||||
of the draft continues on the cross-platform POSIX.1e implementation
|
||||
mailing list. To join this list, see the
|
||||
mailing list.
|
||||
To join this list, see the
|
||||
.Fx
|
||||
POSIX.1e implementation
|
||||
page for more information.
|
||||
|
||||
@ -73,9 +73,11 @@ argument is invalid.
|
||||
.Xr acl_init 3 ,
|
||||
.Xr posix1e 3
|
||||
.Sh STANDARDS
|
||||
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
|
||||
POSIX.1e is described in IEEE POSIX.1e draft 17.
|
||||
Discussion
|
||||
of the draft continues on the cross-platform POSIX.1e implementation
|
||||
mailing list. To join this list, see the
|
||||
mailing list.
|
||||
To join this list, see the
|
||||
.Fx
|
||||
POSIX.1e implementation
|
||||
page for more information.
|
||||
|
||||
@ -48,7 +48,8 @@ function converts the text form of an ACL referred to by
|
||||
into the internal working structure for ACLs, appropriate for applying to
|
||||
files or manipulating.
|
||||
.Pp
|
||||
This function may cause memory to be allocated. The caller should free any
|
||||
This function may cause memory to be allocated.
|
||||
The caller should free any
|
||||
releasable memory, when the new ACL is no longer required, by calling
|
||||
.Xr acl_free 3
|
||||
with the
|
||||
@ -60,7 +61,8 @@ support for POSIX.1e interfaces and features is still under
|
||||
development at this time.
|
||||
.Sh RETURN VALUES
|
||||
Upon successful completion, the function shall return a pointer to the
|
||||
internal representation of the ACL in working storage. Otherwise, a value
|
||||
internal representation of the ACL in working storage.
|
||||
Otherwise, a value
|
||||
of
|
||||
.Va (acl_t)NULL
|
||||
shall be returned, and
|
||||
@ -90,9 +92,11 @@ hardware or system-imposed memory management constraints.
|
||||
.Xr acl_to_text 3 ,
|
||||
.Xr posix1e 3
|
||||
.Sh STANDARDS
|
||||
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
|
||||
POSIX.1e is described in IEEE POSIX.1e draft 17.
|
||||
Discussion
|
||||
of the draft continues on the cross-platform POSIX.1e implementation
|
||||
mailing list. To join this list, see the
|
||||
mailing list.
|
||||
To join this list, see the
|
||||
.Fx
|
||||
POSIX.1e implementation
|
||||
page for more information.
|
||||
@ -112,7 +116,8 @@ rely on the
|
||||
.Xr getpwent 3
|
||||
library calls to manage username and uid mapping, as well as the
|
||||
.Xr getgrent 3
|
||||
library calls to manage groupname and gid mapping. These calls are not
|
||||
library calls to manage groupname and gid mapping.
|
||||
These calls are not
|
||||
thread safe, and so transitively, neither are
|
||||
.Fn acl_from_text
|
||||
and
|
||||
|
||||
@ -78,7 +78,8 @@ is a non-portable variation on
|
||||
which does not follow a symlink if the target of the call is a
|
||||
symlink.
|
||||
.Pp
|
||||
These functions may cause memory to be allocated. The caller should free
|
||||
These functions may cause memory to be allocated.
|
||||
The caller should free
|
||||
any releasable memory, when the new ACL is no longer required, by calling
|
||||
.Xr acl_free 3
|
||||
with the
|
||||
@ -96,7 +97,8 @@ support for POSIX.1e interfaces and features is still under
|
||||
development at this time.
|
||||
.Sh RETURN VALUES
|
||||
Upon successful completion, the function shall return a pointer to the ACL
|
||||
that was retrieved. Otherwise, a value of
|
||||
that was retrieved.
|
||||
Otherwise, a value of
|
||||
.Va (acl_t)NULL
|
||||
shall be returned, and
|
||||
.Va errno
|
||||
@ -138,9 +140,11 @@ The file system does not support ACL retrieval.
|
||||
.Xr acl_set 3 ,
|
||||
.Xr posix1e 3
|
||||
.Sh STANDARDS
|
||||
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
|
||||
POSIX.1e is described in IEEE POSIX.1e draft 17.
|
||||
Discussion
|
||||
of the draft continues on the cross-platform POSIX.1e implementation
|
||||
mailing list. To join this list, see the
|
||||
mailing list.
|
||||
To join this list, see the
|
||||
.Fx
|
||||
POSIX.1e implementation
|
||||
page for more information.
|
||||
|
||||
@ -82,7 +82,8 @@ If the
|
||||
function successfully obtains an ACL entry, a value of 1 is returned.
|
||||
If the ACL has no ACL entries, the
|
||||
.Fn acl_get_entry
|
||||
returns a value of 0. If the value of
|
||||
returns a value of 0.
|
||||
If the value of
|
||||
.Fa entry_id
|
||||
is
|
||||
.Dv ACL_NEXT_ENTRY
|
||||
@ -93,7 +94,8 @@ a value of 0 will be returned until a successful call with
|
||||
.Fa entry_id
|
||||
of
|
||||
.Dv ACL_FIRST_ENTRY
|
||||
is made. Otherwise, a value of -1 will be returned and
|
||||
is made.
|
||||
Otherwise, a value of -1 will be returned and
|
||||
the global variable
|
||||
.Va errno
|
||||
will be set to indicate the error.
|
||||
@ -105,7 +107,8 @@ fails if:
|
||||
.It Bq Er EINVAL
|
||||
Argument
|
||||
.Fa acl
|
||||
does not point to a valid ACL. Argument
|
||||
does not point to a valid ACL.
|
||||
Argument
|
||||
.Fa entry_id
|
||||
is neither
|
||||
.Dv ACL_FIRST_ENTRY
|
||||
|
||||
@ -78,7 +78,8 @@ will return a value of
|
||||
.Vt ( void * ) Ns Dv NULL
|
||||
and the function will fail.
|
||||
.Pp
|
||||
This function may cause memory to be allocated. The caller should
|
||||
This function may cause memory to be allocated.
|
||||
The caller should
|
||||
free any releasable memory, when the new qualifier is no longer
|
||||
required, by calling
|
||||
.Fn acl_free
|
||||
@ -102,7 +103,8 @@ fails if:
|
||||
.It Bq Er EINVAL
|
||||
Argument
|
||||
.Fa entry_d
|
||||
does not point to a valid descriptor for an ACL entry. The
|
||||
does not point to a valid descriptor for an ACL entry.
|
||||
The
|
||||
value of the tag type in the ACL entry referenced by argument
|
||||
.Fa entry_d
|
||||
is not
|
||||
|
||||
@ -46,13 +46,16 @@ The
|
||||
function allocates and initializes the working storage for an ACL of at
|
||||
least
|
||||
.Va count
|
||||
ACL entries. A pointer to the working storage is returned. The working
|
||||
ACL entries.
|
||||
A pointer to the working storage is returned.
|
||||
The working
|
||||
storage allocated to contain the ACL is freed by a call to
|
||||
.Xr acl_free 3 .
|
||||
When the area is first allocated, it shall contain an ACL that contains
|
||||
no ACL entries.
|
||||
.Pp
|
||||
This function may cause memory to be allocated. The caller should free any
|
||||
This function may cause memory to be allocated.
|
||||
The caller should free any
|
||||
releasable memory, when the new ACL is no longer required, by calling
|
||||
.Xr acl_free 3
|
||||
with the
|
||||
@ -64,7 +67,8 @@ support for POSIX.1e interfaces and features is still under
|
||||
development at this time.
|
||||
.Sh RETURN VALUES
|
||||
Upon successful completion, this function shall return a pointer to the
|
||||
working storage. Otherwise, a value of
|
||||
working storage.
|
||||
Otherwise, a value of
|
||||
.Va (acl_t)NULL
|
||||
shall be returned, and
|
||||
.Va errno
|
||||
@ -91,9 +95,11 @@ system-imposed memory management constraints.
|
||||
.Xr acl_free 3 ,
|
||||
.Xr posix1e 3
|
||||
.Sh STANDARDS
|
||||
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
|
||||
POSIX.1e is described in IEEE POSIX.1e draft 17.
|
||||
Discussion
|
||||
of the draft continues on the cross-platform POSIX.1e implementation
|
||||
mailing list. To join this list, see the
|
||||
mailing list.
|
||||
To join this list, see the
|
||||
.Fx
|
||||
POSIX.1e implementation
|
||||
page for more information.
|
||||
|
||||
@ -126,9 +126,11 @@ read-only.
|
||||
.Xr acl_valid 3 ,
|
||||
.Xr posix1e 3
|
||||
.Sh STANDARDS
|
||||
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
|
||||
POSIX.1e is described in IEEE POSIX.1e draft 17.
|
||||
Discussion
|
||||
of the draft continues on the cross-platform POSIX.1e implementation
|
||||
mailing list. To join this list, see the
|
||||
mailing list.
|
||||
To join this list, see the
|
||||
.Fx
|
||||
POSIX.1e implementation
|
||||
page for more information.
|
||||
|
||||
@ -56,7 +56,8 @@ function fails if:
|
||||
.It Bq Er EINVAL
|
||||
Argument
|
||||
.Fa entry_d
|
||||
is not a valid descriptor for an ACL entry. The tag type of the
|
||||
is not a valid descriptor for an ACL entry.
|
||||
The tag type of the
|
||||
ACL entry
|
||||
.Fa entry_d
|
||||
is not
|
||||
|
||||
@ -56,7 +56,8 @@ function fails if:
|
||||
.It Bq Er EINVAL
|
||||
Argument
|
||||
.Fa entry_d
|
||||
is not a valid descriptor for an ACL entry. Argument
|
||||
is not a valid descriptor for an ACL entry.
|
||||
Argument
|
||||
.Fa tag_type
|
||||
is not a valid ACL tag type.
|
||||
.El
|
||||
|
||||
@ -45,7 +45,8 @@ The
|
||||
.Fn acl_to_text
|
||||
function translates the ACL pointed to by argument
|
||||
.Va acl
|
||||
into a NULL terminated character string. If the pointer
|
||||
into a NULL terminated character string.
|
||||
If the pointer
|
||||
.Va len_p
|
||||
is not NULL, then the function shall return the length of the string (not
|
||||
including the NULL terminator) in the location pointed to by
|
||||
@ -55,7 +56,8 @@ The format of the text string returned by
|
||||
shall be the POSIX.1e long ACL form.
|
||||
.Pp
|
||||
This function allocates any memory necessary to contain the string and
|
||||
returns a pointer to the string. The caller should free any releasable
|
||||
returns a pointer to the string.
|
||||
The caller should free any releasable
|
||||
memory, when the new string is no longer required, by calling
|
||||
.Xr acl_free 3
|
||||
with the
|
||||
@ -67,7 +69,8 @@ support for POSIX.1e interfaces and features is still under
|
||||
development at this time.
|
||||
.Sh RETURN VALUES
|
||||
Upon successful completion, the function shall return a pointer to the
|
||||
long text form of an ACL. Otherwise, a value of
|
||||
long text form of an ACL.
|
||||
Otherwise, a value of
|
||||
.Va (char*)NULL
|
||||
shall be returned and
|
||||
.Va errno
|
||||
@ -100,9 +103,11 @@ by the hardware or software-imposed memory management constraints.
|
||||
.Xr acl_from_text 3 ,
|
||||
.Xr posix1e 3
|
||||
.Sh STANDARDS
|
||||
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
|
||||
POSIX.1e is described in IEEE POSIX.1e draft 17.
|
||||
Discussion
|
||||
of the draft continues on the cross-platform POSIX.1e implementation
|
||||
mailing list. To join this list, see the
|
||||
mailing list.
|
||||
To join this list, see the
|
||||
.Fx
|
||||
POSIX.1e implementation
|
||||
page for more information.
|
||||
@ -122,7 +127,8 @@ rely on the
|
||||
.Xr getpwent 3
|
||||
library calls to manage username and uid mapping, as well as the
|
||||
.Xr getgrent 3
|
||||
library calls to manage groupname and gid mapping. These calls are not
|
||||
library calls to manage groupname and gid mapping.
|
||||
These calls are not
|
||||
thread safe, and so transitively, neither are
|
||||
.Fn acl_from_text
|
||||
and
|
||||
|
||||
@ -52,10 +52,12 @@
|
||||
.Sh DESCRIPTION
|
||||
These functions check that the ACL referred to by the argument
|
||||
.Va acl
|
||||
is valid. The POSIX.1e routine,
|
||||
is valid.
|
||||
The POSIX.1e routine,
|
||||
.Fn acl_valid ,
|
||||
checks this validity only with POSIX.1e ACL semantics, and irrespective
|
||||
of the context in which the ACL is to be used. The non-portable forms,
|
||||
of the context in which the ACL is to be used.
|
||||
The non-portable forms,
|
||||
.Fn acl_valid_fd_np ,
|
||||
.Fn acl_valid_file_np ,
|
||||
and
|
||||
@ -140,9 +142,11 @@ The file system does not support ACL retrieval.
|
||||
.Xr acl_set 3 ,
|
||||
.Xr posix1e 3
|
||||
.Sh STANDARDS
|
||||
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion
|
||||
POSIX.1e is described in IEEE POSIX.1e draft 17.
|
||||
Discussion
|
||||
of the draft continues on the cross-platform POSIX.1e implementation
|
||||
mailing list. To join this list, see the
|
||||
mailing list.
|
||||
To join this list, see the
|
||||
.Fx
|
||||
POSIX.1e implementation
|
||||
page for more information.
|
||||
|
||||
@ -232,7 +232,7 @@ sequence of characters of that collating element.
|
||||
The sequence is a single element of the bracket expression's list.
|
||||
A bracket expression containing a multi-character collating element
|
||||
can thus match more than one character,
|
||||
e.g. if the collating sequence includes a
|
||||
e.g.\& if the collating sequence includes a
|
||||
.Ql ch
|
||||
collating element,
|
||||
then the RE
|
||||
|
||||
@ -564,7 +564,7 @@ or
|
||||
.Ql |\&
|
||||
cannot appear first or last in a (sub)expression or after another
|
||||
.Ql |\& ,
|
||||
i.e. an operand of
|
||||
i.e., an operand of
|
||||
.Ql |\&
|
||||
cannot be an empty subexpression.
|
||||
An empty parenthesized subexpression,
|
||||
@ -651,7 +651,7 @@ empty (sub)expression
|
||||
.It Dv REG_ASSERT
|
||||
can't happen - you found a bug
|
||||
.It Dv REG_INVARG
|
||||
invalid argument, e.g. negative-length string
|
||||
invalid argument, e.g.\& negative-length string
|
||||
.El
|
||||
.Sh HISTORY
|
||||
Originally written by
|
||||
|
||||
@ -64,7 +64,8 @@ reads the next line of the file, opening the file if necessary.
|
||||
The
|
||||
.Fn setrpcent
|
||||
function
|
||||
opens and rewinds the file. If the
|
||||
opens and rewinds the file.
|
||||
If the
|
||||
.Fa stayopen
|
||||
flag is non-zero,
|
||||
the net data base will not be closed after each call to
|
||||
|
||||
@ -26,7 +26,8 @@ and using protocol
|
||||
.Fa proto .
|
||||
It returns 0 if it cannot contact the portmapper, or if
|
||||
.Fa prognum
|
||||
is not registered. If
|
||||
is not registered.
|
||||
If
|
||||
.Fa prognum
|
||||
is registered but not with version
|
||||
.Fa versnum ,
|
||||
|
||||
@ -39,9 +39,11 @@
|
||||
.Sh DESCRIPTION
|
||||
These routines are part of the
|
||||
.Tn RPC
|
||||
library. They implement
|
||||
library.
|
||||
They implement
|
||||
.Tn DES
|
||||
Authentication. See
|
||||
Authentication.
|
||||
See
|
||||
.Xr rpc 3
|
||||
for further details about
|
||||
.Tn RPC .
|
||||
@ -81,14 +83,16 @@ derived from the utility routine
|
||||
but could also represent a user name using
|
||||
.Fn user2netname .
|
||||
The second field is window on the validity of
|
||||
the client credential, given in seconds. A small
|
||||
the client credential, given in seconds.
|
||||
A small
|
||||
window is more secure than a large one, but choosing
|
||||
too small of a window will increase the frequency of
|
||||
resynchronizations because of clock drift.
|
||||
The third
|
||||
argument
|
||||
.Fa addr
|
||||
is optional. If it is
|
||||
is optional.
|
||||
If it is
|
||||
.Dv NULL ,
|
||||
then the authentication system will assume
|
||||
that the local clock is always in sync with the server's
|
||||
@ -104,7 +108,8 @@ address of the
|
||||
server itself.
|
||||
The final argument
|
||||
.Fa ckey
|
||||
is also optional. If it is
|
||||
is also optional.
|
||||
If it is
|
||||
.Dv NULL ,
|
||||
then the authentication system will
|
||||
generate a random
|
||||
@ -184,7 +189,8 @@ takes a server netname and a
|
||||
.Tn DES
|
||||
key, and decrypts the key by
|
||||
using the public key of the server and the secret key
|
||||
associated with the effective uid of the calling process. It
|
||||
associated with the effective uid of the calling process.
|
||||
It
|
||||
is the inverse of
|
||||
.Fn key_encryptsession .
|
||||
.Pp
|
||||
@ -195,7 +201,8 @@ is a keyserver interface routine.
|
||||
It
|
||||
takes a server netname and a des key, and encrypts
|
||||
it using the public key of the server and the secret key
|
||||
associated with the effective uid of the calling process. It
|
||||
associated with the effective uid of the calling process.
|
||||
It
|
||||
is the inverse of
|
||||
.Fn key_decryptsession .
|
||||
.Pp
|
||||
@ -230,7 +237,8 @@ Returns
|
||||
.Dv TRUE
|
||||
if it succeeds and
|
||||
.Dv FALSE
|
||||
if it fails. Inverse of
|
||||
if it fails.
|
||||
Inverse of
|
||||
.Fn host2netname .
|
||||
.Pp
|
||||
The
|
||||
|
||||
@ -92,15 +92,19 @@ object is indeterminate (garbage) after a file is closed.
|
||||
.Pp
|
||||
A file may be subsequently reopened, by the same or another program
|
||||
execution, and its contents reclaimed or modified (if it can be repositioned
|
||||
at the start). If the main function returns to its original caller, or
|
||||
at the start).
|
||||
If the main function returns to its original caller, or
|
||||
the
|
||||
.Xr exit 3
|
||||
function is called, all open files are closed (hence all output
|
||||
streams are flushed) before program termination. Other methods
|
||||
streams are flushed) before program termination.
|
||||
Other methods
|
||||
of program termination may not close files properly and hence
|
||||
buffered output may be lost. In particular,
|
||||
buffered output may be lost.
|
||||
In particular,
|
||||
.Xr _exit 2
|
||||
does not flush stdio files. Neither does an exit due to a signal.
|
||||
does not flush stdio files.
|
||||
Neither does an exit due to a signal.
|
||||
Buffers are flushed by
|
||||
.Xr abort 3
|
||||
as required by POSIX, although previous implementations did not.
|
||||
|
||||
@ -144,13 +144,15 @@ assigning a differently sized
|
||||
.Fa value
|
||||
to the same
|
||||
.Fa name
|
||||
will result in a memory leak. The
|
||||
will result in a memory leak.
|
||||
The
|
||||
.Fx
|
||||
semantics for these functions
|
||||
(namely, that the contents of
|
||||
.Fa value
|
||||
are copied and that old values remain accessible indefinitely) make this
|
||||
bug unavoidable. Future versions may eliminate one or both of these
|
||||
bug unavoidable.
|
||||
Future versions may eliminate one or both of these
|
||||
semantic guarantees in order to fix the bug.
|
||||
.Sh HISTORY
|
||||
The functions
|
||||
|
||||
@ -149,11 +149,13 @@ The
|
||||
.Fn qsort
|
||||
and
|
||||
.Fn qsort_r
|
||||
functions are an implementation of C.A.R. Hoare's
|
||||
functions are an implementation of C.A.R.
|
||||
Hoare's
|
||||
.Dq quicksort
|
||||
algorithm,
|
||||
a variant of partition-exchange sorting; in particular, see D.E. Knuth's
|
||||
Algorithm Q.
|
||||
a variant of partition-exchange sorting; in particular, see
|
||||
.An D.E. Knuth Ns 's
|
||||
.%T "Algorithm Q" .
|
||||
.Sy Quicksort
|
||||
takes O N lg N average time.
|
||||
This implementation uses median selection to avoid its
|
||||
@ -161,10 +163,13 @@ O N**2 worst-case behavior.
|
||||
.Pp
|
||||
The
|
||||
.Fn heapsort
|
||||
function is an implementation of J.W.J. William's
|
||||
function is an implementation of
|
||||
.An "J.W.J. William" Ns 's
|
||||
.Dq heapsort
|
||||
algorithm,
|
||||
a variant of selection sorting; in particular, see D.E. Knuth's Algorithm H.
|
||||
a variant of selection sorting; in particular, see
|
||||
.An "D.E. Knuth" Ns 's
|
||||
.%T "Algorithm H" .
|
||||
.Sy Heapsort
|
||||
takes O N lg N worst-case time.
|
||||
Its
|
||||
|
||||
@ -105,7 +105,10 @@ The
|
||||
function is not stable, but uses no additional memory.
|
||||
.Pp
|
||||
These functions are variants of most-significant-byte radix sorting; in
|
||||
particular, see D.E. Knuth's Algorithm R and section 5.2.5, exercise 10.
|
||||
particular, see
|
||||
.An "D.E. Knuth" Ns 's
|
||||
.%T "Algorithm R"
|
||||
and section 5.2.5, exercise 10.
|
||||
They take linear time relative to the number of bytes in the strings.
|
||||
.Sh RETURN VALUES
|
||||
.Rv -std radixsort
|
||||
|
||||
@ -81,9 +81,11 @@ functions.
|
||||
The difference is that
|
||||
.Xr rand 3
|
||||
produces a much less random sequence \(em in fact, the low dozen bits
|
||||
generated by rand go through a cyclic pattern. All the bits generated by
|
||||
generated by rand go through a cyclic pattern.
|
||||
All the bits generated by
|
||||
.Fn random
|
||||
are usable. For example,
|
||||
are usable.
|
||||
For example,
|
||||
.Sq Li random()&01
|
||||
will produce a random binary
|
||||
value.
|
||||
@ -115,13 +117,15 @@ a fixed seed.
|
||||
The
|
||||
.Fn initstate
|
||||
routine allows a state array, passed in as an argument, to be initialized
|
||||
for future use. The size of the state array (in bytes) is used by
|
||||
for future use.
|
||||
The size of the state array (in bytes) is used by
|
||||
.Fn initstate
|
||||
to decide how sophisticated a random number generator it should use \(em the
|
||||
more state, the better the random numbers will be.
|
||||
(Current "optimal" values for the amount of state information are
|
||||
8, 32, 64, 128, and 256 bytes; other amounts will be rounded down to
|
||||
the nearest known amount. Using less than 8 bytes will cause an error.)
|
||||
the nearest known amount.
|
||||
Using less than 8 bytes will cause an error.)
|
||||
The seed for the initialization (which specifies a starting point for
|
||||
the random number sequence, and provides for restarting at the same
|
||||
point) is also an argument.
|
||||
|
||||
@ -51,7 +51,8 @@ The
|
||||
and
|
||||
.Fn twalk
|
||||
functions manage binary search trees based on algorithms T and D
|
||||
from Knuth (6.2.2). The comparison function passed in by
|
||||
from Knuth (6.2.2).
|
||||
The comparison function passed in by
|
||||
the user has the same style of return values as
|
||||
.Xr strcmp 3 .
|
||||
.Pp
|
||||
@ -72,7 +73,8 @@ is identical to
|
||||
.Fn tfind
|
||||
except that if no match is found,
|
||||
.Fa key
|
||||
is inserted into the tree and a pointer to it is returned. If
|
||||
is inserted into the tree and a pointer to it is returned.
|
||||
If
|
||||
.Fa rootp
|
||||
points to a NULL value a new binary search tree is created.
|
||||
.Pp
|
||||
|
||||
@ -354,7 +354,8 @@ function will modify the same object.
|
||||
The C Standard provides no mechanism for a program to modify its current
|
||||
local timezone setting, and the
|
||||
.Tn POSIX Ns No \&-standard
|
||||
method is not reentrant. (However, thread-safe implementations are provided
|
||||
method is not reentrant.
|
||||
(However, thread-safe implementations are provided
|
||||
in the
|
||||
.Tn POSIX
|
||||
threaded environment.)
|
||||
|
||||
@ -184,7 +184,8 @@ is replaced by the weekday (Monday as the first day of the week)
|
||||
as a decimal number (1-7).
|
||||
.It Cm \&%V
|
||||
is replaced by the week number of the year (Monday as the first day of
|
||||
the week) as a decimal number (01-53). If the week containing January
|
||||
the week) as a decimal number (01-53).
|
||||
If the week containing January
|
||||
1 has four or more days in the new year, then it is week 1; otherwise
|
||||
it is the last week of the previous year, and the next week is week 1.
|
||||
.It Cm %v
|
||||
|
||||
@ -161,7 +161,8 @@ The
|
||||
format specifier only accepts time zone abbreviations of the local time zone,
|
||||
or the value "GMT".
|
||||
This limitation is because of ambiguity due to of the over loading of time
|
||||
zone abbreviations. One such example is
|
||||
zone abbreviations.
|
||||
One such example is
|
||||
.Fa EST
|
||||
which is both Eastern Standard Time and Eastern Australia Summer Time.
|
||||
.Pp
|
||||
|
||||
@ -47,7 +47,8 @@ The
|
||||
.Fn strlcpy
|
||||
and
|
||||
.Fn strlcat
|
||||
functions copy and concatenate strings respectively. They are designed
|
||||
functions copy and concatenate strings respectively.
|
||||
They are designed
|
||||
to be safer, more consistent, and less error prone replacements for
|
||||
.Xr strncpy 3
|
||||
and
|
||||
@ -108,7 +109,8 @@ The
|
||||
and
|
||||
.Fn strlcat
|
||||
functions return the total length of the string they tried to
|
||||
create. For
|
||||
create.
|
||||
For
|
||||
.Fn strlcpy
|
||||
that means the length of
|
||||
.Fa src .
|
||||
|
||||
@ -115,7 +115,7 @@ While the
|
||||
.Fn strtok
|
||||
function should be preferred for portability reasons (it conforms to
|
||||
.St -isoC )
|
||||
it is unable to handle empty fields, i.e. detect fields delimited by
|
||||
it is unable to handle empty fields, i.e., detect fields delimited by
|
||||
two adjacent delimiter characters, or to be used for more than a single
|
||||
string at a time.
|
||||
The
|
||||
|
||||
@ -76,7 +76,8 @@ connections are present on the queue,
|
||||
returns an error as described below.
|
||||
The accepted socket
|
||||
may not be used
|
||||
to accept more connections. The original socket
|
||||
to accept more connections.
|
||||
The original socket
|
||||
.Fa s
|
||||
remains open.
|
||||
.Pp
|
||||
@ -130,7 +131,8 @@ For some applications, performance may be enhanced by using an
|
||||
.Xr accept_filter 9
|
||||
to pre-process incoming connections.
|
||||
.Sh RETURN VALUES
|
||||
The call returns \-1 on error. If it succeeds, it returns a non-negative
|
||||
The call returns \-1 on error.
|
||||
If it succeeds, it returns a non-negative
|
||||
integer that is a descriptor for the accepted socket.
|
||||
.Sh ERRORS
|
||||
The
|
||||
|
||||
@ -45,9 +45,11 @@ associated with the structure pointed to by
|
||||
.Sh RETURN VALUES
|
||||
If the asynchronous I/O request has completed successfully,
|
||||
.Fn aio_error
|
||||
returns 0. If the request has not yet completed,
|
||||
returns 0.
|
||||
If the request has not yet completed,
|
||||
.Er EINPROGRESS
|
||||
is returned. If the request has completed unsuccessfully the error
|
||||
is returned.
|
||||
If the request has completed unsuccessfully the error
|
||||
status is returned as described in
|
||||
.Xr read 2 ,
|
||||
.Xr write 2 ,
|
||||
|
||||
@ -85,7 +85,8 @@ The Asynchronous I/O Control Block structure pointed to by
|
||||
and the buffer that the
|
||||
.Fa iocb->aio_buf
|
||||
member of that structure references must remain valid until the
|
||||
operation has completed. For this reason, use of auto (stack) variables
|
||||
operation has completed.
|
||||
For this reason, use of auto (stack) variables
|
||||
for these objects is discouraged.
|
||||
.Pp
|
||||
The asynchronous I/O control buffer
|
||||
@ -122,7 +123,8 @@ system call is not supported.
|
||||
.Pp
|
||||
The following conditions may be synchronously detected when the
|
||||
.Fn aio_read
|
||||
system call is made, or asynchronously, at any time thereafter. If they
|
||||
system call is made, or asynchronously, at any time thereafter.
|
||||
If they
|
||||
are detected at call time,
|
||||
.Fn aio_read
|
||||
returns -1 and sets
|
||||
|
||||
@ -50,7 +50,8 @@ The
|
||||
argument
|
||||
is an array of
|
||||
.Fa niocb
|
||||
pointers to asynchronous I/O requests. Array members containing
|
||||
pointers to asynchronous I/O requests.
|
||||
Array members containing
|
||||
NULL will be silently ignored.
|
||||
.Pp
|
||||
If
|
||||
@ -58,7 +59,8 @@ If
|
||||
is a non-nil pointer, it specifies a maximum interval to suspend.
|
||||
If
|
||||
.Fa timeout
|
||||
is a nil pointer, the suspend blocks indefinitely. To effect a
|
||||
is a nil pointer, the suspend blocks indefinitely.
|
||||
To effect a
|
||||
poll, the
|
||||
.Fa timeout
|
||||
should point to a zero-value timespec structure.
|
||||
@ -66,7 +68,8 @@ should point to a zero-value timespec structure.
|
||||
If one or more of the specified asynchronous I/O requests have
|
||||
completed,
|
||||
.Fn aio_suspend
|
||||
returns 0. Otherwise it returns -1 and sets
|
||||
returns 0.
|
||||
Otherwise it returns -1 and sets
|
||||
.Va errno
|
||||
to indicate the error, as enumerated below.
|
||||
.Sh ERRORS
|
||||
|
||||
@ -47,7 +47,8 @@ to the descriptor
|
||||
.Fa iocb->aio_fildes .
|
||||
The call returns immediately after the write request has been enqueued
|
||||
to the descriptor; the write may or may not have completed at the time
|
||||
the call returns. If the request could not be enqueued, generally due
|
||||
the call returns.
|
||||
If the request could not be enqueued, generally due
|
||||
to invalid arguments, the call returns without having enqueued the
|
||||
request.
|
||||
.Pp
|
||||
@ -57,7 +58,8 @@ is set for
|
||||
.Fa iocb->aio_fildes ,
|
||||
.Fn aio_write
|
||||
operations append to the file in the same order as the calls were
|
||||
made. If
|
||||
made.
|
||||
If
|
||||
.Dv O_APPEND
|
||||
is not set for the file descriptor, the write operation will occur at
|
||||
the absolute position from the beginning of the file plus
|
||||
@ -89,7 +91,8 @@ The Asynchronous I/O Control Block structure pointed to by
|
||||
and the buffer that the
|
||||
.Fa iocb->aio_buf
|
||||
member of that structure references must remain valid until the
|
||||
operation has completed. For this reason, use of auto (stack) variables
|
||||
operation has completed.
|
||||
For this reason, use of auto (stack) variables
|
||||
for these objects is discouraged.
|
||||
.Pp
|
||||
The asynchronous I/O control buffer
|
||||
@ -124,7 +127,8 @@ system call is not supported.
|
||||
.Pp
|
||||
The following conditions may be synchronously detected when the
|
||||
.Fn aio_write
|
||||
system call is made, or asynchronously, at any time thereafter. If they
|
||||
system call is made, or asynchronously, at any time thereafter.
|
||||
If they
|
||||
are detected at call time,
|
||||
.Fn aio_write
|
||||
returns -1 and sets
|
||||
|
||||
@ -132,7 +132,8 @@ then the owner of any new files and sub-directories
|
||||
created within this directory are set
|
||||
to be the same as the owner of that directory.
|
||||
If this function is enabled, new directories will inherit
|
||||
the bit from their parents. Execute bits are removed from
|
||||
the bit from their parents.
|
||||
Execute bits are removed from
|
||||
the file, and it will not be given to root.
|
||||
This behavior does not change the
|
||||
requirements for the user to be allowed to write the file, but only the eventual
|
||||
|
||||
@ -97,7 +97,8 @@ Any other value for
|
||||
.Ql kern.chroot_allow_open_directories
|
||||
will bypass the check for open directories
|
||||
.Pp
|
||||
Upon successful completion, a value of 0 is returned. Otherwise,
|
||||
Upon successful completion, a value of 0 is returned.
|
||||
Otherwise,
|
||||
a value of -1 is returned and
|
||||
.Va errno
|
||||
is set to indicate an error.
|
||||
|
||||
@ -95,7 +95,8 @@ system call even when the system is secure.
|
||||
.Pp
|
||||
The resolution (granularity) of a clock is returned by the
|
||||
.Fn clock_getres
|
||||
system call. This value is placed in a (non-NULL)
|
||||
system call.
|
||||
This value is placed in a (non-NULL)
|
||||
.Fa *tp .
|
||||
.Sh RETURN VALUES
|
||||
.Rv -std
|
||||
|
||||
@ -83,7 +83,8 @@ all descriptors for the new child process reference the same
|
||||
objects as they did in the parent before the fork.
|
||||
If a new process is then to be run using
|
||||
.Xr execve 2 ,
|
||||
the process would normally inherit these descriptors. Most
|
||||
the process would normally inherit these descriptors.
|
||||
Most
|
||||
of the descriptors can be rearranged with
|
||||
.Xr dup2 2
|
||||
or deleted with
|
||||
|
||||
@ -59,7 +59,8 @@ the calling process
|
||||
The argument
|
||||
.Fa oldd
|
||||
is a small non-negative integer index in
|
||||
the per-process descriptor table. The value must be less
|
||||
the per-process descriptor table.
|
||||
The value must be less
|
||||
than the size of the table, which is returned by
|
||||
.Xr getdtablesize 2 .
|
||||
The new descriptor returned by the call
|
||||
@ -96,7 +97,8 @@ In
|
||||
.Fn dup2 ,
|
||||
the value of the new descriptor
|
||||
.Fa newd
|
||||
is specified. If this descriptor is already in use and
|
||||
is specified.
|
||||
If this descriptor is already in use and
|
||||
.Fa oldd
|
||||
\*(Ne
|
||||
.Fa newd ,
|
||||
|
||||
@ -58,7 +58,8 @@ This file is either an executable object file,
|
||||
or a file of data for an interpreter.
|
||||
An executable object file consists of an identifying header,
|
||||
followed by pages of data representing the initial program (text)
|
||||
and initialized data pages. Additional pages may be specified
|
||||
and initialized data pages.
|
||||
Additional pages may be specified
|
||||
by the header to be initialized with zero data; see
|
||||
.Xr elf 5
|
||||
and
|
||||
@ -87,7 +88,8 @@ and the name of the originally
|
||||
file becomes the second argument;
|
||||
otherwise, the name of the originally
|
||||
.Sy execve Ap d
|
||||
file becomes the first argument. The original arguments are shifted over to
|
||||
file becomes the first argument.
|
||||
The original arguments are shifted over to
|
||||
become the subsequent arguments.
|
||||
The zeroth argument is set to the specified
|
||||
.Em interpreter .
|
||||
@ -97,7 +99,8 @@ The argument
|
||||
is a pointer to a null-terminated array of
|
||||
character pointers to null-terminated character strings.
|
||||
These strings construct the argument list to be made available to the new
|
||||
process. At least one argument must be present in
|
||||
process.
|
||||
At least one argument must be present in
|
||||
the array; by custom, the first element should be
|
||||
the name of the executed program (for example, the last component of
|
||||
.Fa path ) .
|
||||
@ -159,7 +162,8 @@ These values may be used in changing the effective IDs later (see
|
||||
.Pp
|
||||
The set-ID bits are not honored if the respective file system has the
|
||||
.Cm nosuid
|
||||
option enabled or if the new process file is an interpreter file. Syscall
|
||||
option enabled or if the new process file is an interpreter file.
|
||||
Syscall
|
||||
tracing is disabled if effective IDs are changed.
|
||||
.Pp
|
||||
The new process also inherits the following attributes from
|
||||
|
||||
@ -52,7 +52,8 @@ The argument
|
||||
.Fa fd
|
||||
is a descriptor to be operated on by
|
||||
.Fa cmd
|
||||
as described below. Depending on the value of
|
||||
as described below.
|
||||
Depending on the value of
|
||||
.Fa cmd ,
|
||||
.Fn fcntl
|
||||
can take an additional third argument
|
||||
@ -157,8 +158,10 @@ corresponds to the
|
||||
flag of
|
||||
.Xr open 2 .
|
||||
.It Dv O_DIRECT
|
||||
Minimize or eliminate the cache effects of reading and writing. The system
|
||||
will attempt to avoid caching the data you read or write. If it cannot
|
||||
Minimize or eliminate the cache effects of reading and writing.
|
||||
The system
|
||||
will attempt to avoid caching the data you read or write.
|
||||
If it cannot
|
||||
avoid caching the data, it will minimize the impact the data has on the cache.
|
||||
Use of this flag can drastically reduce performance if not used with care.
|
||||
.It Dv O_ASYNC
|
||||
|
||||
@ -93,7 +93,8 @@ after other processes have gained and released the lock).
|
||||
.Pp
|
||||
Requesting a lock on an object that is already locked
|
||||
normally causes the caller to be blocked until the lock may be
|
||||
acquired. If
|
||||
acquired.
|
||||
If
|
||||
.Dv LOCK_NB
|
||||
is included in
|
||||
.Fa operation ,
|
||||
@ -102,13 +103,15 @@ the error
|
||||
.Er EWOULDBLOCK
|
||||
will be returned.
|
||||
.Sh NOTES
|
||||
Locks are on files, not file descriptors. That is, file descriptors
|
||||
Locks are on files, not file descriptors.
|
||||
That is, file descriptors
|
||||
duplicated through
|
||||
.Xr dup 2
|
||||
or
|
||||
.Xr fork 2
|
||||
do not result in multiple instances of a lock, but rather multiple
|
||||
references to a single lock. If a process holding a lock on a file
|
||||
references to a single lock.
|
||||
If a process holding a lock on a file
|
||||
forks and the child explicitly unlocks the file, the parent will
|
||||
lose its lock.
|
||||
.Pp
|
||||
|
||||
@ -84,7 +84,8 @@ Upon successful completion,
|
||||
.Fn fork
|
||||
returns a value
|
||||
of 0 to the child process and returns the process ID of the child
|
||||
process to the parent process. Otherwise, a value of -1 is returned
|
||||
process to the parent process.
|
||||
Otherwise, a value of -1 is returned
|
||||
to the parent process, no child process is created, and the global
|
||||
variable
|
||||
.Va errno
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue
Block a user