HP3000-L Archives

November 1999, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Mon, 8 Nov 1999 10:54:48 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (34 lines)
Re:

> I may have had a bad dream one day awhile ago, but I was certain that I read
> in this group a post about setting the HP3000 date forward and then
> returning it.

A number of posts :)

> I searched the archives and my keepers without finding anything. I remember
> this post identifying a problem with forwarding and then returning the date.
> Are there any problems that I should know of?

The basic "problem" is that you may have some files marked with a
"future" creation/modification/access date.  This may or may not
be a problem.  Let's say A.B.C has a modification date of 2000-01-01.
If you've returned to 1999, and your daily partial backup says
"backup everything modified since last week", then A.B.C will be backed
up every week until 2000-01-08.

We have a free utility that will search out every file on the system with
a future date and reset it to today.  It's FIXFDATE and is at:
   http://www.allegro.com/software/#FIXFDATE

Note: if you set your clock ahead by changing the date at bootup,
or by using "SETCLOCK;NOW" or by using HourGlass 2000 for the HP 3000,
then you're likely to run into this situation (having future date files
when you return to "today").  If you use any other date/time simulation
tools (which can't intercept 100% of the date/time calls), you won't
run into this situation ... because you didn't test everything :)

--
Stan Sieler                                           [log in to unmask]
www.allegro.com/sieler/wanted/index.html          www.allegro.com/sieler

ATOM RSS1 RSS2