int pmParseTimeWindow(const char * swStart , const char * swEnd , const char * swAlign , const char * swOffset , const struct timeval * logStart , const struct timeval * logEnd , struct timeval * rsltStart , struct timeval * rsltEnd , struct timeval * rsltOffset , char ** errMsg );
The syntax and meaning of the various argument formats for these options is described in PCPIntro (1).
If the application is using a set of PCP archive logs as the source of performance metrics, you also need to supply the time of the first archive log entry as logStart , and the time of the last archive log entry as logEnd . See pmGetArchiveLabel (3) and pmGetArchiveEnd (3) for how to obtain values for these times.
If the application is manipulating multiple concurrent archive logs, then the caller must resolve how the default time window is to be defined (the union of the time intervals in all archive logs is a likely interpretation).
If the application is using a live feed of performance data, logStart should be the current time (but could be aligned on the next second for example), while logEnd should have its tv_sec component set to INT_MAX .
The rsltStart , rsltEnd and rsltOffset structures must be allocated before calling pmParseTimeWindow .
You also need to set the current PCP reporting time zone to correctly reflect the -z and -Z command line parameters before calling pmParseTimeWindow . See pmUseZone (3) and friends for information on how this is done.
If the conversion is successful, but the requested alignment could not be performed (e.g. the set of PCP archive logs is too short) the alignment is ignored, rsltStart , rsltEnd and rsltOffset are filled in and pmParseTimeWindow returns 0. In this case, errMsg will point to a warning message in an internal static buffer. This buffer should not be freed.
If the argument strings could not be parsed, pmParseTimeWindow returns -1. In this case, errMsg will point to an error message in a static internal buffer.