X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C839F1.42594538@onstor-exch02.onstor.net>; Sat, 8 Dec 2007 15:22:54 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C839F1.42594538"
References: <BB375AF679D4A34E9CA8DFA650E2B04E056C9207@onstor-exch02.onstor.net> <20071207190914.644299ce@ripper.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: Did the system clock go haywire on bobcat linux?
Date: Sat, 8 Dec 2007 15:19:05 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E042F0000@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Did the system clock go haywire on bobcat linux?
Thread-Index: Acg5R7dZshdWM7+TTeaaUtcYedRPYgAqQLVd
From: "Larry Scheer" <larry.scheer@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C839F1.42594538
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Did that twice. After setting the clock I did a reboot and the time went =
to a  day in 2023. Before that, I had set the date to the correct time =
and after running several days I did a reboot and the time was 2018.

I don't think normal behavior. Shouldn't the date presist between =
reboots?

Larry

-----Original Message-----
From: Andy Sharp
Sent: Fri 12/7/2007 7:09 PM
To: Larry Scheer
Subject: Re: Did the system clock go haywire on bobcat linux?
=20
On Fri, 7 Dec 2007 18:21:00 -0800 "Larry Scheer"
<larry.scheer@onstor.com> wrote:

> Andy,
>    I thought you had the system clock working on Linux. Was I mistaken
> or is it now busted.
>=20
> When I reboot I now see time way in the future: =20
>=20
> eng216:~# date
> Wed Dec 20 02:04:31 PST 2023
>=20
> Later,
>=20
> Larry

Set the correct date, or start ntp, and then reboot.  Should work.

a


------_=_NextPart_001_01C839F1.42594538
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>RE: Did the system clock go haywire on bobcat linux?</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Did that twice. After setting the clock I did a reboot =
and the time went to a&nbsp; day in 2023. Before that, I had set the =
date to the correct time and after running several days I did a reboot =
and the time was 2018.<BR>
<BR>
I don't think normal behavior. Shouldn't the date presist between =
reboots?<BR>
<BR>
Larry<BR>
<BR>
-----Original Message-----<BR>
From: Andy Sharp<BR>
Sent: Fri 12/7/2007 7:09 PM<BR>
To: Larry Scheer<BR>
Subject: Re: Did the system clock go haywire on bobcat linux?<BR>
<BR>
On Fri, 7 Dec 2007 18:21:00 -0800 &quot;Larry Scheer&quot;<BR>
&lt;larry.scheer@onstor.com&gt; wrote:<BR>
<BR>
&gt; Andy,<BR>
&gt;&nbsp;&nbsp;&nbsp; I thought you had the system clock working on =
Linux. Was I mistaken<BR>
&gt; or is it now busted.<BR>
&gt;<BR>
&gt; When I reboot I now see time way in the future:&nbsp;<BR>
&gt;<BR>
&gt; eng216:~# date<BR>
&gt; Wed Dec 20 02:04:31 PST 2023<BR>
&gt;<BR>
&gt; Later,<BR>
&gt;<BR>
&gt; Larry<BR>
<BR>
Set the correct date, or start ntp, and then reboot.&nbsp; Should =
work.<BR>
<BR>
a<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C839F1.42594538--
