Package: libc6 Version: 2.3.2.ds1-21 Severity: minor Tags: patch
Found some typos in '/usr/share/man/man8/tzconfig.8.gz', see attached '.diff'. Hope this helps... -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.9-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Versions of packages libc6 depends on: ii libdb1-compat 2.1.3-7 The Berkeley database routines [gl -- no debconf information
--- - 2005-04-21 04:50:55.416858000 -0400 +++ /tmp/tzconfig8.gz.26266 2005-04-21 04:50:55.411774037 -0400 @@ -34,7 +34,7 @@ necessary to make your system behave nicely when your location uses Daylight Savings Time. A valid system time together with the correct local time zone will give you best performance -and highest reliablility. It is especially important in a network environment, where even small +and highest reliability. It is especially important in a network environment, where even small time differences can make a mirror refetch a whole ftp site, or where time stamps on external file systems are used. @@ -50,7 +50,7 @@ .B tzconfig will try to change the timezone for you. See the .B Internals -section below for technical details. You must have root privilegies to actually change +section below for technical details. You must have root privileges to actually change anything. Please use .BR tzselect (1) as a user space command to just look at the timezones. It will print the local time in any @@ -69,7 +69,7 @@ which indicates that the hardware clock is set to UTC, or it contains the line .BR UTC=no , which declares the hardware clock is set to Local Time. If these setting are correct, and the hardware -clock is truely set as indicated, then configuring the proper timezone for the machine +clock is truly set as indicated, then configuring the proper timezone for the machine will cause the proper date and time to be displayed. If these are not set correctly, the the reported time will be quite incorrect. See .BR hwclock (8)
