We have actually changed the system time on our year 2000 test server back
and forth to test different scenarios and what I found out is that when you
move forward by more than a day, cron and at get a little confused and jobs
that you did not expect will to get fired off. Moving backwards is a lot
worse, if you have any applications/jobs that depend on file timestamps then
the effect of this change is unpredictable. If you run a database server
then you ran the risk of corrupting all your database (specially Oracle
If you plan to roll the clock back for a test then make sure you have a good
backup, bring down all applications and databases, stop cron, change the
time, restart cron. You will probably have to recreate and reload your
databases from backup ......
>There's a ongoing feud happening in my organization and would like to
>present it to this group for analysis. The feud is the issue of rolling
>back the dates in HP-UX. As I believe that it's necessary to roll back the
>clock on the HP-UX machines we have on 10.20.43, I also think there is
>considerable damage that could occurr when you come back to reality.
>like file datestamping, etc. What's everyone's take on this???
>Data Center Manager
>Community Health Care, Inc.
> > T h e T r u t h i s O u t T h e r e <