mirror of https://github.com/mkerrisk/man-pages
cpuid.4, fd.4, full.4, initrd.4, lirc.4, msr.4, null.4, vcs.4, charmap.5, core.5, dir_colors.5, filesystems.5, gai.conf.5, hosts.equiv.5, locale.5, motd.5, networks.5, nscd.conf.5, nss.5, proc.5, protocols.5, repertoiremap.5, services.5, tmpfs.5, ttytype.5, intro.8, nscd.8: ffix
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk
parent
a721e8b25f
commit
2dad4c59c8
16
man4/cpuid.4
16
man4/cpuid.4
|
|
@ -28,14 +28,14 @@
|
|||
cpuid \- x86 CPUID access device
|
||||
.SH DESCRIPTION
|
||||
CPUID provides an interface for querying information about the x86 CPU.
|
||||
|
||||
.PP
|
||||
This device is accessed by
|
||||
.BR lseek (2)
|
||||
or
|
||||
.BR pread (2)
|
||||
to the appropriate CPUID level and reading in chunks of 16 bytes.
|
||||
A larger read size means multiple reads of consecutive levels.
|
||||
|
||||
.PP
|
||||
The lower 32 bits of the file position is used as the incoming
|
||||
.IR %eax ,
|
||||
and the upper 32 bits of the file position as the incoming
|
||||
|
|
@ -44,7 +44,7 @@ the latter intended for "counting"
|
|||
.I eax
|
||||
levels like
|
||||
.IR eax=4 .
|
||||
|
||||
.PP
|
||||
This driver uses
|
||||
.IR /dev/cpu/CPUNUM/cpuid ,
|
||||
where
|
||||
|
|
@ -54,7 +54,7 @@ and on an SMP box will direct the access to CPU
|
|||
.I CPUNUM
|
||||
as listed in
|
||||
.IR /proc/cpuinfo .
|
||||
|
||||
.PP
|
||||
This file is protected so that it can be read only by the user
|
||||
.IR root ,
|
||||
or members of the group
|
||||
|
|
@ -64,7 +64,7 @@ The CPUID instruction can be directly executed by a program
|
|||
using inline assembler.
|
||||
However this device allows convenient
|
||||
access to all CPUs without changing process affinity.
|
||||
|
||||
.PP
|
||||
Most of the information in
|
||||
.I cpuid
|
||||
is reported by the kernel in cooked form either in
|
||||
|
|
@ -73,7 +73,7 @@ or through subdirectories in
|
|||
.IR /sys/devices/system/cpu .
|
||||
Direct CPUID access through this device should only
|
||||
be used in exceptional cases.
|
||||
|
||||
.PP
|
||||
The
|
||||
.I cpuid
|
||||
driver is not auto-loaded.
|
||||
|
|
@ -88,12 +88,12 @@ $ \fImodprobe cpuid\fP
|
|||
.PP
|
||||
There is no support for CPUID functions that require additional
|
||||
input registers.
|
||||
|
||||
.PP
|
||||
Very old x86 CPUs don't support CPUID.
|
||||
.SH SEE ALSO
|
||||
Intel Corporation, Intel 64 and IA-32 Architectures
|
||||
Software Developer's Manual Volume 2A:
|
||||
Instruction Set Reference, A-M, 3-180 CPUID reference.
|
||||
|
||||
.PP
|
||||
Intel Corporation, Intel Processor Identification and
|
||||
the CPUID Instruction, Application note 485.
|
||||
|
|
|
|||
|
|
@ -200,11 +200,11 @@ However, if a floppy is formatted with an inter-sector gap that is too small,
|
|||
performance may drop,
|
||||
to the point of needing a few seconds to access an entire track.
|
||||
To prevent this, use interleaved formats.
|
||||
|
||||
.PP
|
||||
It is not possible to
|
||||
read floppies which are formatted using GCR (group code recording),
|
||||
which is used by Apple II and Macintosh computers (800k disks).
|
||||
|
||||
.PP
|
||||
Reading floppies which are hard sectored (one hole per sector, with
|
||||
the index hole being a little skewed) is not supported.
|
||||
This used to be common with older 8-inch floppies.
|
||||
|
|
|
|||
|
|
@ -48,11 +48,11 @@ device will fail with an
|
|||
.B ENOSPC
|
||||
error.
|
||||
This can be used to test how a program handles disk-full errors.
|
||||
|
||||
.PP
|
||||
Reads from the
|
||||
.I /dev/full
|
||||
device will return \\0 characters.
|
||||
|
||||
.PP
|
||||
Seeks on
|
||||
.I /dev/full
|
||||
will always succeed.
|
||||
|
|
|
|||
|
|
@ -298,7 +298,7 @@ IP number 193.8.232.2 and named "idefix":
|
|||
>/proc/sys/kernel/nfs-root-addrs
|
||||
echo 255 >/proc/sys/kernel/real-root-dev
|
||||
.fi
|
||||
|
||||
.PP
|
||||
.BR Note :
|
||||
The use of
|
||||
.I /proc/sys/kernel/real-root-dev
|
||||
|
|
@ -477,7 +477,7 @@ The behavior may change in future versions of the Linux kernel.
|
|||
.BR ram (4),
|
||||
.BR freeramdisk (8),
|
||||
.BR rdev (8)
|
||||
|
||||
.PP
|
||||
.I Documentation/initrd.txt
|
||||
in the Linux kernel source tree, the LILO documentation,
|
||||
the LOADLIN documentation, the SYSLINUX documentation
|
||||
|
|
|
|||
|
|
@ -221,7 +221,7 @@ is a number in the range [0,100] which
|
|||
describes the pulse width as a percentage of the total cycle.
|
||||
Currently, no special meaning is defined for 0 or 100, but the values
|
||||
are reserved for future use.
|
||||
|
||||
.IP
|
||||
.TP
|
||||
.BR LIRC_GET_MIN_TIMEOUT " (\fIvoid\fP)", " "\
|
||||
LIRC_GET_MAX_TIMEOUT " (\fIvoid\fP)"
|
||||
|
|
|
|||
|
|
@ -33,13 +33,13 @@ registers (MSRs) of an x86 CPU.
|
|||
.I CPUNUM
|
||||
is the number of the CPU to access as listed in
|
||||
.IR /proc/cpuinfo .
|
||||
|
||||
.PP
|
||||
The register access is done by opening the file and seeking
|
||||
to the MSR number as offset in the file, and then
|
||||
reading or writing in chunks of 8 bytes.
|
||||
An I/O transfer of more than 8 bytes means multiple reads or writes
|
||||
of the same register.
|
||||
|
||||
.PP
|
||||
This file is protected so that it can be read and written only by the user
|
||||
.IR root ,
|
||||
or members of the group
|
||||
|
|
|
|||
|
|
@ -57,7 +57,7 @@ chown root:root /dev/null /dev/zero
|
|||
.SH NOTES
|
||||
If these devices are not writable and readable for all users, many
|
||||
programs will act strangely.
|
||||
|
||||
.PP
|
||||
Since Linux 2.6.31,
|
||||
.\" commit 2b83868723d090078ac0e2120e06a1cc94dbaef0
|
||||
reads from
|
||||
|
|
|
|||
22
man4/vcs.4
22
man4/vcs.4
|
|
@ -55,7 +55,7 @@ dimensions and cursor position:
|
|||
=
|
||||
.I y
|
||||
= 0 at the top left corner of the screen.)
|
||||
|
||||
.PP
|
||||
When a 512-character font is loaded,
|
||||
the 9th bit position can be fetched by applying the
|
||||
.BR ioctl (2)
|
||||
|
|
@ -78,7 +78,7 @@ so the system
|
|||
administrator can control access using filesystem permissions.
|
||||
.PP
|
||||
The devices for the first eight virtual consoles may be created by:
|
||||
|
||||
.PP
|
||||
.nf
|
||||
for x in 0 1 2 3 4 5 6 7 8; do
|
||||
mknod \-m 644 /dev/vcs$x c 7 $x;
|
||||
|
|
@ -86,7 +86,7 @@ The devices for the first eight virtual consoles may be created by:
|
|||
done
|
||||
chown root:tty /dev/vcs*
|
||||
.fi
|
||||
|
||||
.PP
|
||||
No
|
||||
.BR ioctl (2)
|
||||
requests are supported.
|
||||
|
|
@ -100,27 +100,27 @@ requests are supported.
|
|||
Introduced with version 1.1.92 of the Linux kernel.
|
||||
.SH EXAMPLE
|
||||
You may do a screendump on vt3 by switching to vt1 and typing
|
||||
|
||||
.PP
|
||||
cat /dev/vcs3 >foo
|
||||
|
||||
.PP
|
||||
Note that the output does not contain
|
||||
newline characters, so some processing may be required, like
|
||||
in
|
||||
|
||||
.PP
|
||||
fold \-w 81 /dev/vcs3 | lpr
|
||||
|
||||
.PP
|
||||
or (horrors)
|
||||
|
||||
.PP
|
||||
xetterm \-dump 3 \-file /proc/self/fd/1
|
||||
|
||||
.PP
|
||||
The
|
||||
.I /dev/vcsa0
|
||||
device is used for Braille support.
|
||||
|
||||
.PP
|
||||
This program displays the character and screen attributes under the
|
||||
cursor of the second virtual console, then changes the background color
|
||||
there:
|
||||
|
||||
.PP
|
||||
.nf
|
||||
#include <unistd.h>
|
||||
#include <stdlib.h>
|
||||
|
|
|
|||
|
|
@ -56,7 +56,7 @@ If not specified, it defaults to
|
|||
The character set definition section starts with the keyword
|
||||
.I CHARMAP
|
||||
in the first column.
|
||||
|
||||
.PP
|
||||
The following lines may have one of the two following forms to
|
||||
define the character set:
|
||||
.TP
|
||||
|
|
@ -85,7 +85,7 @@ The default character width is 1.
|
|||
The width section for individual characters starts with the keyword
|
||||
.I WIDTH
|
||||
in the first column.
|
||||
|
||||
.PP
|
||||
The following lines may have one of the two following forms to
|
||||
define the widths of the characters:
|
||||
.TP
|
||||
|
|
|
|||
28
man5/core.5
28
man5/core.5
|
|
@ -36,14 +36,14 @@ This image can be used in a debugger (e.g.,
|
|||
to inspect the state of the program at the time that it terminated.
|
||||
A list of the signals which cause a process to dump core can be found in
|
||||
.BR signal (7).
|
||||
|
||||
.PP
|
||||
A process can set its soft
|
||||
.B RLIMIT_CORE
|
||||
resource limit to place an upper limit on the size of the core dump file
|
||||
that will be produced if it receives a "core dump" signal; see
|
||||
.BR getrlimit (2)
|
||||
for details.
|
||||
|
||||
.PP
|
||||
There are various circumstances in which a core dump file is
|
||||
not produced:
|
||||
.IP * 3
|
||||
|
|
@ -207,7 +207,7 @@ and
|
|||
.I /proc/sys/kernel/core_uses_pid
|
||||
(see below)
|
||||
is nonzero, then .PID will be appended to the core filename.
|
||||
|
||||
.PP
|
||||
Paths are interpreted according to the settings that are active for the
|
||||
crashing process.
|
||||
That means the crashing process's mount namespace (see
|
||||
|
|
@ -216,7 +216,7 @@ its current working directory (found via
|
|||
.BR getcwd (2)),
|
||||
and its root directory (see
|
||||
.BR chroot (2)).
|
||||
|
||||
.PP
|
||||
Since version 2.4, Linux has also provided
|
||||
a more primitive method of controlling
|
||||
the name of the core dump file.
|
||||
|
|
@ -227,7 +227,7 @@ file contains the value 0, then a core dump file is simply named
|
|||
If this file contains a nonzero value, then the core dump file includes
|
||||
the process ID in a name of the form
|
||||
.IR core.PID .
|
||||
|
||||
.PP
|
||||
Since Linux 3.6,
|
||||
.\" 9520628e8ceb69fa9a4aee6b57f22675d9e1b709
|
||||
if
|
||||
|
|
@ -306,7 +306,7 @@ files prematurely.
|
|||
This in turn creates the
|
||||
possibility that a misbehaving collecting program can block
|
||||
the reaping of a crashed process by simply never exiting.
|
||||
|
||||
.PP
|
||||
Since Linux 2.6.32,
|
||||
.\" commit a293980c2e261bd5b0d2a77340dd04f684caff58
|
||||
the
|
||||
|
|
@ -316,7 +316,7 @@ The value in this file defines how many concurrent crashing
|
|||
processes may be piped to user-space programs in parallel.
|
||||
If this value is exceeded, then those crashing processes above this value
|
||||
are noted in the kernel log and their core dumps are skipped.
|
||||
|
||||
.PP
|
||||
A value of 0 in this file is special.
|
||||
It indicates that unlimited processes may be captured in parallel,
|
||||
but that no waiting will take place (i.e., the collecting
|
||||
|
|
@ -330,7 +330,7 @@ Since kernel 2.6.23, the Linux-specific
|
|||
file can be used to control which memory segments are written to the
|
||||
core dump file in the event that a core dump is performed for the
|
||||
process with the corresponding process ID.
|
||||
|
||||
.PP
|
||||
The value in the file is a bit mask of memory mapping types (see
|
||||
.BR mmap (2)).
|
||||
If a bit is set in the mask, then memory mappings of the
|
||||
|
|
@ -379,15 +379,15 @@ kernel configuration option is enabled), and 5.
|
|||
This default can be modified at boot time using the
|
||||
.I coredump_filter
|
||||
boot option.
|
||||
|
||||
.PP
|
||||
The value of this file is displayed in hexadecimal.
|
||||
(The default value is thus displayed as 33.)
|
||||
|
||||
.PP
|
||||
Memory-mapped I/O pages such as frame buffer are never dumped, and
|
||||
virtual DSO pages are always dumped, regardless of the
|
||||
.I coredump_filter
|
||||
value.
|
||||
|
||||
.PP
|
||||
A child process created via
|
||||
.BR fork (2)
|
||||
inherits its parent's
|
||||
|
|
@ -397,11 +397,11 @@ the
|
|||
.I coredump_filter
|
||||
value is preserved across an
|
||||
.BR execve (2).
|
||||
|
||||
.PP
|
||||
It can be useful to set
|
||||
.I coredump_filter
|
||||
in the parent shell before running a program, for example:
|
||||
|
||||
.PP
|
||||
.in +4n
|
||||
.nf
|
||||
.RB "$" " echo 0x7 > /proc/self/coredump_filter"
|
||||
|
|
@ -417,7 +417,7 @@ The
|
|||
.BR gdb (1)
|
||||
.I gcore
|
||||
command can be used to obtain a core dump of a running process.
|
||||
|
||||
.PP
|
||||
In Linux versions up to and including 2.6.27,
|
||||
.\" Changed with commit 6409324b385f3f63a03645b4422e3be67348d922
|
||||
if a multithreaded process (or, more precisely, a process that
|
||||
|
|
|
|||
|
|
@ -19,11 +19,11 @@ uses the environment variable
|
|||
.B LS_COLORS
|
||||
to determine the colors in which the filenames are to be displayed.
|
||||
This environment variable is usually set by a command like
|
||||
|
||||
.PP
|
||||
.RS
|
||||
eval \`dircolors some_path/dir_colors\`
|
||||
.RE
|
||||
|
||||
.PP
|
||||
found in a system default shell initialization file, like
|
||||
.I /etc/profile
|
||||
or
|
||||
|
|
@ -102,7 +102,7 @@ does not verify the validity of these options.
|
|||
.TP
|
||||
.B NORMAL \fIcolor-sequence\fR
|
||||
Specifies the color used for normal (nonfilename) text.
|
||||
|
||||
.IP
|
||||
Synonym:
|
||||
.BR NORM .
|
||||
.TP
|
||||
|
|
@ -114,7 +114,7 @@ Specifies the color used for directories.
|
|||
.TP
|
||||
.B LINK \fIcolor-sequence\fR
|
||||
Specifies the color used for a symbolic link.
|
||||
|
||||
.IP
|
||||
Synonyms:
|
||||
.BR LNK ,
|
||||
.BR SYMLINK .
|
||||
|
|
@ -139,7 +139,7 @@ color instead.
|
|||
.TP
|
||||
.B FIFO \fIcolor-sequence\fR
|
||||
Specifies the color used for a FIFO (named pipe).
|
||||
|
||||
.IP
|
||||
Synonym:
|
||||
.BR PIPE .
|
||||
.TP
|
||||
|
|
@ -152,13 +152,13 @@ Specifies the color used for a door (Solaris 2.5 and later).
|
|||
.TP
|
||||
.B BLK \fIcolor-sequence\fR
|
||||
Specifies the color used for a block device special file.
|
||||
|
||||
.IP
|
||||
Synonym:
|
||||
.BR BLOCK .
|
||||
.TP
|
||||
.B CHR \fIcolor-sequence\fR
|
||||
Specifies the color used for a character device special file.
|
||||
|
||||
.IP
|
||||
Synonym:
|
||||
.BR CHAR .
|
||||
.TP
|
||||
|
|
@ -167,13 +167,13 @@ Specifies the color used for a file with the executable attribute set.
|
|||
.TP
|
||||
.B SUID \fIcolor-sequence\fR
|
||||
Specifies the color used for a file with the set-user-ID attribute set.
|
||||
|
||||
.IP
|
||||
Synonym:
|
||||
.BR SETUID .
|
||||
.TP
|
||||
.B SGID \fIcolor-sequence\fR
|
||||
Specifies the color used for a file with the set-group-ID attribute set.
|
||||
|
||||
.IP
|
||||
Synonym:
|
||||
.BR SETGID .
|
||||
.TP
|
||||
|
|
@ -182,13 +182,13 @@ Specifies the color used for a directory with the sticky attribute set.
|
|||
.TP
|
||||
.B STICKY_OTHER_WRITABLE \fIcolor-sequence\fR
|
||||
Specifies the color used for an other-writable directory with the executable attribute set.
|
||||
|
||||
.IP
|
||||
Synonym:
|
||||
.BR OWT .
|
||||
.TP
|
||||
.B OTHER_WRITABLE \fIcolor-sequence\fR
|
||||
Specifies the color used for an other-writable directory without the executable attribute set.
|
||||
|
||||
.IP
|
||||
Synonym:
|
||||
.BR OWR .
|
||||
.TP
|
||||
|
|
@ -196,7 +196,7 @@ Synonym:
|
|||
Specifies the
|
||||
.I "left code"
|
||||
for non-ISO\ 6429 terminals (see below).
|
||||
|
||||
.IP
|
||||
Synonym:
|
||||
.BR LEFT .
|
||||
.TP
|
||||
|
|
@ -204,7 +204,7 @@ Synonym:
|
|||
Specifies the
|
||||
.I "right code"
|
||||
for non-ISO\ 6429 terminals (see below).
|
||||
|
||||
.IP
|
||||
Synonym:
|
||||
.BR RIGHT .
|
||||
.TP
|
||||
|
|
@ -212,7 +212,7 @@ Synonym:
|
|||
Specifies the
|
||||
.I "end code"
|
||||
for non-ISO\ 6429 terminals (see below).
|
||||
|
||||
.IP
|
||||
Synonym:
|
||||
.BR END .
|
||||
.TP
|
||||
|
|
@ -239,7 +239,7 @@ and the widely used and cloned DEC VT100, will recognize ISO 6429 color
|
|||
codes and harmlessly eliminate them from the output or emulate them.
|
||||
.B ls
|
||||
uses ISO 6429 codes by default, assuming colorization is enabled.
|
||||
|
||||
.PP
|
||||
ISO 6429 color sequences are composed of sequences of numbers
|
||||
separated by semicolons.
|
||||
The most common codes are:
|
||||
|
|
|
|||
|
|
@ -42,12 +42,12 @@ see
|
|||
for more details.
|
||||
If you need a currently unsupported filesystem, insert the corresponding
|
||||
module or recompile the kernel.
|
||||
|
||||
.PP
|
||||
In order to use a filesystem, you have to
|
||||
.I mount
|
||||
it; see
|
||||
.BR mount (8).
|
||||
|
||||
.PP
|
||||
Below a short description of the available or historically available
|
||||
filesystems in the Linux kernel.
|
||||
See kernel documentation for a comprehensive
|
||||
|
|
|
|||
|
|
@ -79,7 +79,7 @@ file is supported by glibc since version 2.5.
|
|||
.SH EXAMPLE
|
||||
The default table according to RFC\ 3484 would be specified with the
|
||||
following configuration file:
|
||||
|
||||
.PP
|
||||
.nf
|
||||
label ::1/128 0
|
||||
label ::/0 1
|
||||
|
|
|
|||
|
|
@ -87,84 +87,84 @@ Below are some example
|
|||
or
|
||||
.I ~/.rhosts
|
||||
files.
|
||||
|
||||
.PP
|
||||
Allow any user to log in from any host:
|
||||
|
||||
.PP
|
||||
+
|
||||
|
||||
.PP
|
||||
Allow any user from
|
||||
.I host
|
||||
with a matching local account to log in:
|
||||
|
||||
.PP
|
||||
host
|
||||
|
||||
.PP
|
||||
Note: the use of
|
||||
.I +host
|
||||
is never a valid syntax,
|
||||
including attempting to specify that any user from the host is allowed.
|
||||
|
||||
.PP
|
||||
Allow any user from
|
||||
.I host
|
||||
to log in:
|
||||
|
||||
.PP
|
||||
host +
|
||||
|
||||
.PP
|
||||
Note: this is distinct from the previous example
|
||||
since it does not require a matching local account.
|
||||
|
||||
.PP
|
||||
Allow
|
||||
.I user
|
||||
from
|
||||
.I host
|
||||
to log in as any non-root user:
|
||||
|
||||
.PP
|
||||
host user
|
||||
|
||||
.PP
|
||||
Allow all users with matching local accounts from
|
||||
.I host
|
||||
to log in except for
|
||||
.IR baduser :
|
||||
|
||||
.PP
|
||||
host \-baduser
|
||||
host
|
||||
|
||||
.PP
|
||||
Deny all users from
|
||||
.IR host :
|
||||
|
||||
.PP
|
||||
\-host
|
||||
|
||||
.PP
|
||||
Note: the use of
|
||||
.I "\-host\ \-user"
|
||||
is never a valid syntax,
|
||||
including attempting to specify that a particular user from the host
|
||||
is not trusted.
|
||||
|
||||
.PP
|
||||
Allow all users with matching local accounts on all hosts in a
|
||||
.IR netgroup :
|
||||
|
||||
.PP
|
||||
+@netgroup
|
||||
|
||||
.PP
|
||||
Disallow all users on all hosts in a
|
||||
.IR netgroup :
|
||||
|
||||
.PP
|
||||
\-@netgroup
|
||||
|
||||
.PP
|
||||
Allow all users in a
|
||||
.I netgroup
|
||||
to log in from
|
||||
.IR host
|
||||
as any non-root user:
|
||||
|
||||
.PP
|
||||
host +@netgroup
|
||||
|
||||
.PP
|
||||
Allow all users with matching local accounts on all hosts in a
|
||||
.I netgroup
|
||||
except
|
||||
.IR baduser :
|
||||
|
||||
.PP
|
||||
+@netgroup \-baduser
|
||||
+@netgroup
|
||||
|
||||
.PP
|
||||
Note: the deny statements must always precede the allow statements because
|
||||
the file is processed sequentially until the first matching rule is found.
|
||||
.SH SEE ALSO
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ The
|
|||
definition file contains all the information that the
|
||||
.BR localedef (1)
|
||||
command needs to convert it into the binary locale database.
|
||||
|
||||
.PP
|
||||
The definition files consist of sections which each describe a
|
||||
locale category in detail.
|
||||
See
|
||||
|
|
@ -104,12 +104,12 @@ the GNU C library supports the following nonstandard categories:
|
|||
See
|
||||
.BR locale (7)
|
||||
for a more detailed description of each category.
|
||||
|
||||
.PP
|
||||
.SS LC_ADDRESS
|
||||
The definition starts with the string
|
||||
.I LC_ADDRESS
|
||||
in the first column.
|
||||
|
||||
.PP
|
||||
The following keywords are allowed:
|
||||
.TP
|
||||
.I postal_fmt
|
||||
|
|
@ -231,7 +231,7 @@ definition ends with the string
|
|||
The definition starts with the string
|
||||
.I LC_CTYPE
|
||||
in the first column.
|
||||
|
||||
.PP
|
||||
The following keywords are allowed:
|
||||
.TP
|
||||
.I upper
|
||||
|
|
@ -456,7 +456,7 @@ will override any rule
|
|||
copied or included from other files.
|
||||
In case of duplicate rule definitions in the locale file,
|
||||
only the first rule is used.
|
||||
|
||||
.IP
|
||||
A transliteration rule consist of a character to be transliterated
|
||||
followed by a list of transliteration targets separated by semicolons.
|
||||
The first target which can be presented in the target character set
|
||||
|
|
@ -485,11 +485,11 @@ definition ends with the string
|
|||
.SS LC_COLLATE
|
||||
Note that glibc does not support all POSIX-defined options,
|
||||
only the options described below are supported (as of glibc 2.23).
|
||||
|
||||
.PP
|
||||
The definition starts with the string
|
||||
.I LC_COLLATE
|
||||
in the first column.
|
||||
|
||||
.PP
|
||||
The following keywords are allowed:
|
||||
.TP
|
||||
.I coll_weight_max
|
||||
|
|
@ -555,7 +555,7 @@ definition ends with the string
|
|||
The definition starts with the string
|
||||
.I LC_IDENTIFICATION
|
||||
in the first column.
|
||||
|
||||
.PP
|
||||
The following keywords are allowed:
|
||||
.TP
|
||||
.I title
|
||||
|
|
@ -633,7 +633,7 @@ definition ends with the string
|
|||
The definition starts with the string
|
||||
.I LC_MESSAGES
|
||||
in the first column.
|
||||
|
||||
.PP
|
||||
The following keywords are allowed:
|
||||
.TP
|
||||
.I yesexpr
|
||||
|
|
@ -658,7 +658,7 @@ definition ends with the string
|
|||
The definition starts with the string
|
||||
.I LC_MEASUREMENT
|
||||
in the first column.
|
||||
|
||||
.PP
|
||||
The following keywords are allowed:
|
||||
.TP
|
||||
.I measurement
|
||||
|
|
@ -681,7 +681,7 @@ definition ends with the string
|
|||
The definition starts with the string
|
||||
.I LC_MONETARY
|
||||
in the first column.
|
||||
|
||||
.PP
|
||||
The following keywords are allowed:
|
||||
.TP
|
||||
.I int_curr_symbol
|
||||
|
|
@ -873,7 +873,7 @@ definition ends with the string
|
|||
The definition starts with the string
|
||||
.I LC_NAME
|
||||
in the first column.
|
||||
|
||||
.PP
|
||||
Various keywords are allowed, but only
|
||||
.IR name_fmt
|
||||
is mandatory.
|
||||
|
|
@ -960,7 +960,7 @@ definition ends with the string
|
|||
The definition starts with the string
|
||||
.I LC_NUMERIC
|
||||
in the first column.
|
||||
|
||||
.PP
|
||||
The following keywords are allowed:
|
||||
.TP
|
||||
.I decimal_point
|
||||
|
|
@ -992,7 +992,7 @@ definition ends with the string
|
|||
The definition starts with the string
|
||||
.I LC_PAPER
|
||||
in the first column.
|
||||
|
||||
.PP
|
||||
The following keywords are allowed:
|
||||
.TP
|
||||
.I height
|
||||
|
|
@ -1009,7 +1009,7 @@ definition ends with the string
|
|||
The definition starts with the string
|
||||
.I LC_TELEPHONE
|
||||
in the first column.
|
||||
|
||||
.PP
|
||||
The following keywords are allowed:
|
||||
.TP
|
||||
.I tel_int_fmt
|
||||
|
|
@ -1061,7 +1061,7 @@ definition ends with the string
|
|||
The definition starts with the string
|
||||
.I LC_TIME
|
||||
in the first column.
|
||||
|
||||
.PP
|
||||
The following keywords are allowed:
|
||||
.TP
|
||||
.I abday
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ The contents of
|
|||
are displayed by
|
||||
.BR login (1)
|
||||
after a successful login but just before it executes the login shell.
|
||||
|
||||
.PP
|
||||
The abbreviation "motd" stands for "message of the day", and this file
|
||||
has been traditionally used for exactly that (it requires much less disk
|
||||
space than mail to all users).
|
||||
|
|
|
|||
|
|
@ -32,18 +32,18 @@ The file
|
|||
is a plain ASCII file that describes known DARPA networks and symbolic
|
||||
names for these networks.
|
||||
Each line represents a network and has the following structure:
|
||||
|
||||
.PP
|
||||
.RS
|
||||
.I name number aliases ...
|
||||
.RE
|
||||
|
||||
.PP
|
||||
where the fields are delimited by spaces or tabs.
|
||||
Empty lines are ignored.
|
||||
The hash character (\fB#\fP) indicates the start of a comment:
|
||||
this character, and the remaining characters up to
|
||||
the end of the current line,
|
||||
are ignored by library functions that process the file.
|
||||
|
||||
.PP
|
||||
The field descriptions are:
|
||||
.TP
|
||||
.I name
|
||||
|
|
@ -59,7 +59,7 @@ The trailing ".0" (for the host component of the network address) may be omitted
|
|||
.I aliases
|
||||
Optional aliases for the network.
|
||||
.LP
|
||||
|
||||
.PP
|
||||
This file is read by the
|
||||
.BR route (8)
|
||||
and
|
||||
|
|
|
|||
|
|
@ -33,23 +33,23 @@ or TAB characters.
|
|||
A \(aq#\(aq (number sign) indicates the beginning of a
|
||||
comment; following characters, up to the end of the line,
|
||||
are not interpreted by nscd.
|
||||
|
||||
.PP
|
||||
Valid services are \fIpasswd\fP, \fIgroup\fP, \fIhosts\fP, \fIservices\fP,
|
||||
or \fInetgroup\fP.
|
||||
|
||||
.PP
|
||||
.B logfile
|
||||
.I debug-file-name
|
||||
.RS
|
||||
Specifies name of the file to which debug info should be written.
|
||||
.RE
|
||||
|
||||
.PP
|
||||
.B debug-level
|
||||
.I value
|
||||
.RS
|
||||
Sets the desired debug level.
|
||||
The default is 0.
|
||||
.RE
|
||||
|
||||
.PP
|
||||
.B threads
|
||||
.I number
|
||||
.RS
|
||||
|
|
@ -57,14 +57,14 @@ This is the number of threads that are started to wait for
|
|||
requests.
|
||||
At least five threads will always be created.
|
||||
.RE
|
||||
|
||||
.PP
|
||||
.B max-threads
|
||||
.I number
|
||||
.RS
|
||||
Specifies the maximum number of threads.
|
||||
The default is 32.
|
||||
.RE
|
||||
|
||||
.PP
|
||||
.B server-user
|
||||
.I user
|
||||
.RS
|
||||
|
|
@ -72,13 +72,13 @@ If this option is set, nscd will run as this user and not as root.
|
|||
If a separate cache for every user is used (\-S parameter), this
|
||||
option is ignored.
|
||||
.RE
|
||||
|
||||
.PP
|
||||
.B stat-user
|
||||
.I user
|
||||
.RS
|
||||
Specifies the user who is allowed to request statistics.
|
||||
.RE
|
||||
|
||||
.PP
|
||||
.B reload-count
|
||||
unlimited |
|
||||
.I number
|
||||
|
|
@ -87,14 +87,14 @@ Limit on the number of times a cached entry gets reloaded without being used
|
|||
before it gets removed.
|
||||
The default is 5.
|
||||
.RE
|
||||
|
||||
.PP
|
||||
.B paranoia
|
||||
.I <yes|no>
|
||||
.RS
|
||||
Enabling paranoia mode causes nscd to restart itself periodically.
|
||||
The default is no.
|
||||
.RE
|
||||
|
||||
.PP
|
||||
.B restart-interval
|
||||
.I time
|
||||
.RS
|
||||
|
|
@ -106,7 +106,7 @@ if periodic restart is enabled by enabling
|
|||
mode.
|
||||
The default is 3600.
|
||||
.RE
|
||||
|
||||
.PP
|
||||
.B enable-cache
|
||||
.I service
|
||||
.I <yes|no>
|
||||
|
|
@ -116,7 +116,7 @@ Enables or disables the specified
|
|||
cache.
|
||||
The default is no.
|
||||
.RE
|
||||
|
||||
.PP
|
||||
.B positive-time-to-live
|
||||
.I service
|
||||
.I value
|
||||
|
|
@ -129,7 +129,7 @@ is in seconds.
|
|||
Larger values increase cache hit rates and reduce mean
|
||||
response times, but increase problems with cache coherence.
|
||||
.RE
|
||||
|
||||
.PP
|
||||
.B negative-time-to-live
|
||||
.I service
|
||||
.I value
|
||||
|
|
@ -144,7 +144,7 @@ are several files owned by UIDs (user IDs) not in system databases (for
|
|||
example untarring the Linux kernel sources as root); should be kept small
|
||||
to reduce cache coherency problems.
|
||||
.RE
|
||||
|
||||
.PP
|
||||
.B suggested-size
|
||||
.I service
|
||||
.I value
|
||||
|
|
@ -154,7 +154,7 @@ This is the internal hash table size,
|
|||
should remain a prime number for optimum efficiency.
|
||||
The default is 211.
|
||||
.RE
|
||||
|
||||
.PP
|
||||
.B check-files
|
||||
.I service
|
||||
.I <yes|no>
|
||||
|
|
@ -171,7 +171,7 @@ and
|
|||
.IR /etc/netgroup .
|
||||
The default is yes.
|
||||
.RE
|
||||
|
||||
.PP
|
||||
.B persistent
|
||||
.I service
|
||||
.I <yes|no>
|
||||
|
|
@ -183,7 +183,7 @@ over server restarts; useful when
|
|||
mode is set.
|
||||
The default is no.
|
||||
.RE
|
||||
|
||||
.PP
|
||||
.B shared
|
||||
.I service
|
||||
.I <yes|no>
|
||||
|
|
@ -195,7 +195,7 @@ that they can directly search in them instead of having to ask the
|
|||
daemon over the socket each time a lookup is performed.
|
||||
The default is no.
|
||||
.RE
|
||||
|
||||
.PP
|
||||
.B max-db-size
|
||||
.I service
|
||||
.I bytes
|
||||
|
|
@ -204,7 +204,7 @@ The maximum allowable size, in bytes, of the database files for the
|
|||
.IR service .
|
||||
The default is 33554432.
|
||||
.RE
|
||||
|
||||
.PP
|
||||
.B auto-propagate
|
||||
.I service
|
||||
.I <yes|no>
|
||||
|
|
|
|||
|
|
@ -99,7 +99,7 @@ the next entry.
|
|||
\fI/etc/default/nss\fR
|
||||
.SH EXAMPLE
|
||||
The default configuration corresponds to the following configuration file:
|
||||
|
||||
.PP
|
||||
.nf
|
||||
NETID_AUTHORITATIVE=FALSE
|
||||
SERVICES_AUTHORITATIVE=FALSE
|
||||
|
|
|
|||
366
man5/proc.5
366
man5/proc.5
File diff suppressed because it is too large
Load Diff
|
|
@ -37,24 +37,24 @@ consulted instead of using the numbers in the ARPA include files, or,
|
|||
even worse, just guessing them.
|
||||
These numbers will occur in the
|
||||
protocol field of any IP header.
|
||||
|
||||
.PP
|
||||
Keep this file untouched since changes would result in incorrect IP
|
||||
packages.
|
||||
Protocol numbers and names are specified by the IANA
|
||||
(Internet Assigned Numbers Authority).
|
||||
.\" .. by the DDN Network Information Center.
|
||||
|
||||
.PP
|
||||
Each line is of the following format:
|
||||
|
||||
.PP
|
||||
.RS
|
||||
.I protocol number aliases ...
|
||||
.RE
|
||||
|
||||
.PP
|
||||
where the fields are delimited by spaces or tabs.
|
||||
Empty lines are ignored.
|
||||
If a line contains a hash mark (#), the hash mark and the part
|
||||
of the line following it are ignored.
|
||||
|
||||
.PP
|
||||
The field descriptions are:
|
||||
.TP
|
||||
.I protocol
|
||||
|
|
@ -80,6 +80,6 @@ naming service like Yellow Pages/NIS or BIND/Hesiod.
|
|||
The protocols definition file.
|
||||
.SH SEE ALSO
|
||||
.BR getprotoent (3)
|
||||
|
||||
.PP
|
||||
.UR http://www.iana.org\:/assignments\:/protocol\-numbers
|
||||
.UE
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ It defaults to the backslash (\\).
|
|||
The mapping section starts with the keyword
|
||||
.I CHARIDS
|
||||
in the first column.
|
||||
|
||||
.PP
|
||||
The mapping lines have the following form:
|
||||
.TP
|
||||
.I <symbolic-name> <code-point> comment
|
||||
|
|
|
|||
|
|
@ -49,13 +49,13 @@ The C library routines
|
|||
and
|
||||
.BR endservent (3)
|
||||
support querying this file from programs.
|
||||
|
||||
.PP
|
||||
Port numbers are assigned by the IANA (Internet Assigned Numbers
|
||||
Authority), and their current policy is to assign both TCP and UDP
|
||||
protocols when assigning a port number.
|
||||
Therefore, most entries will
|
||||
have two entries, even for TCP-only services.
|
||||
|
||||
.PP
|
||||
Port numbers below 1024 (so-called "low numbered" ports) can be
|
||||
bound to only by root (see
|
||||
.BR bind (2),
|
||||
|
|
@ -67,7 +67,7 @@ that the service running on the port is the standard implementation,
|
|||
and not a rogue service run by a user of the machine.
|
||||
Well-known port numbers specified by the IANA are normally
|
||||
located in this root-only space.
|
||||
|
||||
.PP
|
||||
The presence of an entry for a service in the
|
||||
.B services
|
||||
file does not necessarily mean that the service is currently running
|
||||
|
|
@ -82,7 +82,7 @@ and so won't appear in
|
|||
.BR inetd.conf (5).
|
||||
In particular, news (NNTP) and mail (SMTP) servers are often
|
||||
initialized from the system boot scripts.
|
||||
|
||||
.PP
|
||||
The location of the
|
||||
.B services
|
||||
file is defined by
|
||||
|
|
@ -91,7 +91,7 @@ in
|
|||
.IR <netdb.h> "."
|
||||
This is usually set to
|
||||
.IR /etc/services "."
|
||||
|
||||
.PP
|
||||
Each line describes one service, and is of the form:
|
||||
.IP
|
||||
\f2service-name\ \ \ port\f3/\f2protocol\ \ \ \f1[\f2aliases ...\f1]
|
||||
|
|
@ -125,11 +125,11 @@ Again, the names are case
|
|||
sensitive.
|
||||
.PP
|
||||
Either spaces or tabs may be used to separate the fields.
|
||||
|
||||
.PP
|
||||
Comments are started by the hash sign (#) and continue until the end
|
||||
of the line.
|
||||
Blank lines are skipped.
|
||||
|
||||
.PP
|
||||
The
|
||||
.I service-name
|
||||
should begin in the first column of the file, since leading spaces are
|
||||
|
|
@ -140,7 +140,7 @@ However, a conservative choice of characters should be used to minimize
|
|||
compatibility problems.
|
||||
For example, a\-z, 0\-9, and hyphen (\-) would seem a
|
||||
sensible choice.
|
||||
|
||||
.PP
|
||||
Lines not matching this format should not be present in the
|
||||
file.
|
||||
(Currently, they are silently skipped by
|
||||
|
|
@ -149,7 +149,7 @@ file.
|
|||
and
|
||||
.BR getservbyport (3).
|
||||
However, this behavior should not be relied on.)
|
||||
|
||||
.PP
|
||||
.\" The following is not true as at glibc 2.8 (a line with a comma is
|
||||
.\" ignored by getservent()); it's not clear if/when it was ever true.
|
||||
.\" As a backward compatibility feature, the slash (/) between the
|
||||
|
|
@ -162,7 +162,7 @@ However, this behavior should not be relied on.)
|
|||
.\"
|
||||
This file might be distributed over a network using a network-wide
|
||||
naming service like Yellow Pages/NIS or BIND/Hesiod.
|
||||
|
||||
.PP
|
||||
A sample
|
||||
.B services
|
||||
file might look like this:
|
||||
|
|
@ -215,5 +215,5 @@ Definition of
|
|||
.BR inetd.conf (5),
|
||||
.BR protocols (5),
|
||||
.BR inetd (8)
|
||||
|
||||
.PP
|
||||
Assigned Numbers RFC, most recently RFC\ 1700, (AKA STD0002).
|
||||
|
|
|
|||
14
man5/tmpfs.5
14
man5/tmpfs.5
|
|
@ -32,7 +32,7 @@ facility allows the creation of filesystems whose contents reside
|
|||
in virtual memory.
|
||||
Since the files on such filesystems typically reside in RAM,
|
||||
file access is extremely fast.
|
||||
|
||||
.PP
|
||||
The filesystem is automatically created when mounting
|
||||
a filesystem with the type
|
||||
.BR tmpfs
|
||||
|
|
@ -78,13 +78,13 @@ For a description of the mount options that may be employed when mounting a
|
|||
.B tmpfs
|
||||
filesystem, see
|
||||
.BR mount (8).
|
||||
|
||||
.PP
|
||||
In order for user-space tools and applications to create
|
||||
.B tmpfs
|
||||
filesystems, the kernel must be configured with the
|
||||
.B CONFIG_TMPFS
|
||||
option.
|
||||
|
||||
.PP
|
||||
The
|
||||
.BR tmpfs
|
||||
filesystem supports extended attributes (see
|
||||
|
|
@ -92,7 +92,7 @@ filesystem supports extended attributes (see
|
|||
but
|
||||
.I user
|
||||
extended attributes are not permitted.
|
||||
|
||||
.PP
|
||||
An internal shared memory filesystem is used for
|
||||
System V shared memory
|
||||
.RB ( shmget (2))
|
||||
|
|
@ -107,7 +107,7 @@ This filesystem is available regardless of whether
|
|||
the kernel was configured with the
|
||||
.B CONFIG_TMPFS
|
||||
option.
|
||||
|
||||
.PP
|
||||
A
|
||||
.B tmpfs
|
||||
filesystem mounted at
|
||||
|
|
@ -116,7 +116,7 @@ as used for the implementation of POSIX shared memory
|
|||
.RB ( shm_overview (7))
|
||||
and POSIX semaphores
|
||||
.RB ( sem_overview (7)).
|
||||
|
||||
.PP
|
||||
The amount of memory consumed by all
|
||||
.B tmpfs
|
||||
filesystems is shown in the
|
||||
|
|
@ -127,7 +127,7 @@ and in the
|
|||
.I shared
|
||||
field displayed by
|
||||
.BR free (1).
|
||||
|
||||
.PP
|
||||
The
|
||||
.B tmpfs
|
||||
facility was formerly called
|
||||
|
|
|
|||
|
|
@ -39,14 +39,14 @@ with tty lines.
|
|||
Each line consists of a terminal type, followed by
|
||||
whitespace, followed by a tty name (a device name without the
|
||||
.IR /dev/ ") prefix."
|
||||
|
||||
.PP
|
||||
This association is used by the program
|
||||
.BR tset (1)
|
||||
to set the environment variable
|
||||
.B TERM
|
||||
to the default terminal name for
|
||||
the user's current tty.
|
||||
|
||||
.PP
|
||||
This facility was designed for a traditional time-sharing environment
|
||||
featuring character-cell terminals hardwired to a UNIX minicomputer.
|
||||
It is little used on modern workstation and personal UNIX systems.
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@ Section 8 of the manual describes commands
|
|||
which either can be or are used only by the superuser,
|
||||
like system-administration commands, daemons,
|
||||
and hardware-related commands.
|
||||
|
||||
.PP
|
||||
As with the commands described in Section 1, the commands described
|
||||
in this section terminate with an exit status that indicates
|
||||
whether the command succeeded or failed.
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ The default configuration file,
|
|||
determines the behavior of the cache daemon.
|
||||
See
|
||||
.BR nscd.conf (5).
|
||||
|
||||
.PP
|
||||
.B nscd
|
||||
provides caching for accesses of the
|
||||
.BR passwd (5),
|
||||
|
|
@ -48,7 +48,7 @@ databases through standard libc interfaces, such as
|
|||
.BR getgrgid (3),
|
||||
.BR gethostbyname (3),
|
||||
and others.
|
||||
|
||||
.PP
|
||||
There are two caches for each database:
|
||||
a positive one for items found, and a negative one
|
||||
for items not found.
|
||||
|
|
|
|||
Loading…
Reference in New Issue