[sleuthkit-developers] [ sleuthkit-Feature Requests-3519549 ] subsecond timestamp reporting
Brought to you by:
carrier
From: SourceForge.net <no...@so...> - 2012-04-19 15:43:59
|
Feature Requests item #3519549, was opened at 2012-04-19 08:43 Message generated for change (Tracker Item Submitted) made by kfairbanks You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=477892&aid=3519549&group_id=55685 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: API Group: None Status: Open Priority: 5 Private: No Submitted By: kfairbanks (kfairbanks) Assigned to: Nobody/Anonymous (nobody) Summary: subsecond timestamp reporting Initial Comment: While working on the Ext4 support, I noticed that a great deal of the time printing functions eventually end up calling tsk_fs_time_to_str. As a temporary hack, I have made a tsk_fs_time_to_str_subsecs which allows me to pass in another parameter for the ext4 nano second timestamps. So the question is, how should subsecond times be represented in TSK output? Does this require changes to the API? [seconds].[subseconds] (Just a decimal point separating) [seconds] | [subseconds] (An entirely new field) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=477892&aid=3519549&group_id=55685 |