Marco,

To add to Ray's comments, UV updates header info in DATA.30 whenever
it's parent UV dynamic hashed file is closed (by any user with write
permissions) whether or NOT there have been any actual data updates.  In
the process, the OS updates the date-time-modified stamp for DATA.30.

This means that you can't really get the info he's looking for: when the
file was last modified, i.e., with real data.

Remember the T30FILE config parameter?   It tells UV about allocating
shared memory for managing current load/split/merge info for dynamic
(Type30) files.  Whenever any write-enabled user closes a T30 file, that
info is written back out to the header DATA.30.   I *think* the step is
entirely superfluous since the header info is also written whenever a
split/merge occurs.

This means even if you LIST a file,  the date-time-modified stamp is set
to current date-time when LIST completes.  (Although a user without
write permissions can successfully list the file & no such
date-time-modified stamping occurs.)

  If UV would store the header info in .Type30 instead of DATA.30 I, for
one, would be grateful.  I'd like to use the date-time-modified stamp
the same way Marco wants.

If anyone can correct me or knows a way around this,  I wish they'd say
so.

- cds



> [mailto:[EMAIL PROTECTED] On Behalf Of Ray Wurlod
> ...If you're talking about a dynamic hashed file, it's 
> DATA.30 (and/or OVER.30) that would be updated, not their 
> parent directory....
> 
> ----- Original Message -----
> From: Marco Manyevere <[EMAIL PROTECTED]>
> Date: Mon, 8 Mar 2004 08:16:38 +0000 (GMT)
> To: [EMAIL PROTECTED]
> Subject: [UV] Date-Time stamping
> 
> > Hi All,
> >  
> > When does universe update the OS level date time stamp ?...
--
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users

Reply via email to