bug-sh-utils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: incorrect DAte---Y2K issue


From: Bob Proulx
Subject: Re: incorrect DAte---Y2K issue
Date: Sat, 22 Mar 2003 17:51:12 -0700
User-agent: Mutt/1.3.28i

Please follow up to the list and not to me privately unless it is
personal.

address@hidden wrote:
> I was running KDE 3.0 and was trying to update the version of python so 
> that it could support Tkinter or X Programs correctly.I was updating to 
> 2.2.1 I believe.The ./configure option (or make command, i forget which) 
> sent out a 'Software date is too far into the future' error and failed to 
> compile.Sure enough, it was the year 1903 at exactly 12am.I used 'date  
> 3/12/03' (I believe) to reset the date, but how do I reset the time form 
> the shell?

I don't understand your question.  You would use date from the shell
to set the date.  With no arguments it prints the date.  With
arguments then it can set the date.  Read the info documentation for
details.

  info date

Example:

  date 032217462003  # set the date to March 22 5:46pm 2003

> It would be easier than logging into root under X just to change 
> the time everytime I restart the machine.

If you have a network connection, even sometimes, then the standard is
to use NTP to set the time.  Use ntpdate at boot time to set the time
directly.  Then start ntpd which keeps the time correctly.  If you
don't have a network connection then you have to rely upon the onboard
clock.  The battery on most of today's onboard clocks last about five
years and then need to be replaced or they don't keep time.

> Mac OS just blindly complies with whatever date Yellow Dog Linux
> (2.3) sets.As for version information, I don't have access to the
> machine anymore.I do think i'm running above 2.0.11, though.

I guess if you don't have access any more then none of this really
matters at all?

Bob




reply via email to

[Prev in Thread] Current Thread [Next in Thread]