Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pmmktime(3) [centos man page]

PMMKTIME(3)						     Library Functions Manual						       PMMKTIME(3)

NAME
__pmMktime - convert a tm structure to a calendar time C SYNOPSIS
#include <time.h> #include <pcp/pmapi.h> #include <pcp/impl.h> time_t *__pmMktime(struct tm *timeptr); cc ... -lpcp DESCRIPTION
__pmMktime is very similar to mktime(3), except the timezone used is the current ``reporting timezone'' (rather than the default TZ envi- ronment variable scheme). Like mktime(3) the time to be converted is passed via timeptr, and the function result contains the calendar time (the number of seconds since 00:00:00 UTC, January 1, 1970). The default current reporting timezone is as defined by the TZ environment variable, so __pmMktime and mktime(3) will initially produce similar conversions. Use pmNewZone(3), pmNewContextZone(3) or pmUseZone(3) to establish a new current reporting timezone that will effect __pmMktime but not mktime(3). SEE ALSO
mktime(3), PMAPI(3), pmCtime(3), pmLocaltime(3), pmNewContextZone(3), pmNewZone(3) and pmUseZone(3). Performance Co-Pilot PCP PMMKTIME(3)

Check Out this Related Man Page

PMNEWCONTEXTZONE(3)					     Library Functions Manual					       PMNEWCONTEXTZONE(3)

NAME
pmNewContextZone - establish a reporting timezone based on a PMAPI context C SYNOPSIS
#include <pcp/pmapi.h> int pmNewContextZone(void); cc ... -lpcp DESCRIPTION
The current reporting timezone affects the timezone used by pmCtime(3) and pmLocaltime(3). If the current PMAPI context is an archive, pmNewContextZone uses the timezone from the archive label record to set the current reporting timezone. If the current PMAPI context corresponds to a host source of metrics, pmNewContextZone executes a pmFetch(3) to retrieve the value for the metric pmcd.timezone and uses that to set the current reporting timezone. In both cases, pmNewContextZone returns a value to identify the current reporting timezone that may be used in a subsequent call to pmUse- Zone(3) to restore this reporting timezone. SEE ALSO
PMAPI(3), pmCtime(3), pmFetch(3), pmGetConfig(3), pmLocaltime(3), pmNewContext(3), pmNewZone(3), pmUseZone(3), pmWhichZone(3), pcp.conf(5), pcp.env(5) and environ(5). DIAGNOSTICS
PM_ERR_NOCONTEXT the current PMAPI context is not valid other a return value less than zero indicates a fatal error from a system call, most likely malloc(3C) Performance Co-Pilot PCP PMNEWCONTEXTZONE(3)
Man Page