Re: Date Problems...
on 7/18/01 11:34 AM, Leonard Leblanc at [EMAIL PROTECTED] wrote: Hey All, This is probably going to be an easy question for most of you, but I can't seem to get a grasp on what the problem is... # hwclock Tue Jul 17 22:38:11 2001 -0.044470 seconds # hwclock --localtime Wed Jul 18 03:37:34 2001 -0.558978 seconds # uname -a Sat Nov 18 18:47:15 EST 2000 This one completely has me baffled and I can't seem to find any information on it. Any help is greatly appreciated. This may be a problem due to timezone settings - but 'm quite SURE that you get it wrong - use ntpdate
RE: Date Problems...
The #uname -a command also gives you the version and date of compilation (installation ?) eg one our old machines gives Linux router1 2.0.36 #1 Thu Sep 2 09:28:09 EST 1999 i686 unknown one of the newer gives Linux router2 2.2.17 #1 Sun Jun 25 09:24:41 EST 2000 i586 unknown I often use the command 'hwclock --systohc' to set the clock to the system time after a date command. Ian -Original Message- From: Ari Pollak [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 18, 2001 1:53 PM To: debian-user@lists.debian.org Subject: Re: Date Problems... First of all, I don't think that's the real 'uname -a' output. uname -a has more than just the date. Second of all, the hardware clock and the system (Linux) clock are different. if you type the command 'date', you'll probably get the same output as uname. To transfer the hardware clock to the system clock, use the command 'hwclock --hctosys'. On Tue, Jul 17, 2001 at 10:34:55PM -0500, Leonard Leblanc wrote: Hey All, This is probably going to be an easy question for most of you, but I can't seem to get a grasp on what the problem is... # hwclock Tue Jul 17 22:38:11 2001 -0.044470 seconds # hwclock --localtime Wed Jul 18 03:37:34 2001 -0.558978 seconds # uname -a Sat Nov 18 18:47:15 EST 2000 This one completely has me baffled and I can't seem to find any information on it. Any help is greatly appreciated. -- ___ ___ / _ | / _ \ Ari Pollak - [EMAIL PROTECTED] - www.aripollak.com / __ |/ ___/ /_/ |_/_/ A man needs a good memory after he has lied. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Date Problems...
Hey All, This is probably going to be an easy question for most of you, but I can't seem to get a grasp on what the problem is... # hwclock Tue Jul 17 22:38:11 2001 -0.044470 seconds # hwclock --localtime Wed Jul 18 03:37:34 2001 -0.558978 seconds # uname -a Sat Nov 18 18:47:15 EST 2000 This one completely has me baffled and I can't seem to find any information on it. Any help is greatly appreciated. -- Leonard Leblanc Vice President - Technology www.emergeknowledge.com
Re: Date Problems...
First of all, I don't think that's the real 'uname -a' output. uname -a has more than just the date. Second of all, the hardware clock and the system (Linux) clock are different. if you type the command 'date', you'll probably get the same output as uname. To transfer the hardware clock to the system clock, use the command 'hwclock --hctosys'. On Tue, Jul 17, 2001 at 10:34:55PM -0500, Leonard Leblanc wrote: Hey All, This is probably going to be an easy question for most of you, but I can't seem to get a grasp on what the problem is... # hwclock Tue Jul 17 22:38:11 2001 -0.044470 seconds # hwclock --localtime Wed Jul 18 03:37:34 2001 -0.558978 seconds # uname -a Sat Nov 18 18:47:15 EST 2000 This one completely has me baffled and I can't seem to find any information on it. Any help is greatly appreciated. -- ___ ___ / _ | / _ \ Ari Pollak - [EMAIL PROTECTED] - www.aripollak.com / __ |/ ___/ /_/ |_/_/ A man needs a good memory after he has lied.
Re: time/date problems
David Wright wrote: Quoting Ed Cogburn ([EMAIL PROTECTED]): This isn't exactly true. You can keep your hardware clock on local, and you can tell Linux to use local time (keeping it from messing around). Linux does not set my hardware clock to GMT at shutdown, it sets it with local time, which is what I want because I use ntpdate to update date/time every time I bring up a net connection. Sure, setting up GMT is the Unix(TM) thing to do, but why bother? It knows my timezone, handles daylight savings automatically, and it stays ^^ How does it do this? If it changes the hardware clock, I call this messing around. The trouble is, the Broken OS also messes around and suddenly you've jumped two hours instead of one.. (If it doesn't change the hardware clock, then it's not running local time, is it.) I'll look at this when I have some time, but when my machine shuts down I see a message saying hardware clock being updated or something like that. This behavior may be part of the ntpdate package, I didn't consider that possibility. -- It is dangerous to be right when the government is wrong. - Voltaire Ed C.
Re: time/date problems
On Sat, Feb 12, 2000 at 11:42:26AM +, Ed Cogburn wrote: I'll look at this when I have some time, but when my machine shuts down I see a message saying hardware clock being updated or something like that. This behavior may be part of the ntpdate package, I didn't consider that possibility. no that is the hwclock package doing that, and it does it regardless of whether you keep the hardware clock set to GMT or not, all that setting changes is whether hwclock updates the RTC to current GMT time or current local time. it has nothing to do with DST. -- Ethan Benson
Re: time/date problems
On Fri, Feb 11, 2000 at 09:23:36AM +1300, [EMAIL PROTECTED] wrote: Hi i am running slink 2.1 with kernel 2.0.36 on a Dell Power Edge 2100 and i am having problems with the time. Basically what happens is that once i set up the correct date/time in BIOS...when i load up linux the time date get's corrupted. you should not tamper with the hardware clock. eg. real date time is 11-Feb 09:36. When i load linux up it shows 12-Feb 04:28. usually linux (and every other unix i am aware of) keeps the hardware clock set to UTC (GMT) not local time like broken OSes. When i go back into BIOS it shows 11-Feb 15:31 what the hell is going on? :) your hardware clock is reset at shutdown by linux, its set to the current time in GMT, as known by linux. i have tested the bios clock by setting it up correctly and booting with a windows boot disk and it keeps the correct date/time. I can only surmise that it is the linux software that is corrupting my date/clock. its not corrupted, windows is broken and keeps the hardware clock in local time, linux/un*x does not, it keeps it in GMT. Any thoughts would be appreciated. if you must have correct time in windows you will have to reconfigure linux to keep time in local time instead of GMT. personally i just set the broken OS's (in my case MacOS) timezone to London, England (GMT) so it won't corrupt the hardware clock, then linux has correct time and hardware clock is also correct (in GMT as it should be) I never do anything in my broken OS that depends on the time anymore so its not a problem, i just use my wristwatch when i need to know what time it is ;-) -- Ethan Benson
time/date problems solved
i am running slink 2.1 with kernel 2.0.36 on a Dell Power Edge 2100 and i am having problems with the time. Basically what happens is that once i set up the correct date/time in BIOS...when i load up linux the time date get's corrupted. Hiya problem solved... i had to set GMT= in the /etc/default/rcS file to turn off the GMT feature... thanx to Ethan Benson and all that replied.
Re: time/date problems
On Fri, Feb 11, 2000 at 02:32:16AM -0900, Ethan Benson wrote: I don't think Linux will adjust for Daylight savings unless the hardware clock is in GMT, otherwise it would just end up being a race condition with the broken OS also installed (why else would you have your HW clock set to local time?) (at least iirc) Yes, Linux will update for DST. i finally decided to set my hardware clock to GMT to stop that, because it seemed every third time i booted windows it'd change the clock for DST, meaning i'd have to reset it since Linux had taken care of it. (yes, i boot windows that rarely) -- finger for GPG public key. 8 Jan 2000 - Old email addresses removed from key, new added pgpKV8ULBu4BF.pgp Description: PGP signature
time/date problems
Hi i am running slink 2.1 with kernel 2.0.36 on a Dell Power Edge 2100 and i am having problems with the time. Basically what happens is that once i set up the correct date/time in BIOS...when i load up linux the time date get's corrupted. eg. real date time is 11-Feb 09:36. When i load linux up it shows 12-Feb 04:28. When i go back into BIOS it shows 11-Feb 15:31 what the hell is going on? :) i have tested the bios clock by setting it up correctly and booting with a windows boot disk and it keeps the correct date/time. I can only surmise that it is the linux software that is corrupting my date/clock. Any thoughts would be appreciated.
Re: Date Problems and more
First off thanks to everyone who replied to my first problem. I was actually trying to just change the hour and nothing else using the 'date' command. Duh! Ok my brother is wanting to install Debian on his home machine, after I've been telling him how great the support is from you guys and how cool and efficient the Linux OS is. He has a old i386 with a 1mg+ HD that his BIOS and Windows doesn't see all of. Well we ran a floppy I prepared from my machine and we quickly had Debian up and running. I tried to just use the part of the drive that Windows doesn't see and everything seemed Ok from the Linux side with fdisk. However from the BIOS and Windows the Partition Table was messed up in such a way as to make Windows unbootable. I had to run a rescue disk and do a fdisk /mbr to get it back to normal. I've been following this list for a while and someone somewhere mentioned that you could write the root partition to the lower part of the HD and make it work OK. If so can you do this without screwing up his existing Windows partition? Also his computer has a Sony cdrom (CDU-33A) which is supported by the kernal already. But the installation program wouldn't recognize it. I've got the hamm dist. Any one have any ideas? I don't think he had any problems with the cdrom from Windows although I didn't check it out while I was there. TIA Duane BTW I converted from Slack to Debian after I tried to get support from them and while doing a search for some file I thought was broken ran accross this mailing list and saw a lot of my questions answered just by reading the archives. Just one thing though. is there a way to search just the mailing list archives for answers to specific problems? That would sure be a BIG timesaver for a lot of people.
Re: Date Problems
Subject: Date Problems Date: Wed, Jul 07, 2004 at 01:10:08AM -0500 In reply to:D Richards Quoting D Richards([EMAIL PROTECTED]): Hello I've just reinstalled debian hamm on my new 2.5 gig HD with no problems. Except I can't seem to understand the correct syntax for setting my system date and time using 'date'. Can anyone give me an example with an explanation TIA Duane Richards man date, man clock, man hwclock. Clock-HOWTO -- Real Programmers don't write in PL/I. PL/I is for programmers who can't decide whether to write in COBOL or FORTRAN. ___ Wayne T. Topa [EMAIL PROTECTED]
Re: Date Problems
On Wed, Jul 07, 2004 at 01:10:08AM -0500, D Richards [EMAIL PROTECTED] wrote: I've just reinstalled debian hamm on my new 2.5 gig HD with no problems. Except I can't seem to understand the correct syntax for setting my system date and time using 'date'. Can anyone give me an example with an explanation TIA Duane Richards The GNU date command is pretty smart. You can use most common date formats with the -s option. For example, date -s 'Mar 1 8:55am 1999' is the same as date -s '3/1/1999 8:55:00'. -- /---\ | Eric Gillespie, Jr.| [EMAIL PROTECTED] | |*| | Between depriving a man of one hour from his life and| | depriving him of his life there exists only a difference | | of degree. | | --Emperor Paul Muad'dib (Frank Herbert's Dune Messiah) | \---/
Date Problems
Hello I've just reinstalled debian hamm on my new 2.5 gig HD with no problems. Except I can't seem to understand the correct syntax for setting my system date and time using 'date'. Can anyone give me an example with an explanation TIA Duane Richards
Re: Date Problems
On Wed, Jul 07, 2004 at 01:10:08AM -0500, D Richards wrote: Hello I've just reinstalled debian hamm on my new 2.5 gig HD with no problems. Except I can't seem to understand the correct syntax for setting my system date and time using 'date'. Can anyone give me an example with an explanation TIA Duane Richards -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null This works for me: date -s Sun Feb 28 15:38:13 CST 1999 You were probably missing the quotes. -- Stephen Pitts [EMAIL PROTECTED] webmaster - http://www.mschess.org
