Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!mtxinu!unisoft!hoptoad!peora!rtmvax!bilver!bill
From: bill@bilver.UUCP (bill vermillion)
Newsgroups: comp.unix.questions
Subject: Re: find(1) question about mtime
Message-ID: <492@bilver.UUCP>
Date: 6 Apr 89 01:40:30 GMT
References: <976@n8emr.UUCP>
Reply-To: bill@bilver.UUCP (bill vermillion)
Organization: W. J. Vermillion, Winter Park, FL
Lines: 25

In article <976@n8emr.UUCP> lwv@n8emr.UUCP (Larry W. Virden) writes:
>
>I am using find on both Ultrix 2.3 and SunOS 4.0.1 on a 386i.  I have
>a file whose ls -l date (documented as the modification time) is
>April 1, 1989 at 9:09 am.  On my machine, it is after 10am on April 3.
>I run find filename -mtime +1 -print.  My file's name does not appear.
>I run find filename -mtime 1 -print.  My file's name DOES appear.
>
>Note that it is more than 48 hours after the modification time.  Why does
>find insist that the mtime is only 1 day old?
>

It's relatively simple - from the way I see it.  Your file is less
than 48 hours old.

All files times are stored in GMT - (or UCT now).  From 909am April 1,
that should be 1409 GMT.   10am on April 3 should be 1400 GMT.  

GMT did NOT change at 2am Sunday, but your computer went from EST to
EDT.  Thus 10am Monday is only 47 hours and 50 minutes later than
910AM saturday.
 
Just a stroke of timing.  If you had waited another 10 or 15 minutes
you probably wouldn't have seen it.
-- 
Bill Vermillion - UUCP: {uiucuxc,hoptoad,petsd}!peora!rtmvax!bilver!bill
                      : bill@bilver.UUCP