Asciidoc: Fix typo and remove invisible spaces which confuse po4a
This commit is contained in:
Mario Blättermann
parent
3cb9715628
commit
544e64e09e
|
|
@ -99,15 +99,15 @@ The terminal permissions. The default value is _0600_ or _0620_ if tty group is
|
|||
|
||||
*TTYGROUP* (string)::
|
||||
|
||||
The login tty will be owned by the *TTYGROUP*. The default value is _tty_. If the *TTYGROUP* does not exist, then the ownership of the terminal is set to the user´s primary group.
|
||||
The login tty will be owned by the *TTYGROUP*. The default value is _tty_. If the *TTYGROUP* does not exist, then the ownership of the terminal is set to the user's primary group.
|
||||
+
|
||||
The *TTYGROUP* can be either the name of a group or a numeric group identifier.
|
||||
|
||||
*HUSHLOGIN_FILE* (string)::
|
||||
|
||||
If defined, this file can inhibit all the usual chatter during the login sequence. If a full pathname (for example, _/etc/hushlogins_) is specified, then hushed mode will be enabled if the user´s name or shell are found in the file. If this global hush login file is empty then the hushed mode will be enabled for all users.
|
||||
If defined, this file can inhibit all the usual chatter during the login sequence. If a full pathname (for example, _/etc/hushlogins_) is specified, then hushed mode will be enabled if the user's name or shell are found in the file. If this global hush login file is empty then the hushed mode will be enabled for all users.
|
||||
+
|
||||
If a full pathname is not specified, then hushed mode will be enabled if the file exists in the user´s home directory.
|
||||
If a full pathname is not specified, then hushed mode will be enabled if the file exists in the user's home directory.
|
||||
+
|
||||
The default is to check _/etc/hushlogins_ and if it does not exist then _~/.hushlogin_.
|
||||
+
|
||||
|
|
|
|||
|
|
@ -21,9 +21,9 @@ findmnt - find a filesystem
|
|||
|
||||
== DESCRIPTION
|
||||
|
||||
*findmnt* will list all mounted filesystems or search for a filesystem. The *findmnt* command is able to search in _/etc/fstab_, _/etc/mtab_ or _/proc/self/mountinfo_. If _device_ or _mountpoint_ is not given, all filesystems are shown.
|
||||
*findmnt* will list all mounted filesystems or search for a filesystem. The *findmnt* command is able to search in _/etc/fstab_, _/etc/mtab_ or _/proc/self/mountinfo_. If _device_ or _mountpoint_ is not given, all filesystems are shown.
|
||||
|
||||
The device may be specified by device name, major:minor numbers, filesystem label or UUID, or partition label or UUID. Note that *findmnt* follows *mount*(8) behavior where a device name may be interpreted as a mountpoint (and vice versa) if the *--target*, *--mountpoint* or *--source* options are not specified.
|
||||
The device may be specified by device name, major:minor numbers, filesystem label or UUID, or partition label or UUID. Note that *findmnt* follows *mount*(8) behavior where a device name may be interpreted as a mountpoint (and vice versa) if the *--target*, *--mountpoint* or *--source* options are not specified.
|
||||
|
||||
The command prints all mounted filesystems in the tree-like format by default.
|
||||
|
||||
|
|
@ -123,7 +123,7 @@ Print only pseudo filesystems.
|
|||
Print only filesystems over-mounted by another filesystem.
|
||||
|
||||
*-R*, *--submounts*::
|
||||
Print recursively all submounts for the selected filesystems. The restrictions defined by options *-t*, *-O*, *-S*, *-T* and *--direction* are not applied to submounts. All submounts are always printed in tree-like order. The option enables the tree-like output format by default. This option has no effect for *--mtab* or *--fstab*.
|
||||
Print recursively all submounts for the selected filesystems. The restrictions defined by options *-t*, *-O*, *-S*, *-T* and *--direction* are not applied to submounts. All submounts are always printed in tree-like order. The option enables the tree-like output format by default. This option has no effect for *--mtab* or *--fstab*.
|
||||
|
||||
*-r*, *--raw*::
|
||||
Use raw output format. All potentially unsafe characters are hex-escaped (\x<code>).
|
||||
|
|
|
|||
|
|
@ -66,7 +66,7 @@ This field describes the block special device, remote filesystem or filesystem i
|
|||
|
||||
For ordinary mounts, it will hold (a link to) a block special device node (as created by *mknod*(2)) for the device to be mounted, like _/dev/cdrom_ or _/dev/sdb7_. For NFS mounts, this field is _<host>:<dir>_, e.g., _knuth.aeb.nl:/_. For filesystems with no storage, any string can be used, and will show up in *df*(1) output, for example. Typical usage is _proc_ for *procfs*; _mem_, _none_, or _tmpfs_ for *tmpfs*. Other special filesystems, like *udev* and *sysfs*, are typically not listed in *fstab*.
|
||||
|
||||
LABEL=<label> or UUID=<uuid> may be given instead of a device name. This is the recommended method, as device names are often a coincidence of hardware detection order, and can change when other disks are added or removed. For example, `LABEL=Boot' or `UUID=3e6be9de-8139-11d1-9106-a43f08d823a6'. (Use a filesystem-specific tool like *e2label*(8), *xfs_admin*(8), or *fatlabel*(8) to set LABELs on filesystems).
|
||||
LABEL=<label> or UUID=<uuid> may be given instead of a device name. This is the recommended method, as device names are often a coincidence of hardware detection order, and can change when other disks are added or removed. For example, 'LABEL=Boot' or 'UUID=3e6be9de-8139-11d1-9106-a43f08d823a6'. (Use a filesystem-specific tool like *e2label*(8), *xfs_admin*(8), or *fatlabel*(8) to set LABELs on filesystems).
|
||||
|
||||
It's also possible to use *PARTUUID=* and *PARTLABEL=*. These partitions identifiers are supported for example for GUID Partition Table (GPT).
|
||||
|
||||
|
|
|
|||
|
|
@ -187,7 +187,7 @@ The System Time is the time that matters. The Hardware Clock's basic purpose is
|
|||
|
||||
It is important that the System Time not have any discontinuities such as would happen if you used the *date*(1) program to set it while the system is running. You can, however, do whatever you want to the Hardware Clock while the system is running, and the next time Linux starts up, it will do so with the adjusted time from the Hardware Clock. Note: currently this is not possible on most systems because *hwclock --systohc* is called at shutdown.
|
||||
|
||||
The Linux kernel's timezone is set by *hwclock*. But don't be misled -- almost nobody cares what timezone the kernel thinks it is in. Instead, programs that care about the timezone (perhaps because they want to display a local time for you) almost always use a more traditional method of determining the timezone: They use the *TZ* environment variable or the _/etc/localtime_ file, as explained in the man page for *tzset*(3). However, some programs and fringe parts of the Linux kernel such as filesystems use the kernel's timezone value. An example is the vfat filesystem. If the kernel timezone value is wrong, the vfat filesystem will report and set the wrong timestamps on files. Another example is the kernel's NTP '11 minute mode'. If the kernel's timezone value and/or the _persistent_clock_is_local_ variable are wrong, then the Hardware Clock will be set incorrectly by '11 minute mode'. See the discussion below, under *Automatic Hardware Clock Synchronization by the Kernel*.
|
||||
The Linux kernel's timezone is set by *hwclock*. But don't be misled -- almost nobody cares what timezone the kernel thinks it is in. Instead, programs that care about the timezone (perhaps because they want to display a local time for you) almost always use a more traditional method of determining the timezone: They use the *TZ* environment variable or the _/etc/localtime_ file, as explained in the man page for *tzset*(3). However, some programs and fringe parts of the Linux kernel such as filesystems use the kernel's timezone value. An example is the vfat filesystem. If the kernel timezone value is wrong, the vfat filesystem will report and set the wrong timestamps on files. Another example is the kernel's NTP '11 minute mode'. If the kernel's timezone value and/or the _persistent_clock_is_local_ variable are wrong, then the Hardware Clock will be set incorrectly by '11 minute mode'. See the discussion below, under *Automatic Hardware Clock Synchronization by the Kernel*.
|
||||
|
||||
*hwclock* sets the kernel's timezone to the value indicated by *TZ* or _/etc/localtime_ with the *--hctosys* or *--systz* functions.
|
||||
|
||||
|
|
@ -235,13 +235,13 @@ You can use an adjtime file that was previously used with the *clock*(8) program
|
|||
|
||||
You should be aware of another way that the Hardware Clock is kept synchronized in some systems. The Linux kernel has a mode wherein it copies the System Time to the Hardware Clock every 11 minutes. This mode is a compile time option, so not all kernels will have this capability. This is a good mode to use when you are using something sophisticated like NTP to keep your System Clock synchronized. (NTP is a way to keep your System Time synchronized either to a time server somewhere on the network or to a radio clock hooked up to your system. See RFC 1305.)
|
||||
|
||||
If the kernel is compiled with the '11 minute mode' option it will be active when the kernel's clock discipline is in a synchronized state. When in this state, bit 6 (the bit that is set in the mask 0x0040) of the kernel's _time_status_ variable is unset. This value is output as the 'status' line of the *adjtimex --print* or *ntptime* commands.
|
||||
If the kernel is compiled with the '11 minute mode' option it will be active when the kernel's clock discipline is in a synchronized state. When in this state, bit 6 (the bit that is set in the mask 0x0040) of the kernel's _time_status_ variable is unset. This value is output as the 'status' line of the *adjtimex --print* or *ntptime* commands.
|
||||
|
||||
It takes an outside influence, like the NTP daemon to put the kernel's clock discipline into a synchronized state, and therefore turn on '11 minute mode'. It can be turned off by running anything that sets the System Clock the old fashioned way, including *hwclock --hctosys*. However, if the NTP daemon is still running, it will turn '11 minute mode' back on again the next time it synchronizes the System Clock.
|
||||
|
||||
If your system runs with '11 minute mode' on, it may need to use either *--hctosys* or *--systz* in a startup script, especially if the Hardware Clock is configured to use the local timescale. Unless the kernel is informed of what timescale the Hardware Clock is using, it may clobber it with the wrong one. The kernel uses UTC by default.
|
||||
|
||||
The first userspace command to set the System Clock informs the kernel what timescale the Hardware Clock is using. This happens via the _persistent_clock_is_local_ kernel variable. If *--hctosys* or *--systz* is the first, it will set this variable according to the adjtime file or the appropriate command-line argument. Note that when using this capability and the Hardware Clock timescale configuration is changed, then a reboot is required to notify the kernel.
|
||||
The first userspace command to set the System Clock informs the kernel what timescale the Hardware Clock is using. This happens via the _persistent_clock_is_local_ kernel variable. If *--hctosys* or *--systz* is the first, it will set this variable according to the adjtime file or the appropriate command-line argument. Note that when using this capability and the Hardware Clock timescale configuration is changed, then a reboot is required to notify the kernel.
|
||||
|
||||
*hwclock --adjust* should not be used with NTP '11 minute mode'.
|
||||
|
||||
|
|
@ -278,7 +278,7 @@ Some Linux distributions attempt to automatically calculate the System Clock dri
|
|||
|
||||
It may be more effective to simply track the System Clock drift with *sntp*, or *date -Ins* and a precision timepiece, and then calculate the correction manually.
|
||||
|
||||
After setting the tick and frequency values, continue to test and refine the adjustments until the System Clock keeps good time. See *adjtimex*(2) for more information and the example demonstrating manual drift calculations.
|
||||
After setting the tick and frequency values, continue to test and refine the adjustments until the System Clock keeps good time. See *adjtimex*(2) for more information and the example demonstrating manual drift calculations.
|
||||
|
||||
Once the System Clock is ticking smoothly, move on to the Hardware Clock.
|
||||
|
||||
|
|
@ -328,9 +328,9 @@ Linux does, however, attempt to accommodate the Hardware Clock being in the loca
|
|||
A discussion on date-time configuration would be incomplete without addressing timezones, this is mostly well covered by *tzset*(3). One area that seems to have no documentation is the 'right' directory of the Time Zone Database, sometimes called tz or zoneinfo.
|
||||
|
||||
//TRANSLATORS: Keep {plus} untranslated.
|
||||
There are two separate databases in the zoneinfo system, posix and 'right'. 'Right' (now named zoneinfo-leaps) includes leap seconds and posix does not. To use the 'right' database the System Clock must be set to (UTC {plus} leap seconds), which is equivalent to (TAI - 10). This allows calculating the exact number of seconds between two dates that cross a leap second epoch. The System Clock is then converted to the correct civil time, including UTC, by using the 'right' timezone files which subtract the leap seconds. Note: this configuration is considered experimental and is known to have issues.
|
||||
There are two separate databases in the zoneinfo system, posix and 'right'. 'Right' (now named zoneinfo-leaps) includes leap seconds and posix does not. To use the 'right' database the System Clock must be set to (UTC {plus} leap seconds), which is equivalent to (TAI - 10). This allows calculating the exact number of seconds between two dates that cross a leap second epoch. The System Clock is then converted to the correct civil time, including UTC, by using the 'right' timezone files which subtract the leap seconds. Note: this configuration is considered experimental and is known to have issues.
|
||||
|
||||
To configure a system to use a particular database all of the files located in its directory must be copied to the root of _/usr/share/zoneinfo_. Files are never used directly from the posix or 'right' subdirectories, e.g., TZ='_right/Europe/Dublin_'. This habit was becoming so common that the upstream zoneinfo project restructured the system's file tree by moving the posix and 'right' subdirectories out of the zoneinfo directory and into sibling directories:
|
||||
To configure a system to use a particular database all of the files located in its directory must be copied to the root of _/usr/share/zoneinfo_. Files are never used directly from the posix or 'right' subdirectories, e.g., TZ='_right/Europe/Dublin_'. This habit was becoming so common that the upstream zoneinfo project restructured the system's file tree by moving the posix and 'right' subdirectories out of the zoneinfo directory and into sibling directories:
|
||||
|
||||
_/usr/share/zoneinfo_, _/usr/share/zoneinfo-posix_, _/usr/share/zoneinfo-leaps_
|
||||
|
||||
|
|
|
|||
|
|
@ -454,10 +454,10 @@ The following options apply to any filesystem that is being mounted (but not eve
|
|||
All I/O to the filesystem should be done asynchronously. (See also the *sync* option.)
|
||||
|
||||
*atime*::
|
||||
Do not use the *noatime* feature, so the inode access time is controlled by kernel defaults. See also the descriptions of the *relatime* and *strictatime* mount options.
|
||||
Do not use the *noatime* feature, so the inode access time is controlled by kernel defaults. See also the descriptions of the *relatime* and *strictatime* mount options.
|
||||
|
||||
*noatime*::
|
||||
Do not update inode access times on this filesystem (e.g. for faster access on the news spool to speed up news servers). This works for all inode types (directories too), so it implies *nodiratime*.
|
||||
Do not update inode access times on this filesystem (e.g. for faster access on the news spool to speed up news servers). This works for all inode types (directories too), so it implies *nodiratime*.
|
||||
|
||||
*auto*::
|
||||
Can be mounted with the *-a* option.
|
||||
|
|
@ -536,7 +536,7 @@ The filesystem resides on a device that requires network access (used to prevent
|
|||
Do not report errors for this device if it does not exist.
|
||||
|
||||
*relatime*::
|
||||
Update inode access times relative to modify or change time. Access time is only updated if the previous access time was earlier than the current modify or change time. (Similar to *noatime*, but it doesn't break *mutt*(1) or other applications that need to know if a file has been read since the last time it was modified.)
|
||||
Update inode access times relative to modify or change time. Access time is only updated if the previous access time was earlier than the current modify or change time. (Similar to *noatime*, but it doesn't break *mutt*(1) or other applications that need to know if a file has been read since the last time it was modified.)
|
||||
+
|
||||
Since Linux 2.6.30, the kernel defaults to the behavior provided by this option (unless *noatime* was specified), and the *strictatime* option is required to obtain traditional semantics. In addition, since Linux 2.6.30, the file's last access time is always updated if it is more than 1 day old.
|
||||
|
||||
|
|
@ -1344,7 +1344,7 @@ ____
|
|||
*mount -t ext4 /tmp/disk.img /mnt*
|
||||
____
|
||||
|
||||
This type of mount knows about three options, namely *loop*, *offset* and *sizelimit*, that are really options to *losetup*(8). (These options can be used in addition to those specific to the filesystem type.)
|
||||
This type of mount knows about three options, namely *loop*, *offset* and *sizelimit*, that are really options to *losetup*(8). (These options can be used in addition to those specific to the filesystem type.)
|
||||
|
||||
Since Linux 2.6.25 auto-destruction of loop devices is supported, meaning that any loop device allocated by *mount* will be freed by *umount* independently of _/etc/mtab_.
|
||||
|
||||
|
|
|
|||
|
|
@ -63,7 +63,7 @@ Disable the corresponding device.
|
|||
Enable the corresponding device. If the device is hard-blocked, for example via a hardware switch, it will remain unavailable though it is now soft-unblocked.
|
||||
|
||||
**toggle id**|*type* [...]::
|
||||
Enable or disable the the corresponding device.
|
||||
Enable or disable the corresponding device.
|
||||
|
||||
== EXAMPLE
|
||||
....
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ unshare - run program in new namespaces
|
|||
|
||||
The *unshare* command creates new namespaces (as specified by the command-line options described below) and then executes the specified _program_. If _program_ is not given, then "${SHELL}" is run (default: _/bin/sh_).
|
||||
|
||||
By default, a new namespace persists only as long as it has member processes. A new namespace can be made persistent even when it has no member processes by bind mounting /proc/_pid_/ns/_type_ files to a filesystem path. A namespace that has been made persistent in this way can subsequently be entered with *nsenter*(1) even after the _program_ terminates (except PID namespaces where a permanently running init process is required). Once a persistent namespace is no longer needed, it can be unpersisted by using *umount*(8) to remove the bind mount. See the EXAMPLES section for more details.
|
||||
By default, a new namespace persists only as long as it has member processes. A new namespace can be made persistent even when it has no member processes by bind mounting /proc/_pid_/ns/_type_ files to a filesystem path. A namespace that has been made persistent in this way can subsequently be entered with *nsenter*(1) even after the _program_ terminates (except PID namespaces where a permanently running init process is required). Once a persistent namespace is no longer needed, it can be unpersisted by using *umount*(8) to remove the bind mount. See the EXAMPLES section for more details.
|
||||
|
||||
*unshare* since util-linux version 2.36 uses _/proc/[pid]/ns/pid_for_children_ and _/proc/[pid]/ns/time_for_children_ files for persistent PID and TIME namespaces. This change requires Linux kernel 4.17 or newer.
|
||||
|
||||
|
|
@ -33,7 +33,7 @@ Mounting and unmounting filesystems will not affect the rest of the system, exce
|
|||
Setting hostname or domainname will not affect the rest of the system. For further details, see *uts_namespaces*(7).
|
||||
|
||||
*IPC namespace*::
|
||||
The process will have an independent namespace for POSIX message queues as well as System V message queues, semaphore sets and shared memory segments. For further details, see *ipc_namespaces*(7).
|
||||
The process will have an independent namespace for POSIX message queues as well as System V message queues, semaphore sets and shared memory segments. For further details, see *ipc_namespaces*(7).
|
||||
|
||||
*network namespace*::
|
||||
The process will have independent IPv4 and IPv6 stacks, IP routing tables, firewall rules, the _/proc/net_ and _/sys/class/net_ directory trees, sockets, etc. For further details, see *network_namespaces*(7).
|
||||
|
|
@ -108,7 +108,7 @@ Recursively set the mount propagation flag in the new mount namespace. The defau
|
|||
**--setgroups allow**|*deny*::
|
||||
Allow or deny the *setgroups*(2) system call in a user namespace.
|
||||
+
|
||||
To be able to call *setgroups*(2), the calling process must at least have *CAP_SETGID*. But since Linux 3.19 a further restriction applies: the kernel gives permission to call *setgroups*(2) only after the GID map (**/proc/**__pid__*/gid_map*) has been set. The GID map is writable by root when *setgroups*(2) is enabled (i.e., *allow*, the default), and the GID map becomes writable by unprivileged processes when *setgroups*(2) is permanently disabled (with *deny*).
|
||||
To be able to call *setgroups*(2), the calling process must at least have *CAP_SETGID*. But since Linux 3.19 a further restriction applies: the kernel gives permission to call *setgroups*(2) only after the GID map (**/proc/**__pid__*/gid_map*) has been set. The GID map is writable by root when *setgroups*(2) is enabled (i.e., *allow*, the default), and the GID map becomes writable by unprivileged processes when *setgroups*(2) is permanently disabled (with *deny*).
|
||||
|
||||
*-R*, **--root=**__dir__::
|
||||
run the command with root directory set to _dir_.
|
||||
|
|
|
|||
|
|
@ -163,10 +163,10 @@ By default the hostname will be printed. With this option enabled, no hostname a
|
|||
By default the hostname is only printed until the first dot. With this option enabled, the fully qualified hostname by *gethostname*(3P) or (if not found) by *getaddrinfo*(3) is shown.
|
||||
|
||||
*--erase-chars* _string_::
|
||||
This option specifies additional characters that should be interpreted as a backspace ("ignore the previous character") when the user types the login name. The default additional ´erase´ has been ´#´, but since util-linux 2.23 no additional erase characters are enabled by default.
|
||||
This option specifies additional characters that should be interpreted as a backspace ("ignore the previous character") when the user types the login name. The default additional 'erase' has been '#', but since util-linux 2.23 no additional erase characters are enabled by default.
|
||||
|
||||
*--kill-chars* _string_::
|
||||
This option specifies additional characters that should be interpreted as a kill ("ignore all previous characters") when the user types the login name. The default additional ´kill´ has been ´@´, but since util-linux 2.23 no additional kill characters are enabled by default.
|
||||
This option specifies additional characters that should be interpreted as a kill ("ignore all previous characters") when the user types the login name. The default additional 'kill' has been '@', but since util-linux 2.23 no additional kill characters are enabled by default.
|
||||
|
||||
*--chdir* _directory_::
|
||||
Change directory before the login.
|
||||
|
|
|
|||
|
|
@ -142,7 +142,7 @@ The script ends when the forked shell exits (a _control-D_ for the Bourne shell
|
|||
|
||||
Certain interactive commands, such as *vi*(1), create garbage in the typescript file. *script* works best with commands that do not manipulate the screen, the results are meant to emulate a hardcopy terminal.
|
||||
|
||||
It is not recommended to run *script* in non-interactive shells. The inner shell of *script* is always interactive, and this could lead to unexpected results. If you use *script* in the shell initialization file, you have to avoid entering an infinite loop. You can use for example the *.profile* file, which is read by login shells only:
|
||||
It is not recommended to run *script* in non-interactive shells. The inner shell of *script* is always interactive, and this could lead to unexpected results. If you use *script* in the shell initialization file, you have to avoid entering an infinite loop. You can use for example the *.profile* file, which is read by login shells only:
|
||||
|
||||
....
|
||||
if test -t 0 ; then
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@
|
|||
:man source: util-linux {release-version}
|
||||
:page-layout: base
|
||||
:command: scriptlive
|
||||
:copyright: ©
|
||||
|
||||
== NAME
|
||||
|
||||
|
|
@ -68,7 +69,8 @@ mailto:kzak@redhat.com[Karel Zak]
|
|||
|
||||
== COPYRIGHT
|
||||
|
||||
Copyright © 2019 Karel Zak
|
||||
//TRANSLATORS: Keep {copyright} untranslated.
|
||||
Copyright {copyright} 2019 Karel Zak
|
||||
|
||||
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
||||
|
||||
|
|
|
|||
|
|
@ -118,7 +118,7 @@ Specify columns order on output.
|
|||
Specify the table name used for JSON output. The default is "table".
|
||||
|
||||
*-L, --keep-empty-lines*::
|
||||
Preserve whitespace-only lines in the input. The default is ignore empty lines at all. This option’s original name was *--table-empty-lines* but is now deprecated because it gives the false impression that the option only applies to table mode.
|
||||
Preserve whitespace-only lines in the input. The default is ignore empty lines at all. This option's original name was *--table-empty-lines* but is now deprecated because it gives the false impression that the option only applies to table mode.
|
||||
|
||||
*-r, --tree* _column_::
|
||||
Specify column to use tree-like output. Note that the circular dependencies and other anomalies in child and parent relation are silently ignored.
|
||||
|
|
|
|||
Loading…
Reference in New Issue