id summary reporter owner description type status priority milestone component version resolution keywords cc drp_resources i_links o_links remaining_time sprint 3158 DOC: FAQ/other explanation of atime/ctime/mtime jamoore ajpatterson "{{{ 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. }}} " task closed major Unscheduled Documentation fixed