Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Ok, I'm having touble with my clock losing 5 hours during the boot process. Here's what I see in:
>>>>Here's the reboot. Before it booted back up I checked BIOS and the time was still correct, 18:45, however, after reboot I lost 5 hours, 18:45 to 13:45.
Apr 27 18:45:06 localhost kernel: Kernel logging (proc) stopped.
Apr 27 18:45:06 localhost kernel: Kernel log daemon terminating.
Apr 27 18:45:07 localhost syslog: klogd shutdown succeeded
Apr 27 18:45:07 localhost exiting on signal 15
Apr 27 13:47:06 localhost syslogd 1.4.1: restart.
Apr 27 13:47:06 localhost syslog: syslogd startup succeeded
....then the time magically changes back to the correct time here after autofs, maybe in rc.sysinit
Apr 27 13:47:07 localhost kernel: eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.
Apr 27 13:47:07 localhost autofs: automount startup succeeded
Apr 27 18:46:34 localhost rc.sysinit: Mounting proc filesystem: succeeded
Apr 27 18:46:34 localhost rc.sysinit: Unmounting initrd: succeeded
Apr 27 18:46:34 localhost sysctl: net.ipv4.ip_forward = 0
Apr 27 18:46:34 localhost sysctl: net.ipv4.conf.default.rp_filter = 1
Apr 27 18:46:34 localhost sysctl: kernel.sysrq = 0
Apr 27 18:46:34 localhost sysctl: kernel.core_uses_pid = 1
Apr 27 18:46:34 localhost rc.sysinit: Configuring kernel parameters: succeeded
Apr 27 18:46:34 localhost date: Sun Apr 27 18:46:32 UTC 2003
Apr 27 18:46:34 localhost rc.sysinit: Setting clock : Sun Apr 27 18:46:32 UTC 2003 succeeded
Apr 27 18:46:34 localhost rc.sysinit: Loading default keymap succeeded
....then a few lines later, apparently in rc.sysinit, the 5 hours get's lopped off again...
Apr 27 18:46:41 localhost fsck: /usr/local: clean, 1715/513024 files, 247948/1024135 blocks
Apr 27 18:46:41 localhost fsck: /var: clean, 5772/384000 files, 73446/767095 blocks
Apr 27 18:46:41 localhost rc.sysinit: Checking filesystems succeeded
Apr 27 13:46:41 localhost rc.sysinit: Mounting local filesystems: succeeded
Apr 27 13:46:41 localhost rc.sysinit: Enabling local filesystem quotas: succeeded
Apr 27 13:46:42 localhost rc.sysinit: Enabling swap space: succeeded
Apr 27 13:46:44 localhost init: Entering runlevel: 5
I looked in rc.sysinit, but don't really know what I'm looking for in there.
There are several instances of 'time' and 'clock' in there.
Also, I am still getting the weird phenomenon where pressing the OK button after running redhat-config-date causes the screensaver to start up. Also, after running redhat-config-date, I see this:
Apr 27 13:52:19 localhost su(pam_unix): session opened for user root by (uid=500)
Apr 27 14:05:30 localhost userhelper: pam_timestamp: timestamp file `/var/run/sudo/bsl1/unknown:root' is too old,
disallowing access to redhat-config-date for UID 500
Apr 27 14:05:44 localhost ntpd: ntpd shutdown failed
Apr 27 19:15:15 localhost kernel: eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.
I'm not running ntpd. And, the time DOES change.
And, whether I select to use UTC or not I get the same result and if I select to use UTC, when I reboot and come back in, the UTC selection is no longer selected.