UbuntuThis forum is for the discussion of Ubuntu Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm having lots of trouble trying to figure out what is wrong with my Ubuntu clock.
I installed 13.04 on my server using VMWare (maybe it has something to do with that.)
After rebooting the system, the clock is always 2h ahead. After updating the ntp service, the clock sets itself back to the proper time, but after rebooting the system it is off again.
The timezone is set to CEST, but even the CEST is 2h off after a reboot. It feels like the system is applying the daylight saving time twice after the reboot.
Distribution: Debian Sid AMD64, Raspbian Wheezy, Slackware Current AMD64, various VMs
This is a guess because I don't use VMWare (only VirtualBox) but do you have the guest set to think that "system time is UTC"? It occurs that the host OS might be passing on non-UTC time so you might want to change that?
Apologies if I'm barking up the wrong tree but I'd rather post and be wrong than hold back if it works.
I also don't use VmWare, it seems it deals with time differently
taken from page 22 of previously linked pdf
Because guest operating systems generally get their time from the virtual CMOS TOD clock when they are powered on, you must set this device to your fictitious time if you want the time to persist across guest operating system restarts.
If you want to start a guest operating system with the same time on every startup, use the rtc.startTime option described in “Virtual CMOS RTC” on page 10.
If, instead, you want the guest operating system to have a constant offset from real time as maintained by the host, you can use the rtc.diffFromUTC option, or simply set the CMOS TOD clock from the virtual machine’s BIOS setup screen or from within the guest operating system.
In Microsoft Windows, setting the system time automatically updates the CMOS clock.
In Linux, you can use the /sbin/hwclock program to set the CMOS clock. Alternatively, because most Linux distributions are configured to copy the system time into the CMOS clock during system shutdown, you can simply set the system time and shut down the guest operating system before restarting it again.
all seems a bit confusing , but It looks like The VMWare guest has it's own BIOS settings.. It could be that it pulled local time from the host during initial setup, and due to some quirk it is now out of step
so a variation on post #2
What time does your VmWare Guest's BIOS think it is?
Last edited by Firerat; 08-03-2013 at 03:56 PM.
Reason: cut'n'paste formating fail