Summary: | setting of timezone could be in the wrong place | ||
---|---|---|---|
Product: | [OLD] Docs-user | Reporter: | Steve B. <rshadow> |
Component: | Gentoo Linux x86 Installation Guide | Assignee: | Sven Vermeulen (RETIRED) <swift> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | docs-team |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Steve B.
2003-12-11 00:31:28 UTC
Setting the timezone doesn't alter the time written down when a file is created/modified. In other words, clock skews aren't due to a changed /etc/localtime. Clock skews are when your system clock is really wrong (lagging behind). You didn't run "date -s" or "ntpdate" previously after emerge system'ing, did you? Not that I can recall. I recently did a new install and set the timezone according to the docs and no problems. Perhaps something else was wack with my system the first time I did a install. I'll mark this one as WORKSFORME then. If you ever get into troubles regarding times and dates, take a look at net-misc/ntp. You can set it so it keeps your clock synchronised with an online ntp-server. Such a setup provides you with a very correct timesetting. In production environments, where correct time synchronisation is important (for instance for logfiles), ntp is a de facto standard. |