Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #3158 (closed)

Opened 14 years ago

Closed 14 years ago

DOC: FAQ/other explanation of atime/ctime/mtime

Reported by: jamoore Owned by: ajpatterson
Priority: major Milestone: Unscheduled
Component: Documentation Version: n.a.
Keywords: n.a. Cc:
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.


8:34:12 PM User: Hey Josh... Quick question. Got a sec?
8:34:24 PM Josh Moore: Sure. Shoot.
8:35:08 PM User: OriginalFile atime, mtime, ctime aren't documented as to what they are. mtime probably is "modified"... how about (a) and (c)?
8:35:36 PM Josh Moore: access/creation/modification.
8:36:13 PM Josh Moore: These are left in the user space, i.e. the server doesn't try to control them, for example when you access a file the atime is not incremented.
8:36:32 PM Josh Moore: It's basically to allow clients to write as much info as is available on the linux file system into the db.
8:36:40 PM User: All in "file system" terms as opposed to "biologist" frame of ref, where creation could be "acquisition" timestamp...
8:37:52 PM Josh Moore: Exactly. Acquisition information is else where in the data model.
8:38:49 PM User: ... if put in there. Thanks! That's what I needed to know.
8:39:03 PM Josh Moore: No problem.

Change History (2)

comment:2 Changed 14 years ago by ajpatterson

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.61934 sec.)

We're Hiring!