Open JElchison opened 10 years ago
Can we get better granularity via the API's sscm_file_history()
call?
sscm_file_history()
seems to return date as a time_t
, so there's hope...
Solution found: sscm_file_history()
indeed returns date as a time_t
. Broken out into separate sscmhist
C application.
Still need to integrate it with the Python script.
NOTE: Python can get a bunch of the args (except the password) from the cached info in sscm setinfo
.
Right now,
sscm history
outputs timestamps with granularity of minutes (seconds always are 00). Find a way to get seconds, so that we can replay events in the right order.If we can't do this, perhaps we'll need to be smarter about what order we replay events (topological sort?).