From: Mario Blättermann Date: Fri, 26 Mar 2021 19:54:06 +0000 (+0100) Subject: Asciidoc: Fix artifacts from initial import, third attempt X-Git-Tag: v2.37-rc1~34^2~13 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=9b7051d5bf7ccf64469f9602abe8c885c57f5899;p=thirdparty%2Futil-linux.git Asciidoc: Fix artifacts from initial import, third attempt --- diff --git a/man-common/util-linux-man.pot b/man-common/util-linux-man.pot index 9b3d38bb29..abe4629c6b 100644 --- a/man-common/util-linux-man.pot +++ b/man-common/util-linux-man.pot @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2021-03-26 17:27+0100\n" +"POT-Creation-Date: 2021-03-26 20:17+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -168,7 +168,7 @@ msgstr "" #: ../sys-utils/dmesg.1.adoc:13 ../sys-utils/eject.1.adoc:17 #: ../sys-utils/fallocate.1.adoc:9 ../sys-utils/flock.1.adoc:33 #: ../sys-utils/fsfreeze.8.adoc:9 ../sys-utils/fstab.5.adoc:43 -#: ../sys-utils/fstrim.8.adoc:9 ../sys-utils/hwclock.8.adoc:16 +#: ../sys-utils/fstrim.8.adoc:9 ../sys-utils/hwclock.8.adoc:17 #: ../sys-utils/ipcmk.1.adoc:13 ../sys-utils/ipcrm.1.adoc:14 #: ../sys-utils/ipcs.1.adoc:13 ../sys-utils/irqtop.1.adoc:9 #: ../sys-utils/ldattach.8.adoc:13 ../sys-utils/losetup.8.adoc:9 @@ -242,7 +242,7 @@ msgstr "" #: ../sys-utils/ctrlaltdel.8.adoc:17 ../sys-utils/dmesg.1.adoc:17 #: ../sys-utils/fallocate.1.adoc:13 ../sys-utils/flock.1.adoc:37 #: ../sys-utils/fsfreeze.8.adoc:13 ../sys-utils/fstab.5.adoc:47 -#: ../sys-utils/fstrim.8.adoc:13 ../sys-utils/hwclock.8.adoc:20 +#: ../sys-utils/fstrim.8.adoc:13 ../sys-utils/hwclock.8.adoc:21 #: ../sys-utils/ipcmk.1.adoc:17 ../sys-utils/ipcrm.1.adoc:18 #: ../sys-utils/ipcs.1.adoc:17 ../sys-utils/irqtop.1.adoc:13 #: ../sys-utils/ldattach.8.adoc:17 ../sys-utils/losetup.8.adoc:13 @@ -317,7 +317,7 @@ msgstr "" #: ../sys-utils/dmesg.1.adoc:31 ../sys-utils/eject.1.adoc:23 #: ../sys-utils/fallocate.1.adoc:21 ../sys-utils/flock.1.adoc:45 #: ../sys-utils/fsfreeze.8.adoc:17 ../sys-utils/fstab.5.adoc:51 -#: ../sys-utils/fstrim.8.adoc:17 ../sys-utils/hwclock.8.adoc:24 +#: ../sys-utils/fstrim.8.adoc:17 ../sys-utils/hwclock.8.adoc:25 #: ../sys-utils/ipcmk.1.adoc:21 ../sys-utils/ipcrm.1.adoc:24 #: ../sys-utils/ipcs.1.adoc:21 ../sys-utils/irqtop.1.adoc:17 #: ../sys-utils/ldattach.8.adoc:21 ../sys-utils/losetup.8.adoc:39 @@ -449,7 +449,7 @@ msgstr "" #: ../sys-utils/dmesg.1.adoc:187 ../sys-utils/eject.1.adoc:121 #: ../sys-utils/fallocate.1.adoc:90 ../sys-utils/flock.1.adoc:127 #: ../sys-utils/fsfreeze.8.adoc:57 ../sys-utils/fstab.5.adoc:135 -#: ../sys-utils/fstrim.8.adoc:85 ../sys-utils/hwclock.8.adoc:370 +#: ../sys-utils/fstrim.8.adoc:85 ../sys-utils/hwclock.8.adoc:372 #: ../sys-utils/ipcmk.1.adoc:53 ../sys-utils/ipcrm.1.adoc:72 #: ../sys-utils/ipcs.1.adoc:91 ../sys-utils/ldattach.8.adoc:122 #: ../sys-utils/lscpu.1.adoc:162 ../sys-utils/lsipc.1.adoc:107 @@ -557,7 +557,7 @@ msgstr "" #: ../sys-utils/dmesg.1.adoc:37 ../sys-utils/eject.1.adoc:35 #: ../sys-utils/fallocate.1.adoc:27 ../sys-utils/flock.1.adoc:53 #: ../sys-utils/fsfreeze.8.adoc:29 ../sys-utils/fstrim.8.adoc:27 -#: ../sys-utils/hwclock.8.adoc:104 ../sys-utils/ipcmk.1.adoc:25 +#: ../sys-utils/hwclock.8.adoc:105 ../sys-utils/ipcmk.1.adoc:25 #: ../sys-utils/ipcrm.1.adoc:36 ../sys-utils/ipcs.1.adoc:25 #: ../sys-utils/irqtop.1.adoc:23 ../sys-utils/ldattach.8.adoc:74 #: ../sys-utils/losetup.8.adoc:49 ../sys-utils/lscpu.1.adoc:84 @@ -651,7 +651,7 @@ msgstr "" #: ../sys-utils/dmesg.1.adoc:144 ../sys-utils/eject.1.adoc:52 #: ../sys-utils/fallocate.1.adoc:82 ../sys-utils/flock.1.adoc:88 #: ../sys-utils/fsfreeze.8.adoc:42 ../sys-utils/fstrim.8.adoc:65 -#: ../sys-utils/hwclock.8.adoc:101 ../sys-utils/ipcmk.1.adoc:46 +#: ../sys-utils/hwclock.8.adoc:102 ../sys-utils/ipcmk.1.adoc:46 #: ../sys-utils/ipcrm.1.adoc:64 ../sys-utils/ipcs.1.adoc:30 #: ../sys-utils/irqtop.1.adoc:40 ../sys-utils/ldattach.8.adoc:115 #: ../sys-utils/losetup.8.adoc:119 ../sys-utils/lscpu.1.adoc:116 @@ -702,7 +702,7 @@ msgstr "" #: ../sys-utils/dmesg.1.adoc:146 ../sys-utils/eject.1.adoc:54 #: ../sys-utils/fallocate.1.adoc:84 ../sys-utils/flock.1.adoc:90 #: ../sys-utils/fsfreeze.8.adoc:44 ../sys-utils/fstrim.8.adoc:67 -#: ../sys-utils/hwclock.8.adoc:103 ../sys-utils/ipcmk.1.adoc:48 +#: ../sys-utils/hwclock.8.adoc:104 ../sys-utils/ipcmk.1.adoc:48 #: ../sys-utils/ipcrm.1.adoc:66 ../sys-utils/ipcs.1.adoc:32 #: ../sys-utils/irqtop.1.adoc:42 ../sys-utils/ldattach.8.adoc:117 #: ../sys-utils/losetup.8.adoc:121 ../sys-utils/lscpu.1.adoc:118 @@ -756,7 +756,7 @@ msgstr "" #: ../sys-utils/dmesg.1.adoc:141 ../sys-utils/eject.1.adoc:85 #: ../sys-utils/fallocate.1.adoc:79 ../sys-utils/flock.1.adoc:85 #: ../sys-utils/fsfreeze.8.adoc:39 ../sys-utils/fstrim.8.adoc:62 -#: ../sys-utils/hwclock.8.adoc:98 ../sys-utils/ipcmk.1.adoc:43 +#: ../sys-utils/hwclock.8.adoc:99 ../sys-utils/ipcmk.1.adoc:43 #: ../sys-utils/ipcrm.1.adoc:61 ../sys-utils/ipcs.1.adoc:33 #: ../sys-utils/irqtop.1.adoc:37 ../sys-utils/ldattach.8.adoc:112 #: ../sys-utils/losetup.8.adoc:116 ../sys-utils/lscpu.1.adoc:142 @@ -1072,7 +1072,7 @@ msgstr "" #: ../sys-utils/ctrlaltdel.8.adoc:47 ../sys-utils/dmesg.1.adoc:181 #: ../sys-utils/eject.1.adoc:117 ../sys-utils/fallocate.1.adoc:85 #: ../sys-utils/flock.1.adoc:119 ../sys-utils/fsfreeze.8.adoc:53 -#: ../sys-utils/fstrim.8.adoc:81 ../sys-utils/hwclock.8.adoc:379 +#: ../sys-utils/fstrim.8.adoc:81 ../sys-utils/hwclock.8.adoc:381 #: ../sys-utils/ipcmk.1.adoc:49 ../sys-utils/ipcs.1.adoc:87 #: ../sys-utils/irqtop.1.adoc:60 ../sys-utils/ldattach.8.adoc:118 #: ../sys-utils/losetup.8.adoc:160 ../sys-utils/lscpu.1.adoc:156 @@ -1244,7 +1244,7 @@ msgstr "" #: ../sys-utils/dmesg.1.adoc:143 ../sys-utils/eject.1.adoc:87 #: ../sys-utils/fallocate.1.adoc:81 ../sys-utils/flock.1.adoc:87 #: ../sys-utils/fsfreeze.8.adoc:41 ../sys-utils/fstrim.8.adoc:64 -#: ../sys-utils/hwclock.8.adoc:100 ../sys-utils/ipcmk.1.adoc:45 +#: ../sys-utils/hwclock.8.adoc:101 ../sys-utils/ipcmk.1.adoc:45 #: ../sys-utils/ipcrm.1.adoc:63 ../sys-utils/ipcs.1.adoc:35 #: ../sys-utils/irqtop.1.adoc:39 ../sys-utils/ldattach.8.adoc:114 #: ../sys-utils/losetup.8.adoc:118 ../sys-utils/lscpu.1.adoc:144 @@ -1557,7 +1557,7 @@ msgstr "" #: ../misc-utils/findfs.8.adoc:56 ../misc-utils/findmnt.8.adoc:170 #: ../misc-utils/getopt.1.adoc:135 ../misc-utils/look.1.adoc:81 #: ../misc-utils/lsblk.8.adoc:138 ../misc-utils/whereis.1.adoc:110 -#: ../misc-utils/wipefs.8.adoc:84 ../sys-utils/hwclock.8.adoc:349 +#: ../misc-utils/wipefs.8.adoc:84 ../sys-utils/hwclock.8.adoc:351 #: ../sys-utils/losetup.8.adoc:134 ../sys-utils/mount.8.adoc:1395 #: ../sys-utils/mountpoint.1.adoc:56 ../sys-utils/swapon.8.adoc:124 #: ../sys-utils/umount.8.adoc:154 ../term-utils/script.1.adoc:132 @@ -1832,7 +1832,7 @@ msgstr "" #: ../schedutils/ionice.1.adoc:72 ../schedutils/uclampset.1.adoc:113 #: ../sys-utils/choom.1.adoc:37 ../sys-utils/eject.1.adoc:101 #: ../sys-utils/fsfreeze.8.adoc:49 ../sys-utils/fstab.5.adoc:125 -#: ../sys-utils/hwclock.8.adoc:169 ../sys-utils/ipcrm.1.adoc:67 +#: ../sys-utils/hwclock.8.adoc:170 ../sys-utils/ipcrm.1.adoc:67 #: ../sys-utils/ipcs.1.adoc:83 ../sys-utils/losetup.8.adoc:130 #: ../sys-utils/mountpoint.1.adoc:61 ../sys-utils/prlimit.1.adoc:114 #: ../sys-utils/renice.1.adoc:80 ../sys-utils/rtcwake.8.adoc:114 @@ -3231,7 +3231,7 @@ msgstr "" #: ../login-utils/su.1.adoc:119 ../misc-utils/look.1.adoc:86 #: ../misc-utils/mcookie.1.adoc:48 ../sys-utils/adjtime_config.5.adoc:50 #: ../sys-utils/ctrlaltdel.8.adoc:43 ../sys-utils/fstab.5.adoc:120 -#: ../sys-utils/hwclock.8.adoc:357 ../sys-utils/losetup.8.adoc:139 +#: ../sys-utils/hwclock.8.adoc:359 ../sys-utils/losetup.8.adoc:139 #: ../sys-utils/mount.8.adoc:1412 ../sys-utils/readprofile.8.adoc:60 #: ../sys-utils/renice.1.adoc:75 ../sys-utils/rtcwake.8.adoc:118 #: ../sys-utils/swapon.8.adoc:132 ../sys-utils/tunelp.8.adoc:59 @@ -3302,7 +3302,7 @@ msgstr "" #: ../schedutils/uclampset.1.adoc:82 ../sys-utils/blkdiscard.8.adoc:49 #: ../sys-utils/blkzone.8.adoc:98 ../sys-utils/chmem.8.adoc:52 #: ../sys-utils/eject.1.adoc:88 ../sys-utils/fallocate.1.adoc:64 -#: ../sys-utils/hwclock.8.adoc:166 ../sys-utils/losetup.8.adoc:95 +#: ../sys-utils/hwclock.8.adoc:167 ../sys-utils/losetup.8.adoc:95 #: ../sys-utils/mount.8.adoc:429 ../sys-utils/readprofile.8.adoc:51 #: ../sys-utils/rtcwake.8.adoc:105 ../sys-utils/setarch.8.adoc:37 #: ../sys-utils/swapon.8.adoc:89 ../sys-utils/umount.8.adoc:111 @@ -3372,7 +3372,7 @@ msgstr "" #: ../misc-utils/rename.1.adoc:58 ../sys-utils/chcpu.8.adoc:59 #: ../sys-utils/chmem.8.adoc:58 ../sys-utils/dmesg.1.adoc:177 #: ../sys-utils/eject.1.adoc:97 ../sys-utils/flock.1.adoc:91 -#: ../sys-utils/fstrim.8.adoc:68 ../sys-utils/hwclock.8.adoc:339 +#: ../sys-utils/fstrim.8.adoc:68 ../sys-utils/hwclock.8.adoc:341 #: ../sys-utils/losetup.8.adoc:126 ../sys-utils/lsipc.1.adoc:87 #: ../sys-utils/mount.8.adoc:1355 ../sys-utils/mountpoint.1.adoc:43 #: ../sys-utils/swapon.8.adoc:95 ../sys-utils/switch_root.8.adoc:33 @@ -4006,14 +4006,14 @@ msgstr "" #. type: Plain text #: ../disk-utils/mkfs.cramfs.8.adoc:24 -msgid "File sizes are limited to less than 16 MB." +msgid "File sizes are limited to less than 16 MB." msgstr "" #. type: Plain text #: ../disk-utils/mkfs.cramfs.8.adoc:26 msgid "" -"Maximum file system size is a little under 272 MB. (The last file on the " -"file system must begin before the 256 MB block, but can extend past it.)" +"Maximum file system size is a little under 272 MB. (The last file on the " +"file system must begin before the 256 MB block, but can extend past it.)" msgstr "" #. type: Title == @@ -9290,10 +9290,10 @@ msgstr "" #. type: Plain text #: ../login-utils/lslogins.1.adoc:86 msgid "" -"Show system accounts.  These are by default all accounts with a UID " -"between 101 and 999 (inclusive), with the exception of either nobody or " -"nfsnobody (UID 65534). This hardcoded default may be overwritten by " -"parameters SYS_UID_MIN and SYS_UID_MAX in the file _/etc/login.defs_." +"Show system accounts. These are by default all accounts with a UID between " +"101 and 999 (inclusive), with the exception of either nobody or nfsnobody " +"(UID 65534). This hardcoded default may be overwritten by parameters " +"SYS_UID_MIN and SYS_UID_MAX in the file _/etc/login.defs_." msgstr "" #. type: Labeled list @@ -9376,7 +9376,7 @@ msgstr "" #. type: Labeled list #: ../login-utils/lslogins.1.adoc:113 ../login-utils/runuser.1.adoc:105 #: ../login-utils/su.1.adoc:112 ../misc-utils/lsblk.8.adoc:129 -#: ../sys-utils/fstrim.8.adoc:72 ../sys-utils/hwclock.8.adoc:288 +#: ../sys-utils/fstrim.8.adoc:72 ../sys-utils/hwclock.8.adoc:289 #: ../sys-utils/lsipc.1.adoc:92 #, no-wrap msgid "1" @@ -9388,7 +9388,7 @@ msgid "if incorrect arguments specified," msgstr "" #. type: Labeled list -#: ../login-utils/lslogins.1.adoc:116 ../sys-utils/hwclock.8.adoc:291 +#: ../login-utils/lslogins.1.adoc:116 ../sys-utils/hwclock.8.adoc:292 #: ../sys-utils/lsipc.1.adoc:95 #, no-wrap msgid "2" @@ -21248,18 +21248,18 @@ msgid "hwclock(8)" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:19 +#: ../sys-utils/hwclock.8.adoc:20 msgid "hwclock - time clocks utility" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:23 +#: ../sys-utils/hwclock.8.adoc:24 #, no-wrap msgid "*hwclock* [_function_] [_option_...]\n" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:27 +#: ../sys-utils/hwclock.8.adoc:28 #, no-wrap msgid "" "*hwclock* is an administration tool for the time clocks. It can: display the " @@ -21271,7 +21271,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:29 +#: ../sys-utils/hwclock.8.adoc:30 msgid "" "Since v2.26 important changes were made to the *--hctosys* function and the " "*--directisa* option, and a new option *--update-drift* was added. See their " @@ -21279,26 +21279,26 @@ msgid "" msgstr "" #. type: Title == -#: ../sys-utils/hwclock.8.adoc:30 +#: ../sys-utils/hwclock.8.adoc:31 #, no-wrap msgid "FUNCTIONS" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:33 +#: ../sys-utils/hwclock.8.adoc:34 msgid "" "The following functions are mutually exclusive, only one can be given at a " "time. If none is given, the default is *--show*." msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:34 +#: ../sys-utils/hwclock.8.adoc:35 #, no-wrap msgid "*-a, --adjust*" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:36 +#: ../sys-utils/hwclock.8.adoc:37 msgid "" "Add or subtract time from the Hardware Clock to account for systematic drift " "since the last time the clock was set or adjusted. See the discussion below, " @@ -21306,20 +21306,20 @@ msgid "" msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:37 +#: ../sys-utils/hwclock.8.adoc:38 #, no-wrap msgid "*--getepoch*; *--setepoch*" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:39 +#: ../sys-utils/hwclock.8.adoc:40 msgid "" "These functions are for Alpha machines only, and are only available through " "the Linux kernel RTC driver." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:41 +#: ../sys-utils/hwclock.8.adoc:42 msgid "" "They are used to read and set the kernel's Hardware Clock epoch value. Epoch " "is the number of years into AD to which a zero year value in the Hardware " @@ -21329,27 +21329,27 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:43 +#: ../sys-utils/hwclock.8.adoc:44 msgid "" "The *­--setepoch* function requires using the *­--epoch* option to specify " "the year. For example:" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:45 +#: ../sys-utils/hwclock.8.adoc:46 #, no-wrap msgid "**hwclock --setepoch --epoch=1952**\n" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:47 +#: ../sys-utils/hwclock.8.adoc:48 msgid "" "The RTC driver attempts to guess the correct epoch value, so setting it may " "not be required." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:49 +#: ../sys-utils/hwclock.8.adoc:50 msgid "" "This epoch value is used whenever *­hwclock* reads or sets the Hardware " "Clock on an Alpha machine. For ISA machines the kernel uses the fixed " @@ -21357,13 +21357,13 @@ msgid "" msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:50 +#: ../sys-utils/hwclock.8.adoc:51 #, no-wrap msgid "*--predict*" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:52 +#: ../sys-utils/hwclock.8.adoc:53 msgid "" "Predict what the Hardware Clock will read in the future based upon the time " "given by the *--date* option and the information in _{ADJTIME_PATH}_. This " @@ -21372,21 +21372,21 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:54 +#: ../sys-utils/hwclock.8.adoc:55 msgid "" "Do not use this function if the Hardware Clock is being modified by anything " -"other than the current operating system's *­hwclock* command, such as " -"­'11 minute mode' or from dual-booting another OS." +"other than the current operating system's *hwclock* command, such as '11 " +"minute mode' or from dual-booting another OS." msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:55 +#: ../sys-utils/hwclock.8.adoc:56 #, no-wrap msgid "*-r*, *--show*; *--get*" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:57 +#: ../sys-utils/hwclock.8.adoc:58 msgid "" "Read the Hardware Clock and print its time to standard output in the *ISO " "8601* format. The time shown is always in local time, even if you keep your " @@ -21394,30 +21394,30 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:59 +#: ../sys-utils/hwclock.8.adoc:60 msgid "" "Showing the Hardware Clock time is the default when no function is " "specified." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:61 +#: ../sys-utils/hwclock.8.adoc:62 msgid "" "The *--get* function also applies drift correction to the time read, based " "upon the information in _{ADJTIME_PATH}_. Do not use this function if the " "Hardware Clock is being modified by anything other than the current " -"operating system's *­hwclock* command, such as ­'11 minute mode' or from " +"operating system's *hwclock* command, such as '11 minute mode' or from " "dual-booting another OS." msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:62 +#: ../sys-utils/hwclock.8.adoc:63 #, no-wrap msgid "*-s*, *--hctosys*" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:64 +#: ../sys-utils/hwclock.8.adoc:65 msgid "" "Set the System Clock from the Hardware Clock. The time read from the " "Hardware Clock is compensated to account for systematic drift before using " @@ -21426,7 +21426,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:66 +#: ../sys-utils/hwclock.8.adoc:67 msgid "" "The System Clock must be kept in the UTC timescale for date-time " "applications to work correctly in conjunction with the timezone configured " @@ -21439,7 +21439,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:68 +#: ../sys-utils/hwclock.8.adoc:69 msgid "" "The kernel also keeps a timezone value, the *­--hctosys* function sets it " "to the timezone configured for the system. The system timezone is configured " @@ -21450,41 +21450,40 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:70 +#: ../sys-utils/hwclock.8.adoc:71 msgid "" "When used in a startup script, making the *­--hctosys* function the first " -"caller of *­settimeofday*(2) from boot, it will set the NTP " -"­'11 minute mode' timescale via the _­persistent_clock_is_local_ kernel " -"variable. If the Hardware Clock's timescale configuration is changed then a " -"reboot is required to inform the kernel. See the discussion below, under " -"*Automatic Hardware Clock Synchronization by the Kernel*." +"caller of *settimeofday*(2) from boot, it will set the NTP '11 minute mode' " +"timescale via the _persistent_clock_is_local_ kernel variable. If the " +"Hardware Clock's timescale configuration is changed then a reboot is " +"required to inform the kernel. See the discussion below, under *Automatic " +"Hardware Clock Synchronization by the Kernel*." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:72 +#: ../sys-utils/hwclock.8.adoc:73 msgid "" "This is a good function to use in one of the system startup scripts before " "the file systems are mounted read/write." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:74 +#: ../sys-utils/hwclock.8.adoc:75 msgid "" "This function should never be used on a running system. Jumping system time " "will cause problems, such as corrupted filesystem timestamps. Also, if " -"something has changed the Hardware Clock, like NTP's ­'11 minute mode', " -"then *­--hctosys* will set the time incorrectly by including drift " -"compensation." +"something has changed the Hardware Clock, like NTP's '11 minute mode', then " +"*--hctosys* will set the time incorrectly by including drift compensation." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:76 +#: ../sys-utils/hwclock.8.adoc:77 msgid "" "Drift compensation can be inhibited by setting the drift factor in " "_{ADJTIME_PATH}_ to zero. This setting will be persistent as long as the " "*­--update-drift* option is not used with *­--systohc* at shutdown (or " "anywhere else). Another way to inhibit this is by using the *­--noadjfile* " -"option when calling the *­--hctosys* function. A third method is to delete " +"option when calling the *--hctosys* function. A third method is to delete " "the _{ADJTIME_PATH}_ file. *Hwclock* will then default to using the UTC " "timescale for the Hardware Clock. If the Hardware Clock is ticking local " "time it will need to be defined in the file. This can be done by calling " @@ -21494,7 +21493,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:78 +#: ../sys-utils/hwclock.8.adoc:79 msgid "" "A condition under which inhibiting *hwclock*'s drift correction may be " "desired is when dual-booting multiple operating systems. If while this " @@ -21504,20 +21503,20 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:80 +#: ../sys-utils/hwclock.8.adoc:81 msgid "" "For *hwclock*'s drift correction to work properly it is imperative that " "nothing changes the Hardware Clock while its Linux instance is not running." msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:81 +#: ../sys-utils/hwclock.8.adoc:82 #, no-wrap msgid "*--set*" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:83 +#: ../sys-utils/hwclock.8.adoc:84 msgid "" "Set the Hardware Clock to the time given by the *--date* option, and update " "the timestamps in _{ADJTIME_PATH}_. With the *­--update-drift* option also " @@ -21526,13 +21525,13 @@ msgid "" msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:84 +#: ../sys-utils/hwclock.8.adoc:85 #, no-wrap msgid "*--systz*" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:86 +#: ../sys-utils/hwclock.8.adoc:87 msgid "" "This is an alternate to the *­--hctosys* function that does not read the " "Hardware Clock nor set the System Clock; consequently there is not any drift " @@ -21542,14 +21541,14 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:88 +#: ../sys-utils/hwclock.8.adoc:89 msgid "" "It does the following things that are detailed above in the *­--hctosys* " "function:" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:90 +#: ../sys-utils/hwclock.8.adoc:91 msgid "" "Corrects the System Clock timescale to UTC as needed. Only instead of " "accomplishing this by setting the System Clock, *hwclock* simply informs the " @@ -21557,17 +21556,17 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:91 -msgid "Sets the kernel's NTP ­'11 minute mode' timescale." +#: ../sys-utils/hwclock.8.adoc:92 +msgid "Sets the kernel's NTP '11 minute mode' timescale." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:92 +#: ../sys-utils/hwclock.8.adoc:93 msgid "Sets the kernel's timezone." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:94 +#: ../sys-utils/hwclock.8.adoc:95 msgid "" "The first two are only available on the first call of ­*settimeofday*(2) " "after boot. Consequently this option only makes sense when used in a startup " @@ -21576,13 +21575,13 @@ msgid "" msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:95 +#: ../sys-utils/hwclock.8.adoc:96 #, no-wrap msgid "*-w*, *--systohc*" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:97 +#: ../sys-utils/hwclock.8.adoc:98 msgid "" "Set the Hardware Clock from the System Clock, and update the timestamps in " "_{ADJTIME_PATH}_. With the *­--update-drift* option also (re)calculate the " @@ -21591,43 +21590,43 @@ msgid "" msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:106 +#: ../sys-utils/hwclock.8.adoc:107 #, no-wrap msgid "**--adjfile=**__filename__" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:108 +#: ../sys-utils/hwclock.8.adoc:109 msgid "Override the default _{ADJTIME_PATH}_ file path." msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:109 +#: ../sys-utils/hwclock.8.adoc:110 #, no-wrap msgid "**­--date=**__date_string__" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:111 +#: ../sys-utils/hwclock.8.adoc:112 msgid "" "This option must be used with the *--set* or *­--predict* functions, " "otherwise it is ignored." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:113 +#: ../sys-utils/hwclock.8.adoc:114 #, no-wrap -msgid "*hwclock --set --date='16:45'*\n" +msgid "*hwclock --set --date='16:45'*\n" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:115 +#: ../sys-utils/hwclock.8.adoc:116 #, no-wrap -msgid "*hwclock --predict --date='2525-08-14 07:11:05'*\n" +msgid "*hwclock --predict --date='2525-08-14 07:11:05'*\n" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:117 +#: ../sys-utils/hwclock.8.adoc:118 msgid "" "The argument must be in local time, even if you keep your Hardware Clock in " "UTC. See the *­--localtime* option. Therefore, the argument should not " @@ -21639,13 +21638,13 @@ msgid "" msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:118 +#: ../sys-utils/hwclock.8.adoc:119 #, no-wrap msgid "**­--delay=**__seconds__" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:120 +#: ../sys-utils/hwclock.8.adoc:121 msgid "" "This option can be used to overwrite the internally used delay when setting " "the clock time. The default is 0.5 (500ms) for rtc_cmos, for another RTC " @@ -21654,7 +21653,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:122 +#: ../sys-utils/hwclock.8.adoc:123 msgid "" "The 500ms default is based on commonly used MC146818A-compatible (x86) " "hardware clock. This Hardware Clock can only be set to any integer time plus " @@ -21666,26 +21665,26 @@ msgid "" msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:123 +#: ../sys-utils/hwclock.8.adoc:124 #, no-wrap msgid "*-D*, *--debug*" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:125 +#: ../sys-utils/hwclock.8.adoc:126 msgid "" "Use *--verbose*. The *­--debug* option has been deprecated and may be " "repurposed or removed in a future release." msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:126 +#: ../sys-utils/hwclock.8.adoc:127 #, no-wrap msgid "*--directisa*" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:128 +#: ../sys-utils/hwclock.8.adoc:129 msgid "" "This option is meaningful for ISA compatible machines in the x86 and x86_64 " "family. For other machines, it has no effect. This option tells *­hwclock* " @@ -21700,26 +21699,26 @@ msgid "" msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:129 +#: ../sys-utils/hwclock.8.adoc:130 #, no-wrap msgid "**--epoch=**__year__" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:131 +#: ../sys-utils/hwclock.8.adoc:132 msgid "" "This option is required when using the *­--setepoch* function. The minimum " "_year_ value is 1900. The maximum is system dependent (*ULONG_MAX - 1*)." msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:132 +#: ../sys-utils/hwclock.8.adoc:133 #, no-wrap msgid "*-f*, **--rtc=**__filename__" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:134 +#: ../sys-utils/hwclock.8.adoc:135 msgid "" "Override *­hwclock*'s default rtc device file name. Otherwise it will use " "the first one found in this order: _/dev/rtc0_, _/dev/rtc_, " @@ -21727,18 +21726,18 @@ msgid "" msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:135 +#: ../sys-utils/hwclock.8.adoc:136 #, no-wrap msgid "*-l*, *--localtime*; *-u*, *--utc*" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:137 +#: ../sys-utils/hwclock.8.adoc:138 msgid "Indicate which timescale the Hardware Clock is set to." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:139 +#: ../sys-utils/hwclock.8.adoc:140 msgid "" "The Hardware Clock may be configured to use either the UTC or the local " "timescale, but nothing in the clock itself says which alternative is being " @@ -21749,7 +21748,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:141 +#: ../sys-utils/hwclock.8.adoc:142 msgid "" "If you specify neither *--utc* nor *­--localtime* then the one last given " "with a set function (*--set*, *­--systohc*, or *­--adjust*), as recorded " @@ -21758,20 +21757,20 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:143 +#: ../sys-utils/hwclock.8.adoc:144 msgid "" "Note: daylight saving time changes may be inconsistent when the Hardware " "Clock is kept in local time. See the discussion below, under *LOCAL vs UTC*." msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:144 +#: ../sys-utils/hwclock.8.adoc:145 #, no-wrap msgid "*--noadjfile*" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:146 +#: ../sys-utils/hwclock.8.adoc:147 msgid "" "Disable the facilities provided by _{ADJTIME_PATH}_. *­hwclock* will not " "read nor write to that file with this option. Either *--utc* or " @@ -21779,33 +21778,33 @@ msgid "" msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:147 +#: ../sys-utils/hwclock.8.adoc:148 #, no-wrap msgid "*--test*" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:149 +#: ../sys-utils/hwclock.8.adoc:150 msgid "" "Do not actually change anything on the system, that is, the Clocks or " "_{ADJTIME_PATH}_ (*­--verbose* is implicit with this option)." msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:150 +#: ../sys-utils/hwclock.8.adoc:151 #, no-wrap msgid "*--update-drift*" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:152 +#: ../sys-utils/hwclock.8.adoc:153 msgid "" "Update the Hardware Clock's drift factor in _{ADJTIME_PATH}_. It can only be " "used with *--set* or *­--systohc*." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:154 +#: ../sys-utils/hwclock.8.adoc:155 msgid "" "A minimum four hour period between settings is required. This is to avoid " "invalid calculations. The longer the period, the more precise the resulting " @@ -21813,7 +21812,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:156 +#: ../sys-utils/hwclock.8.adoc:157 msgid "" "This option was added in v2.26, because it is typical for systems to call " "*­hwclock --systohc* at shutdown; with the old behaviour this would " @@ -21821,14 +21820,14 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:158 +#: ../sys-utils/hwclock.8.adoc:159 msgid "" -"When using NTP with an ­'11 minute mode' kernel the drift factor would be " +"When using NTP with an '11 minute mode' kernel the drift factor would be " "clobbered to near zero." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:159 +#: ../sys-utils/hwclock.8.adoc:160 msgid "" "It would not allow the use of 'cold' drift correction. With most " "configurations using 'cold' drift will yield favorable results. Cold, means " @@ -21837,7 +21836,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:160 +#: ../sys-utils/hwclock.8.adoc:161 msgid "" "(Re)calculating drift factor on every shutdown delivers suboptimal " "results. For example, if ephemeral conditions cause the machine to be " @@ -21845,14 +21844,14 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:161 +#: ../sys-utils/hwclock.8.adoc:162 msgid "" "Significantly increased system shutdown times (as of v2.31 when not using " "*­--update-drift* the RTC is not read)." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:163 +#: ../sys-utils/hwclock.8.adoc:164 msgid "" "Having *­hwclock* calculate the drift factor is a good starting point, but " "for optimal results it will likely need to be adjusted by directly editing " @@ -21864,7 +21863,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:165 +#: ../sys-utils/hwclock.8.adoc:166 msgid "" "This option requires reading the Hardware Clock before setting it. If it " "cannot be read, then this option will cause the set functions to fail. This " @@ -21875,23 +21874,23 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:168 +#: ../sys-utils/hwclock.8.adoc:169 msgid "Display more details about what *­hwclock* is doing internally." msgstr "" #. type: Title === -#: ../sys-utils/hwclock.8.adoc:171 +#: ../sys-utils/hwclock.8.adoc:172 #, no-wrap msgid "Clocks in a Linux System" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:174 +#: ../sys-utils/hwclock.8.adoc:175 msgid "There are two types of date-time clocks:" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:176 +#: ../sys-utils/hwclock.8.adoc:177 #, no-wrap msgid "" "*The Hardware Clock:* This clock is an independent hardware device, with its " @@ -21900,7 +21899,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:178 +#: ../sys-utils/hwclock.8.adoc:179 msgid "" "On an ISA compatible system, this clock is specified as part of the ISA " "standard. A control program can read or set this clock only to a whole " @@ -21909,7 +21908,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:180 +#: ../sys-utils/hwclock.8.adoc:181 msgid "" "This clock is commonly called the hardware clock, the real time clock, the " "RTC, the BIOS clock, and the CMOS clock. Hardware Clock, in its capitalized " @@ -21918,7 +21917,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:182 +#: ../sys-utils/hwclock.8.adoc:183 msgid "" "Some non-ISA systems have a few real time clocks with only one of them " "having its own power domain. A very low power external I2C or SPI clock chip " @@ -21928,7 +21927,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:184 +#: ../sys-utils/hwclock.8.adoc:185 #, no-wrap msgid "" "*The System Clock:* This clock is part of the Linux kernel and is driven by " @@ -21941,7 +21940,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:186 +#: ../sys-utils/hwclock.8.adoc:187 msgid "" "The System Time is the time that matters. The Hardware Clock's basic purpose " "is to keep time when Linux is not running so that the System Clock can be " @@ -21950,7 +21949,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:188 +#: ../sys-utils/hwclock.8.adoc:189 msgid "" "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 " @@ -21962,26 +21961,26 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:190 +#: ../sys-utils/hwclock.8.adoc:191 msgid "" "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*." +"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*." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:192 +#: ../sys-utils/hwclock.8.adoc:193 #, no-wrap msgid "" "*­hwclock* sets the kernel's timezone to the value indicated by *TZ* or " @@ -21989,7 +21988,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:194 +#: ../sys-utils/hwclock.8.adoc:195 msgid "" "The kernel's timezone value actually consists of two parts: 1) a field " "tz_minuteswest indicating how many minutes local time (not adjusted for DST) " @@ -22000,13 +21999,13 @@ msgid "" msgstr "" #. type: Title === -#: ../sys-utils/hwclock.8.adoc:195 +#: ../sys-utils/hwclock.8.adoc:196 #, no-wrap msgid "Hardware Clock Access Methods" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:198 +#: ../sys-utils/hwclock.8.adoc:199 #, no-wrap msgid "" "*­hwclock* uses many different ways to get and set Hardware Clock " @@ -22018,7 +22017,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:200 +#: ../sys-utils/hwclock.8.adoc:201 msgid "" "However, this method is not always available as older systems do not have an " "rtc driver. On these systems, the method of accessing the Hardware Clock " @@ -22026,7 +22025,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:202 +#: ../sys-utils/hwclock.8.adoc:203 msgid "" "On an ISA compatible system, *­hwclock* can directly access the \"CMOS " "memory\" registers that constitute the clock, by doing I/O to Ports 0x70 and " @@ -22036,7 +22035,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:204 +#: ../sys-utils/hwclock.8.adoc:205 msgid "" "This is a really poor method of accessing the clock, for all the reasons " "that userspace programs are generally not supposed to do direct I/O and " @@ -22046,13 +22045,13 @@ msgid "" msgstr "" #. type: Title === -#: ../sys-utils/hwclock.8.adoc:205 +#: ../sys-utils/hwclock.8.adoc:206 #, no-wrap msgid "The Adjust Function" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:208 +#: ../sys-utils/hwclock.8.adoc:209 msgid "" "The Hardware Clock is usually not very accurate. However, much of its " "inaccuracy is completely predictable - it gains or loses the same amount of " @@ -22061,14 +22060,14 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:210 +#: ../sys-utils/hwclock.8.adoc:211 msgid "" "It works like this: *­hwclock* keeps a file, _{ADJTIME_PATH}_, that keeps " "some historical information. This is called the adjtime file." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:212 +#: ../sys-utils/hwclock.8.adoc:213 msgid "" "Suppose you start with no adjtime file. You issue a *­hwclock --set* " "command to set the Hardware Clock to the true current time. *­hwclock* " @@ -22089,7 +22088,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:214 +#: ../sys-utils/hwclock.8.adoc:215 msgid "" "When you use the *­--update-drift* option with *--set* or *­--systohc*, " "the systematic drift rate is (re)calculated by comparing the fully drift " @@ -22100,7 +22099,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:216 +#: ../sys-utils/hwclock.8.adoc:217 msgid "" "A small amount of error creeps in when the Hardware Clock is set, so " "*­--adjust* refrains from making any adjustment that is less than 1 " @@ -22110,7 +22109,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:218 +#: ../sys-utils/hwclock.8.adoc:219 #, no-wrap msgid "" "*­hwclock --hctosys* also uses the adjtime file data to compensate the " @@ -22123,13 +22122,13 @@ msgid "" msgstr "" #. type: Title === -#: ../sys-utils/hwclock.8.adoc:219 +#: ../sys-utils/hwclock.8.adoc:220 #, no-wrap msgid "The Adjtime File" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:222 +#: ../sys-utils/hwclock.8.adoc:223 msgid "" "While named for its historical purpose of controlling adjustments only, it " "actually contains other information used by *hwclock* from one invocation to " @@ -22137,12 +22136,12 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:224 +#: ../sys-utils/hwclock.8.adoc:225 msgid "The format of the adjtime file is, in ASCII:" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:226 +#: ../sys-utils/hwclock.8.adoc:227 msgid "" "Line 1: Three numbers, separated by blanks: 1) the systematic drift rate in " "seconds per day, floating point decimal; 2) the resulting number of seconds " @@ -22151,7 +22150,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:228 +#: ../sys-utils/hwclock.8.adoc:229 msgid "" "Line 2: One number: the resulting number of seconds since 1969 UTC of most " "recent calibration. Zero if there has been no calibration yet or it is known " @@ -22161,7 +22160,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:230 +#: ../sys-utils/hwclock.8.adoc:231 msgid "" "Line 3: \"UTC\" or \"LOCAL\". Tells whether the Hardware Clock is set to " "Coordinated Universal Time or local time. You can always override this value " @@ -22169,20 +22168,20 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:232 +#: ../sys-utils/hwclock.8.adoc:233 msgid "" "You can use an adjtime file that was previously used with the *­clock*(8) " "program with *­hwclock*." msgstr "" #. type: Title === -#: ../sys-utils/hwclock.8.adoc:233 +#: ../sys-utils/hwclock.8.adoc:234 #, no-wrap msgid "Automatic Hardware Clock Synchronization by the Kernel" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:236 +#: ../sys-utils/hwclock.8.adoc:237 msgid "" "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 " @@ -22195,39 +22194,38 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:238 +#: ../sys-utils/hwclock.8.adoc:239 msgid "" -"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." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:240 +#: ../sys-utils/hwclock.8.adoc:241 msgid "" "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." +"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." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:242 +#: ../sys-utils/hwclock.8.adoc:243 msgid "" -"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 " +"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." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:244 +#: ../sys-utils/hwclock.8.adoc:245 msgid "" "The first userspace command to set the System Clock informs the kernel what " "timescale the Hardware Clock is using. This happens via the " @@ -22239,19 +22237,19 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:246 +#: ../sys-utils/hwclock.8.adoc:247 #, no-wrap -msgid "*­hwclock --adjust* should not be used with NTP ­'11 minute mode'.\n" +msgid "*hwclock --adjust* should not be used with NTP '11 minute mode'.\n" msgstr "" #. type: Title === -#: ../sys-utils/hwclock.8.adoc:247 +#: ../sys-utils/hwclock.8.adoc:248 #, no-wrap msgid "ISA Hardware Clock Century value" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:250 +#: ../sys-utils/hwclock.8.adoc:251 msgid "" "There is some sort of standard that defines CMOS memory Byte 50 on an ISA " "machine as an indicator of what century it is. *­hwclock* does not use or " @@ -22261,14 +22259,14 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:252 +#: ../sys-utils/hwclock.8.adoc:253 msgid "" "If you have a bona fide use for a CMOS century byte, contact the *­hwclock* " "maintainer; an option may be appropriate." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:254 +#: ../sys-utils/hwclock.8.adoc:255 msgid "" "Note that this section is only relevant when you are using the \"direct " "ISA\" method of accessing the Hardware Clock. ACPI provides a standard way " @@ -22276,62 +22274,62 @@ msgid "" msgstr "" #. type: Title == -#: ../sys-utils/hwclock.8.adoc:255 +#: ../sys-utils/hwclock.8.adoc:256 #, no-wrap msgid "DATE-TIME CONFIGURATION" msgstr "" #. type: Title === -#: ../sys-utils/hwclock.8.adoc:257 +#: ../sys-utils/hwclock.8.adoc:258 #, no-wrap msgid "Keeping Time without External Synchronization" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:260 +#: ../sys-utils/hwclock.8.adoc:261 msgid "This discussion is based on the following conditions:" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:262 +#: ../sys-utils/hwclock.8.adoc:263 msgid "" "Nothing is running that alters the date-time clocks, such as NTP daemon or a " "cron job.\"" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:263 +#: ../sys-utils/hwclock.8.adoc:264 msgid "" "The system timezone is configured for the correct local time. See below, " "under *POSIX vs 'RIGHT'*." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:264 +#: ../sys-utils/hwclock.8.adoc:265 msgid "" "Early during startup the following are called, in this order: *­adjtimex " "--tick* _value_ *--frequency* _value_ *­hwclock --hctosys*" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:265 +#: ../sys-utils/hwclock.8.adoc:266 msgid "During shutdown the following is called: *­hwclock --systohc*" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:267 +#: ../sys-utils/hwclock.8.adoc:268 msgid "Systems without *adjtimex* may use *ntptime*." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:269 +#: ../sys-utils/hwclock.8.adoc:270 msgid "" "Whether maintaining precision time with NTP daemon or not, it makes sense to " "configure the system to keep reasonably good date-time on its own." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:271 +#: ../sys-utils/hwclock.8.adoc:272 msgid "" "The first step in making that happen is having a clear understanding of the " "big picture. There are two completely separate hardware devices running at " @@ -22345,7 +22343,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:273 +#: ../sys-utils/hwclock.8.adoc:274 msgid "" "This problem can be avoided when configuring drift correction for the System " "Clock by simply not shutting down the machine. This, plus the fact that all " @@ -22355,7 +22353,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:275 +#: ../sys-utils/hwclock.8.adoc:276 msgid "" "The System Clock drift is corrected with the *­adjtimex*(8) command's " "*--tick* and *­--frequency* options. These two work together: tick is the " @@ -22364,7 +22362,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:277 +#: ../sys-utils/hwclock.8.adoc:278 msgid "" "Some Linux distributions attempt to automatically calculate the System Clock " "drift with *­adjtimex*'s compare operation. Trying to correct one drifting " @@ -22377,7 +22375,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:279 +#: ../sys-utils/hwclock.8.adoc:280 msgid "" "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 " @@ -22385,7 +22383,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:281 +#: ../sys-utils/hwclock.8.adoc:282 msgid "" "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 " @@ -22393,12 +22391,12 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:283 +#: ../sys-utils/hwclock.8.adoc:284 msgid "Once the System Clock is ticking smoothly, move on to the Hardware Clock." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:285 +#: ../sys-utils/hwclock.8.adoc:286 msgid "" "As a rule, cold drift will work best for most use cases. This should be true " "even for 24/7 machines whose normal downtime consists of a reboot. In that " @@ -22408,77 +22406,77 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:287 +#: ../sys-utils/hwclock.8.adoc:288 #, no-wrap msgid "*Steps to calculate cold drift:*\n" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:290 +#: ../sys-utils/hwclock.8.adoc:291 #, no-wrap msgid "*Ensure that NTP daemon will not be launched at startup.*\n" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:293 +#: ../sys-utils/hwclock.8.adoc:294 msgid "The _System Clock_ time must be correct at shutdown!" msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:294 +#: ../sys-utils/hwclock.8.adoc:295 #, no-wrap msgid "3" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:296 +#: ../sys-utils/hwclock.8.adoc:297 msgid "Shut down the system." msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:297 +#: ../sys-utils/hwclock.8.adoc:298 #, no-wrap msgid "4" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:299 +#: ../sys-utils/hwclock.8.adoc:300 msgid "Let an extended period pass without changing the Hardware Clock." msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:300 +#: ../sys-utils/hwclock.8.adoc:301 #, no-wrap msgid "5" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:302 +#: ../sys-utils/hwclock.8.adoc:303 msgid "Start the system." msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:303 +#: ../sys-utils/hwclock.8.adoc:304 #, no-wrap msgid "6" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:305 +#: ../sys-utils/hwclock.8.adoc:306 msgid "" "Immediately use *hwclock* to set the correct time, adding the " "*­--update-drift* option." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:307 +#: ../sys-utils/hwclock.8.adoc:308 msgid "" "Note: if step 6 uses *­--systohc*, then the System Clock must be set " "correctly (step 6a) just before doing so." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:309 +#: ../sys-utils/hwclock.8.adoc:310 msgid "" "Having *hwclock* calculate the drift factor is a good starting point, but " "for optimal results it will likely need to be adjusted by directly editing " @@ -22490,34 +22488,34 @@ msgid "" msgstr "" #. type: Title === -#: ../sys-utils/hwclock.8.adoc:310 +#: ../sys-utils/hwclock.8.adoc:311 #, no-wrap msgid "LOCAL vs UTC" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:313 +#: ../sys-utils/hwclock.8.adoc:314 msgid "" "Keeping the Hardware Clock in a local timescale causes inconsistent daylight " "saving time results:" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:315 +#: ../sys-utils/hwclock.8.adoc:316 msgid "" "If Linux is running during a daylight saving time change, the time written " "to the Hardware Clock will be adjusted for the change." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:316 +#: ../sys-utils/hwclock.8.adoc:317 msgid "" "If Linux is NOT running during a daylight saving time change, the time read " "from the Hardware Clock will NOT be adjusted for the change." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:318 +#: ../sys-utils/hwclock.8.adoc:319 msgid "" "The Hardware Clock on an ISA compatible system keeps only a date and time, " "it has no concept of timezone nor daylight saving. Therefore, when *hwclock* " @@ -22526,7 +22524,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:320 +#: ../sys-utils/hwclock.8.adoc:321 msgid "" "Linux handles daylight saving time changes transparently only when the " "Hardware Clock is kept in the UTC timescale. Doing so is made easy for " @@ -22535,7 +22533,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:322 +#: ../sys-utils/hwclock.8.adoc:323 msgid "" "POSIX systems, like Linux, are designed to have the System Clock operate in " "the UTC timescale. The Hardware Clock's purpose is to initialize the System " @@ -22543,7 +22541,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:324 +#: ../sys-utils/hwclock.8.adoc:325 msgid "" "Linux does, however, attempt to accommodate the Hardware Clock being in the " "local timescale. This is primarily for dual-booting with older versions of " @@ -22553,13 +22551,13 @@ msgid "" msgstr "" #. type: Title === -#: ../sys-utils/hwclock.8.adoc:325 +#: ../sys-utils/hwclock.8.adoc:326 #, no-wrap msgid "POSIX vs 'RIGHT'" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:328 +#: ../sys-utils/hwclock.8.adoc:329 msgid "" "A discussion on date-time configuration would be incomplete without " "addressing timezones, this is mostly well covered by *tzset*(3). One area " @@ -22567,13 +22565,14 @@ msgid "" "Zone Database, sometimes called tz or zoneinfo." msgstr "" +#. TRANSLATORS: Keep {plus} untranslated. #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:330 +#: ../sys-utils/hwclock.8.adoc:332 msgid "" "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 + leap seconds), which is equivalent to ­(TAI - 10). This allows " +"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 " @@ -22582,7 +22581,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:332 +#: ../sys-utils/hwclock.8.adoc:334 msgid "" "To configure a system to use a particular database all of the files located " "in its directory must be copied to the root of " @@ -22594,14 +22593,14 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:334 +#: ../sys-utils/hwclock.8.adoc:336 msgid "" "_/usr/share/zoneinfo_, _/usr/share/zoneinfo-posix_, " "_/usr/share/zoneinfo-leaps_" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:336 +#: ../sys-utils/hwclock.8.adoc:338 msgid "" "Unfortunately, some Linux distributions are changing it back to the old tree " "structure in their packages. So the problem of system administrators " @@ -22616,7 +22615,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:338 +#: ../sys-utils/hwclock.8.adoc:340 msgid "" "Attempting to mix and match files from these separate databases will not " "work, because they each require the System Clock to use a different " @@ -22626,100 +22625,100 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:342 +#: ../sys-utils/hwclock.8.adoc:344 msgid "One of the following exit values will be returned:" msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:343 +#: ../sys-utils/hwclock.8.adoc:345 #, no-wrap msgid "*EXIT_SUCCESS* ('0' on POSIX systems)" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:345 +#: ../sys-utils/hwclock.8.adoc:347 msgid "Successful program execution." msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:346 +#: ../sys-utils/hwclock.8.adoc:348 #, no-wrap msgid "*EXIT_FAILURE* ('1' on POSIX systems)" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:348 +#: ../sys-utils/hwclock.8.adoc:350 msgid "The operation failed or the command syntax was not valid." msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:351 +#: ../sys-utils/hwclock.8.adoc:353 #, no-wrap msgid "*TZ*" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:353 +#: ../sys-utils/hwclock.8.adoc:355 msgid "" "If this variable is set its value takes precedence over the system " "configured timezone." msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:354 +#: ../sys-utils/hwclock.8.adoc:356 #, no-wrap msgid "*TZDIR*" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:356 +#: ../sys-utils/hwclock.8.adoc:358 msgid "" "If this variable is set its value takes precedence over the system " "configured timezone database directory path." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:359 ../sys-utils/rtcwake.8.adoc:121 +#: ../sys-utils/hwclock.8.adoc:361 ../sys-utils/rtcwake.8.adoc:121 #, no-wrap msgid "_{ADJTIME_PATH}_" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:361 +#: ../sys-utils/hwclock.8.adoc:363 msgid "The configuration and state file for hwclock." msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:362 +#: ../sys-utils/hwclock.8.adoc:364 #, no-wrap msgid "_/etc/localtime_" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:364 +#: ../sys-utils/hwclock.8.adoc:366 msgid "The system timezone file." msgstr "" #. type: Labeled list -#: ../sys-utils/hwclock.8.adoc:365 +#: ../sys-utils/hwclock.8.adoc:367 #, no-wrap msgid "_/usr/share/zoneinfo/_" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:367 +#: ../sys-utils/hwclock.8.adoc:369 msgid "The system timezone database directory." msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:369 +#: ../sys-utils/hwclock.8.adoc:371 msgid "" "Device files *hwclock* may try for Hardware Clock access: _/dev/rtc0_ " "_/dev/rtc_ _/dev/misc/rtc_ _/dev/efirtc_ _/dev/misc/efirtc_" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:378 +#: ../sys-utils/hwclock.8.adoc:380 #, no-wrap msgid "" "*date*(1),\n" @@ -22731,7 +22730,7 @@ msgid "" msgstr "" #. type: Plain text -#: ../sys-utils/hwclock.8.adoc:382 +#: ../sys-utils/hwclock.8.adoc:384 msgid "" "Written by mailto:bryanh@giraffe-data.com[Bryan Henderson], September 1996, " "based on work done on the *­clock*(8) program by Charles Hedrick, Rob " @@ -28262,7 +28261,7 @@ msgstr "" msgid "" "If the high byte of the file length contains other garbage, set this mount " "option to ignore the high order bits of the file length. This implies that a " -"file cannot be larger than 16 MB." +"file cannot be larger than 16 MB." msgstr "" #. type: Labeled list diff --git a/sys-utils/hwclock.8.adoc b/sys-utils/hwclock.8.adoc index 4056fdee80..b9b3fc9745 100644 --- a/sys-utils/hwclock.8.adoc +++ b/sys-utils/hwclock.8.adoc @@ -46,7 +46,7 @@ The *­--setepoch* function requires using the *­--epoch* option to specify the + The RTC driver attempts to guess the correct epoch value, so setting it may not be required. + -This epoch value is used whenever *­hwclock* reads or sets the Hardware Clock on an Alpha machine. For ISA machines the kernel uses the fixed Hardware Clock epoch of 1900. +This epoch value is used whenever *hwclock* reads or sets the Hardware Clock on an Alpha machine. For ISA machines the kernel uses the fixed Hardware Clock epoch of 1900. *--predict*:: Predict what the Hardware Clock will read in the future based upon the time given by the *--date* option and the information in _{ADJTIME_PATH}_. This is useful, for example, to account for drift when setting a Hardware Clock wakeup (aka alarm). See *­rtcwake*(8). @@ -73,28 +73,28 @@ This is a good function to use in one of the system startup scripts before the f + This function should never be used on a running system. Jumping system time will cause problems, such as corrupted filesystem timestamps. Also, if something has changed the Hardware Clock, like NTP's '11 minute mode', then *--hctosys* will set the time incorrectly by including drift compensation. + -Drift compensation can be inhibited by setting the drift factor in _{ADJTIME_PATH}_ to zero. This setting will be persistent as long as the *­--update-drift* option is not used with *­--systohc* at shutdown (or anywhere else). Another way to inhibit this is by using the *­--noadjfile* option when calling the *--hctosys* function. A third method is to delete the _{ADJTIME_PATH}_ file. *Hwclock* will then default to using the UTC timescale for the Hardware Clock. If the Hardware Clock is ticking local time it will need to be defined in the file. This can be done by calling *hwclock --localtime --adjust*; when the file is not present this command will not actually adjust the Clock, but it will create the file with local time configured, and a drift factor of zero. +Drift compensation can be inhibited by setting the drift factor in _{ADJTIME_PATH}_ to zero. This setting will be persistent as long as the *--update-drift* option is not used with *--systohc* at shutdown (or anywhere else). Another way to inhibit this is by using the *--noadjfile* option when calling the *--hctosys* function. A third method is to delete the _{ADJTIME_PATH}_ file. *Hwclock* will then default to using the UTC timescale for the Hardware Clock. If the Hardware Clock is ticking local time it will need to be defined in the file. This can be done by calling *hwclock --localtime --adjust*; when the file is not present this command will not actually adjust the Clock, but it will create the file with local time configured, and a drift factor of zero. + A condition under which inhibiting *hwclock*'s drift correction may be desired is when dual-booting multiple operating systems. If while this instance of Linux is stopped, another OS changes the Hardware Clock's value, then when this instance is started again the drift correction applied will be incorrect. + For *hwclock*'s drift correction to work properly it is imperative that nothing changes the Hardware Clock while its Linux instance is not running. *--set*:: -Set the Hardware Clock to the time given by the *--date* option, and update the timestamps in _{ADJTIME_PATH}_. With the *­--update-drift* option also (re)calculate the drift factor. Try it without the option if *­--set* fails. See *­--update-drift* below. +Set the Hardware Clock to the time given by the *--date* option, and update the timestamps in _{ADJTIME_PATH}_. With the *--update-drift* option also (re)calculate the drift factor. Try it without the option if *--set* fails. See *--update-drift* below. *--systz*:: -This is an alternate to the *­--hctosys* function that does not read the Hardware Clock nor set the System Clock; consequently there is not any drift correction. It is intended to be used in a startup script on systems with kernels above version 2.6 where you know the System Clock has been set from the Hardware Clock by the kernel during boot. +This is an alternate to the *--hctosys* function that does not read the Hardware Clock nor set the System Clock; consequently there is not any drift correction. It is intended to be used in a startup script on systems with kernels above version 2.6 where you know the System Clock has been set from the Hardware Clock by the kernel during boot. + -It does the following things that are detailed above in the *­--hctosys* function: +It does the following things that are detailed above in the *--hctosys* function: * Corrects the System Clock timescale to UTC as needed. Only instead of accomplishing this by setting the System Clock, *hwclock* simply informs the kernel and it handles the change. * Sets the kernel's NTP '11 minute mode' timescale. * Sets the kernel's timezone. -The first two are only available on the first call of ­*settimeofday*(2) after boot. Consequently this option only makes sense when used in a startup script. If the Hardware Clocks timescale configuration is changed then a reboot would be required to inform the kernel. +The first two are only available on the first call of *settimeofday*(2) after boot. Consequently this option only makes sense when used in a startup script. If the Hardware Clocks timescale configuration is changed then a reboot would be required to inform the kernel. *-w*, *--systohc*:: -Set the Hardware Clock from the System Clock, and update the timestamps in _{ADJTIME_PATH}_. With the *­--update-drift* option also (re)calculate the drift factor. Try it without the option if *­--systohc* fails. See *­--update-drift* below. +Set the Hardware Clock from the System Clock, and update the timestamps in _{ADJTIME_PATH}_. With the *--update-drift* option also (re)calculate the drift factor. Try it without the option if ­*--systohc* fails. See *--update-drift* below. *-V*, *--version*:: Display version information and exit. @@ -107,65 +107,65 @@ Display help text and exit. **--adjfile=**__filename__:: Override the default _{ADJTIME_PATH}_ file path. -**­--date=**__date_string__:: -This option must be used with the *--set* or *­--predict* functions, otherwise it is ignored. +**--date=**__date_string__:: +This option must be used with the *--set* or *--predict* functions, otherwise it is ignored. + *hwclock --set --date='16:45'* + -*hwclock --predict --date='2525-08-14 07:11:05'* +*hwclock --predict --date='2525-08-14 07:11:05'* + -The argument must be in local time, even if you keep your Hardware Clock in UTC. See the *­--localtime* option. Therefore, the argument should not include any timezone information. It also should not be a relative time like "+5 minutes", because *­hwclock*'s precision depends upon correlation between the argument's value and when the enter key is pressed. Fractional seconds are silently dropped. This option is capable of understanding many time and date formats, but the previous parameters should be observed. +The argument must be in local time, even if you keep your Hardware Clock in UTC. See the *--localtime* option. Therefore, the argument should not include any timezone information. It also should not be a relative time like "+5 minutes", because *hwclock*'s precision depends upon correlation between the argument's value and when the enter key is pressed. Fractional seconds are silently dropped. This option is capable of understanding many time and date formats, but the previous parameters should be observed. -**­--delay=**__seconds__:: +**--delay=**__seconds__:: This option can be used to overwrite the internally used delay when setting the clock time. The default is 0.5 (500ms) for rtc_cmos, for another RTC types the delay is 0. If RTC type is impossible to determine (from sysfs) then it defaults also to 0.5 to be backwardly compatible. + The 500ms default is based on commonly used MC146818A-compatible (x86) hardware clock. This Hardware Clock can only be set to any integer time plus one half second. The integer time is required because there is no interface to set or get a fractional second. The additional half second delay is because the Hardware Clock updates to the following second precisely 500 ms after setting the new time. Unfortunately, this behavior is hardware specific and in same cases another delay is required. *-D*, *--debug*:: -Use *--verbose*. The *­--debug* option has been deprecated and may be repurposed or removed in a future release. +Use *--verbose*. The *--debug* option has been deprecated and may be repurposed or removed in a future release. *--directisa*:: -This option is meaningful for ISA compatible machines in the x86 and x86_64 family. For other machines, it has no effect. This option tells *­hwclock* to use explicit I/O instructions to access the Hardware Clock. Without this option, *­hwclock* will use the rtc device file, which it assumes to be driven by the Linux RTC device driver. As of v2.26 it will no longer automatically use directisa when the rtc driver is unavailable; this was causing an unsafe condition that could allow two processes to access the Hardware Clock at the same time. Direct hardware access from userspace should only be used for testing, troubleshooting, and as a last resort when all other methods fail. See the *--rtc* option. +This option is meaningful for ISA compatible machines in the x86 and x86_64 family. For other machines, it has no effect. This option tells *hwclock* to use explicit I/O instructions to access the Hardware Clock. Without this option, *hwclock* will use the rtc device file, which it assumes to be driven by the Linux RTC device driver. As of v2.26 it will no longer automatically use directisa when the rtc driver is unavailable; this was causing an unsafe condition that could allow two processes to access the Hardware Clock at the same time. Direct hardware access from userspace should only be used for testing, troubleshooting, and as a last resort when all other methods fail. See the *--rtc* option. **--epoch=**__year__:: -This option is required when using the *­--setepoch* function. The minimum _year_ value is 1900. The maximum is system dependent (*ULONG_MAX - 1*). +This option is required when using the *--setepoch* function. The minimum _year_ value is 1900. The maximum is system dependent (*ULONG_MAX - 1*). *-f*, **--rtc=**__filename__:: -Override *­hwclock*'s default rtc device file name. Otherwise it will use the first one found in this order: _/dev/rtc0_, _/dev/rtc_, _/dev/misc/rtc_. For *IA-64:* _/dev/efirtc_ _/dev/misc/efirtc_ +Override *hwclock*'s default rtc device file name. Otherwise it will use the first one found in this order: _/dev/rtc0_, _/dev/rtc_, _/dev/misc/rtc_. For *IA-64:* _/dev/efirtc_ _/dev/misc/efirtc_ *-l*, *--localtime*; *-u*, *--utc*:: Indicate which timescale the Hardware Clock is set to. + -The Hardware Clock may be configured to use either the UTC or the local timescale, but nothing in the clock itself says which alternative is being used. The *­--localtime* or *--utc* options give this information to the *­hwclock* command. If you specify the wrong one (or specify neither and take a wrong default), both setting and reading the Hardware Clock will be incorrect. +The Hardware Clock may be configured to use either the UTC or the local timescale, but nothing in the clock itself says which alternative is being used. The *--localtime* or *--utc* options give this information to the *hwclock* command. If you specify the wrong one (or specify neither and take a wrong default), both setting and reading the Hardware Clock will be incorrect. + -If you specify neither *--utc* nor *­--localtime* then the one last given with a set function (*--set*, *­--systohc*, or *­--adjust*), as recorded in _{ADJTIME_PATH}_, will be used. If the adjtime file doesn't exist, the default is UTC. +If you specify neither *--utc* nor *--localtime* then the one last given with a set function (*--set*, *--systohc*, or *--adjust*), as recorded in _{ADJTIME_PATH}_, will be used. If the adjtime file doesn't exist, the default is UTC. + Note: daylight saving time changes may be inconsistent when the Hardware Clock is kept in local time. See the discussion below, under *LOCAL vs UTC*. *--noadjfile*:: -Disable the facilities provided by _{ADJTIME_PATH}_. *­hwclock* will not read nor write to that file with this option. Either *--utc* or *­--localtime* must be specified when using this option. +Disable the facilities provided by _{ADJTIME_PATH}_. *hwclock* will not read nor write to that file with this option. Either *--utc* or *--localtime* must be specified when using this option. *--test*:: -Do not actually change anything on the system, that is, the Clocks or _{ADJTIME_PATH}_ (*­--verbose* is implicit with this option). +Do not actually change anything on the system, that is, the Clocks or _{ADJTIME_PATH}_ (*--verbose* is implicit with this option). *--update-drift*:: -Update the Hardware Clock's drift factor in _{ADJTIME_PATH}_. It can only be used with *--set* or *­--systohc*. +Update the Hardware Clock's drift factor in _{ADJTIME_PATH}_. It can only be used with *--set* or *--systohc*. + A minimum four hour period between settings is required. This is to avoid invalid calculations. The longer the period, the more precise the resulting drift factor will be. + -This option was added in v2.26, because it is typical for systems to call *­hwclock --systohc* at shutdown; with the old behaviour this would automatically (re)calculate the drift factor which caused several problems: +This option was added in v2.26, because it is typical for systems to call *hwclock --systohc* at shutdown; with the old behavior this would automatically (re)calculate the drift factor which caused several problems: + * When using NTP with an '11 minute mode' kernel the drift factor would be clobbered to near zero. * It would not allow the use of 'cold' drift correction. With most configurations using 'cold' drift will yield favorable results. Cold, means when the machine is turned off which can have a significant impact on the drift factor. * (Re)calculating drift factor on every shutdown delivers suboptimal results. For example, if ephemeral conditions cause the machine to be abnormally hot the drift factor calculation would be out of range. -* Significantly increased system shutdown times (as of v2.31 when not using *­--update-drift* the RTC is not read). +* Significantly increased system shutdown times (as of v2.31 when not using *--update-drift* the RTC is not read). -Having *­hwclock* calculate the drift factor is a good starting point, but for optimal results it will likely need to be adjusted by directly editing the _{ADJTIME_PATH}_ file. For most configurations once a machine's optimal drift factor is crafted it should not need to be changed. Therefore, the old behavior to automatically (re)calculate drift was changed and now requires this option to be used. See the discussion below, under *The Adjust Function*. +Having *hwclock* calculate the drift factor is a good starting point, but for optimal results it will likely need to be adjusted by directly editing the _{ADJTIME_PATH}_ file. For most configurations once a machine's optimal drift factor is crafted it should not need to be changed. Therefore, the old behavior to automatically (re)calculate drift was changed and now requires this option to be used. See the discussion below, under *The Adjust Function*. This option requires reading the Hardware Clock before setting it. If it cannot be read, then this option will cause the set functions to fail. This can happen, for example, if the Hardware Clock is corrupted by a power failure. In that case, the clock must first be set without this option. Despite it not working, the resulting drift correction factor would be invalid anyway. *-v*, *--verbose*:: -Display more details about what *­hwclock* is doing internally. +Display more details about what *hwclock* is doing internally. == NOTES @@ -177,7 +177,7 @@ There are two types of date-time clocks: On an ISA compatible system, this clock is specified as part of the ISA standard. A control program can read or set this clock only to a whole second, but it can also detect the edges of the 1 second clock ticks, so the clock actually has virtually infinite precision. -This clock is commonly called the hardware clock, the real time clock, the RTC, the BIOS clock, and the CMOS clock. Hardware Clock, in its capitalized form, was coined for use by *­hwclock*. The Linux kernel also refers to it as the persistent clock. +This clock is commonly called the hardware clock, the real time clock, the RTC, the BIOS clock, and the CMOS clock. Hardware Clock, in its capitalized form, was coined for use by *hwclock*. The Linux kernel also refers to it as the persistent clock. Some non-ISA systems have a few real time clocks with only one of them having its own power domain. A very low power external I2C or SPI clock chip might be used with a backup battery as the hardware clock to initialize a more functional integrated real-time clock which is used for most other purposes. @@ -185,37 +185,37 @@ Some non-ISA systems have a few real time clocks with only one of them having it The System Time is the time that matters. The Hardware Clock's basic purpose is to keep time when Linux is not running so that the System Clock can be initialized from it at boot. Note that in DOS, for which ISA was designed, the Hardware Clock is the only real time clock. -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. +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*. -*­hwclock* sets the kernel's timezone to the value indicated by *TZ* or _­/etc/localtime_ with the *­--hctosys* or *­--systz* functions. +*hwclock* sets the kernel's timezone to the value indicated by *TZ* or _/etc/localtime_ with the *--hctosys* or *--systz* functions. -The kernel's timezone value actually consists of two parts: 1) a field tz_minuteswest indicating how many minutes local time (not adjusted for DST) lags behind UTC, and 2) a field tz_dsttime indicating the type of Daylight Savings Time (DST) convention that is in effect in the locality at the present time. This second field is not used under Linux and is always zero. See also *­settimeofday*(2). +The kernel's timezone value actually consists of two parts: 1) a field tz_minuteswest indicating how many minutes local time (not adjusted for DST) lags behind UTC, and 2) a field tz_dsttime indicating the type of Daylight Savings Time (DST) convention that is in effect in the locality at the present time. This second field is not used under Linux and is always zero. See also *settimeofday*(2). === Hardware Clock Access Methods -*­hwclock* uses many different ways to get and set Hardware Clock values. The most normal way is to do I/O to the rtc device special file, which is presumed to be driven by the rtc device driver. Also, Linux systems using the rtc framework with udev, are capable of supporting multiple Hardware Clocks. This may bring about the need to override the default rtc device by specifying one with the *--rtc* option. +*hwclock* uses many different ways to get and set Hardware Clock values. The most normal way is to do I/O to the rtc device special file, which is presumed to be driven by the rtc device driver. Also, Linux systems using the rtc framework with udev, are capable of supporting multiple Hardware Clocks. This may bring about the need to override the default rtc device by specifying one with the *--rtc* option. However, this method is not always available as older systems do not have an rtc driver. On these systems, the method of accessing the Hardware Clock depends on the system hardware. -On an ISA compatible system, *­hwclock* can directly access the "CMOS memory" registers that constitute the clock, by doing I/O to Ports 0x70 and 0x71. It does this with actual I/O instructions and consequently can only do it if running with superuser effective userid. This method may be used by specifying the *­--directisa* option. +On an ISA compatible system, ­*hwclock* can directly access the "CMOS memory" registers that constitute the clock, by doing I/O to Ports 0x70 and 0x71. It does this with actual I/O instructions and consequently can only do it if running with superuser effective userid. This method may be used by specifying the *--directisa* option. -This is a really poor method of accessing the clock, for all the reasons that userspace programs are generally not supposed to do direct I/O and disable interrupts. *­hwclock* provides it for testing, troubleshooting, and because it may be the only method available on ISA systems which do not have a working rtc device driver. +This is a really poor method of accessing the clock, for all the reasons that userspace programs are generally not supposed to do direct I/O and disable interrupts. *hwclock* provides it for testing, troubleshooting, and because it may be the only method available on ISA systems which do not have a working rtc device driver. === The Adjust Function -The Hardware Clock is usually not very accurate. However, much of its inaccuracy is completely predictable - it gains or loses the same amount of time every day. This is called systematic drift. *­hwclock*'s *­--adjust* function lets you apply systematic drift corrections to the Hardware Clock. +The Hardware Clock is usually not very accurate. However, much of its inaccuracy is completely predictable - it gains or loses the same amount of time every day. This is called systematic drift. *hwclock*'s *--adjust* function lets you apply systematic drift corrections to the Hardware Clock. -It works like this: *­hwclock* keeps a file, _{ADJTIME_PATH}_, that keeps some historical information. This is called the adjtime file. +It works like this: *hwclock* keeps a file, _{ADJTIME_PATH}_, that keeps some historical information. This is called the adjtime file. -Suppose you start with no adjtime file. You issue a *­hwclock --set* command to set the Hardware Clock to the true current time. *­hwclock* creates the adjtime file and records in it the current time as the last time the clock was calibrated. Five days later, the clock has gained 10 seconds, so you issue a *­hwclock --set --update-drift* command to set it back 10 seconds. *­hwclock* updates the adjtime file to show the current time as the last time the clock was calibrated, and records 2 seconds per day as the systematic drift rate. 24 hours go by, and then you issue a *­hwclock --adjust* command. *­hwclock* consults the adjtime file and sees that the clock gains 2 seconds per day when left alone and that it has been left alone for exactly one day. So it subtracts 2 seconds from the Hardware Clock. It then records the current time as the last time the clock was adjusted. Another 24 hours go by and you issue another *­hwclock --adjust*. *­hwclock* does the same thing: subtracts 2 seconds and updates the adjtime file with the current time as the last time the clock was adjusted. +Suppose you start with no adjtime file. You issue a *hwclock --set* command to set the Hardware Clock to the true current time. *hwclock* creates the adjtime file and records in it the current time as the last time the clock was calibrated. Five days later, the clock has gained 10 seconds, so you issue a *hwclock --set --update-drift* command to set it back 10 seconds. *hwclock* updates the adjtime file to show the current time as the last time the clock was calibrated, and records 2 seconds per day as the systematic drift rate. 24 hours go by, and then you issue a *hwclock --adjust* command. *hwclock* consults the adjtime file and sees that the clock gains 2 seconds per day when left alone and that it has been left alone for exactly one day. So it subtracts 2 seconds from the Hardware Clock. It then records the current time as the last time the clock was adjusted. Another 24 hours go by and you issue another *hwclock --adjust*. *hwclock* does the same thing: subtracts 2 seconds and updates the adjtime file with the current time as the last time the clock was adjusted. -When you use the *­--update-drift* option with *--set* or *­--systohc*, the systematic drift rate is (re)calculated by comparing the fully drift corrected current Hardware Clock time with the new set time, from that it derives the 24 hour drift rate based on the last calibrated timestamp from the adjtime file. This updated drift factor is then saved in _{ADJTIME_PATH}_. +When you use the *--update-drift* option with *--set* or *--systohc*, the systematic drift rate is (re)calculated by comparing the fully drift corrected current Hardware Clock time with the new set time, from that it derives the 24 hour drift rate based on the last calibrated timestamp from the adjtime file. This updated drift factor is then saved in _{ADJTIME_PATH}_. -A small amount of error creeps in when the Hardware Clock is set, so *­--adjust* refrains from making any adjustment that is less than 1 second. Later on, when you request an adjustment again, the accumulated drift will be more than 1 second and *­--adjust* will make the adjustment including any fractional amount. +A small amount of error creeps in when the Hardware Clock is set, so *--adjust* refrains from making any adjustment that is less than 1 second. Later on, when you request an adjustment again, the accumulated drift will be more than 1 second and *--adjust* will make the adjustment including any fractional amount. -*­hwclock --hctosys* also uses the adjtime file data to compensate the value read from the Hardware Clock before using it to set the System Clock. It does not share the 1 second limitation of *­--adjust*, and will correct sub-second drift values immediately. It does not change the Hardware Clock time nor the adjtime file. This may eliminate the need to use *­--adjust*, unless something else on the system needs the Hardware Clock to be compensated. +*hwclock --hctosys* also uses the adjtime file data to compensate the value read from the Hardware Clock before using it to set the System Clock. It does not share the 1 second limitation of *--adjust*, and will correct sub-second drift values immediately. It does not change the Hardware Clock time nor the adjtime file. This may eliminate the need to use *--adjust*, unless something else on the system needs the Hardware Clock to be compensated. === The Adjtime File @@ -223,13 +223,13 @@ While named for its historical purpose of controlling adjustments only, it actua The format of the adjtime file is, in ASCII: -Line 1: Three numbers, separated by blanks: 1) the systematic drift rate in seconds per day, floating point decimal; 2) the resulting number of seconds since 1969 UTC of most recent adjustment or calibration, decimal integer; 3) zero (for compatibility with ­*clock*(8)) as a floating point decimal. +Line 1: Three numbers, separated by blanks: 1) the systematic drift rate in seconds per day, floating point decimal; 2) the resulting number of seconds since 1969 UTC of most recent adjustment or calibration, decimal integer; 3) zero (for compatibility with *clock*(8)) as a floating point decimal. Line 2: One number: the resulting number of seconds since 1969 UTC of most recent calibration. Zero if there has been no calibration yet or it is known that any previous calibration is moot (for example, because the Hardware Clock has been found, since that calibration, not to contain a valid time). This is a decimal integer. -Line 3: "UTC" or "LOCAL". Tells whether the Hardware Clock is set to Coordinated Universal Time or local time. You can always override this value with options on the *­hwclock* command line. +Line 3: "UTC" or "LOCAL". Tells whether the Hardware Clock is set to Coordinated Universal Time or local time. You can always override this value with options on the *hwclock* command line. -You can use an adjtime file that was previously used with the *­clock*(8) program with *­hwclock*. +You can use an adjtime file that was previously used with the *clock*(8) program with *hwclock*. === Automatic Hardware Clock Synchronization by the Kernel @@ -237,19 +237,19 @@ You should be aware of another way that the Hardware Clock is kept synchronized 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. +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'. === ISA Hardware Clock Century value -There is some sort of standard that defines CMOS memory Byte 50 on an ISA machine as an indicator of what century it is. *­hwclock* does not use or set that byte because there are some machines that don't define the byte that way, and it really isn't necessary anyway, since the year-of-century does a good job of implying which century it is. +There is some sort of standard that defines CMOS memory Byte 50 on an ISA machine as an indicator of what century it is. *hwclock* does not use or set that byte because there are some machines that don't define the byte that way, and it really isn't necessary anyway, since the year-of-century does a good job of implying which century it is. -If you have a bona fide use for a CMOS century byte, contact the *­hwclock* maintainer; an option may be appropriate. +If you have a bona fide use for a CMOS century byte, contact the *hwclock* maintainer; an option may be appropriate. Note that this section is only relevant when you are using the "direct ISA" method of accessing the Hardware Clock. ACPI provides a standard way to access century values, when they are supported by the hardware. @@ -261,8 +261,8 @@ This discussion is based on the following conditions: * Nothing is running that alters the date-time clocks, such as NTP daemon or a cron job." * The system timezone is configured for the correct local time. See below, under *POSIX vs 'RIGHT'*. -* Early during startup the following are called, in this order: *­adjtimex --tick* _value_ *--frequency* _value_ *­hwclock --hctosys* -* During shutdown the following is called: *­hwclock --systohc* +* Early during startup the following are called, in this order: *adjtimex --tick* _value_ *--frequency* _value_ *hwclock --hctosys* +* During shutdown the following is called: *hwclock --systohc* *** Systems without *adjtimex* may use *ntptime*. @@ -270,13 +270,13 @@ Whether maintaining precision time with NTP daemon or not, it makes sense to con The first step in making that happen is having a clear understanding of the big picture. There are two completely separate hardware devices running at their own speed and drifting away from the 'correct' time at their own rates. The methods and software for drift correction are different for each of them. However, most systems are configured to exchange values between these two clocks at startup and shutdown. Now the individual device's time keeping errors are transferred back and forth between each other. Attempt to configure drift correction for only one of them, and the other's drift will be overlaid upon it. -This problem can be avoided when configuring drift correction for the System Clock by simply not shutting down the machine. This, plus the fact that all of *­hwclock*'s precision (including calculating drift factors) depends upon the System Clock's rate being correct, means that configuration of the System Clock should be done first. +This problem can be avoided when configuring drift correction for the System Clock by simply not shutting down the machine. This, plus the fact that all of *hwclock*'s precision (including calculating drift factors) depends upon the System Clock's rate being correct, means that configuration of the System Clock should be done first. -The System Clock drift is corrected with the *­adjtimex*(8) command's *--tick* and *­--frequency* options. These two work together: tick is the coarse adjustment and frequency is the fine adjustment. (For systems that do not have an *­adjtimex* package, *­ntptime -f* _ppm_ may be used instead.) +The System Clock drift is corrected with the *adjtimex*(8) command's *--tick* and *--frequency* options. These two work together: tick is the coarse adjustment and frequency is the fine adjustment. (For systems that do not have an *adjtimex* package, *ntptime -f* _ppm_ may be used instead.) -Some Linux distributions attempt to automatically calculate the System Clock drift with *­adjtimex*'s compare operation. Trying to correct one drifting clock by using another drifting clock as a reference is akin to a dog trying to catch its own tail. Success may happen eventually, but great effort and frustration will likely precede it. This automation may yield an improvement over no configuration, but expecting optimum results would be in error. A better choice for manual configuration would be *­adjtimex*'s *--log* options. +Some Linux distributions attempt to automatically calculate the System Clock drift with *adjtimex*'s compare operation. Trying to correct one drifting clock by using another drifting clock as a reference is akin to a dog trying to catch its own tail. Success may happen eventually, but great effort and frustration will likely precede it. This automation may yield an improvement over no configuration, but expecting optimum results would be in error. A better choice for manual configuration would be *adjtimex*'s *--log* options. -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. +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. @@ -302,11 +302,11 @@ Let an extended period pass without changing the Hardware Clock. Start the system. 6:: -Immediately use *hwclock* to set the correct time, adding the *­--update-drift* option. +Immediately use *hwclock* to set the correct time, adding the *--update-drift* option. -Note: if step 6 uses *­--systohc*, then the System Clock must be set correctly (step 6a) just before doing so. +Note: if step 6 uses *--systohc*, then the System Clock must be set correctly (step 6a) just before doing so. -Having *hwclock* calculate the drift factor is a good starting point, but for optimal results it will likely need to be adjusted by directly editing the _{ADJTIME_PATH}_ file. Continue to test and refine the drift factor until the Hardware Clock is corrected properly at startup. To check this, first make sure that the System Time is correct before shutdown and then use *­sntp*, or *­date -Ins* and a precision timepiece, immediately after startup. +Having *hwclock* calculate the drift factor is a good starting point, but for optimal results it will likely need to be adjusted by directly editing the _{ADJTIME_PATH}_ file. Continue to test and refine the drift factor until the Hardware Clock is corrected properly at startup. To check this, first make sure that the System Time is correct before shutdown and then use *sntp*, or *date -Ins* and a precision timepiece, immediately after startup. === LOCAL vs UTC @@ -317,7 +317,7 @@ Keeping the Hardware Clock in a local timescale causes inconsistent daylight sav The Hardware Clock on an ISA compatible system keeps only a date and time, it has no concept of timezone nor daylight saving. Therefore, when *hwclock* is told that it is in local time, it assumes it is in the 'correct' local time and makes no adjustments to the time read from it. -Linux handles daylight saving time changes transparently only when the Hardware Clock is kept in the UTC timescale. Doing so is made easy for system administrators as *­hwclock* uses local time for its output and as the argument to the *­--date* option. +Linux handles daylight saving time changes transparently only when the Hardware Clock is kept in the UTC timescale. Doing so is made easy for system administrators as *hwclock* uses local time for its output and as the argument to the *--date* option. POSIX systems, like Linux, are designed to have the System Clock operate in the UTC timescale. The Hardware Clock's purpose is to initialize the System Clock, so also keeping it in UTC makes sense. @@ -330,11 +330,11 @@ A discussion on date-time configuration would be incomplete without addressing t //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. -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_ -Unfortunately, some Linux distributions are changing it back to the old tree structure in their packages. So the problem of system administrators reaching into the 'right' subdirectory persists. This causes the system timezone to be configured to include leap seconds while the zoneinfo database is still configured to exclude them. Then when an application such as a World Clock needs the South_Pole timezone file; or an email MTA, or *hwclock* needs the UTC timezone file; they fetch it from the root of _­/usr/share/zoneinfo_ , because that is what they are supposed to do. Those files exclude leap seconds, but the System Clock now includes them, causing an incorrect time conversion. +Unfortunately, some Linux distributions are changing it back to the old tree structure in their packages. So the problem of system administrators reaching into the 'right' subdirectory persists. This causes the system timezone to be configured to include leap seconds while the zoneinfo database is still configured to exclude them. Then when an application such as a World Clock needs the South_Pole timezone file; or an email MTA, or *hwclock* needs the UTC timezone file; they fetch it from the root of _/usr/share/zoneinfo_ , because that is what they are supposed to do. Those files exclude leap seconds, but the System Clock now includes them, causing an incorrect time conversion. Attempting to mix and match files from these separate databases will not work, because they each require the System Clock to use a different timescale. The zoneinfo database must be configured to use either posix or 'right', as described above, or by assigning a database path to the _TZDIR_ environment variable. @@ -380,7 +380,7 @@ Device files *hwclock* may try for Hardware Clock access: _/dev/rtc0_ _/dev/rtc_ == AUTHORS -Written by mailto:bryanh@giraffe-data.com[Bryan Henderson], September 1996, based on work done on the *­clock*(8) program by Charles Hedrick, Rob Hooft, and Harald Koenig. See the source code for complete history and credits. +Written by mailto:bryanh@giraffe-data.com[Bryan Henderson], September 1996, based on work done on the *clock*(8) program by Charles Hedrick, Rob Hooft, and Harald Koenig. See the source code for complete history and credits. include::../man-common/bugreports.adoc[]