aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Gundersen <teg@jklm.no>2012-07-21 12:05:11 (GMT)
committerTom Gundersen <teg@jklm.no>2012-07-21 12:05:11 (GMT)
commit383fe909a382746afe47b5aaf4b5265e22474ea7 (patch)
tree3e41dccace172a195454cddb1a4709e61aacd6b4
parentae28554e561517815c07330b2b7d5ee5de2f6dc7 (diff)
downloadinitscripts-383fe909a382746afe47b5aaf4b5265e22474ea7.tar.xz
man: typo
Signed-off-by: Tom Gundersen <teg@jklm.no>
-rw-r--r--rc.conf.5.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/rc.conf.5.txt b/rc.conf.5.txt
index ad5af7d..a413ba7 100644
--- a/rc.conf.5.txt
+++ b/rc.conf.5.txt
@@ -138,10 +138,10 @@ to the correct zoneinfo file. Possible time zones are the relative path to a zon
from the directory /usr/share/zoneinfo. For example, a German time zone would be Europe/Berlin,
which refers to the file /usr/share/zoneinfo/Europe/Berlin.
-It is recommended to leave this unset, and rather update maintain the /etc/localtime symlink manually,
-or via third party tools. The reason for this is to avoid the symlink and the TIMEZONE variable to
-be out of sync, as they are only synchronized at boot. Also, most third-party applications that could
-maintain /etc/localtime do not know to also write to /etc/rc.conf.
+It is recommended to leave this unset, and rather maintain the /etc/localtime symlink manually, or via
+third party tools. The reason for this is to avoid the symlink and the TIMEZONE variable to be out of sync,
+as they are only synchronized at boot. Also, most third-party applications that could maintain
+/etc/localtime do not know to also write to /etc/rc.conf.
TIMEZONE="Europe/Berlin"