| Summary: | clock on orion.eclipse.org is way off | ||
|---|---|---|---|
| Product: | Community | Reporter: | Boris Bokowski <bokowski> |
| Component: | vservers | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
|
Description
Boris Bokowski
I don't want to just fix this once - shouldn't the time be synchronized using a time server? You won't be able to change the hardware clock; virtual servers should be pulling their clock from the hypervisor. Seems the host server is not syncing properly. I will check it. I had encountered this before with other vservers -- for some reason, the timezone is computed twice, and short of setting an incorrect time on the host, I have a hard time getting it to work. Easiest solution is to tell the domU to use an independent (from the host) clock: echo 1 > /proc/sys/xen/independent_wallclock ... and to sync with an external source. rdate -s build.eclipse.org I've added this to a cron, so your clock should now always be in sync with build.eclipse.org's (which is synced from an external source). |