Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Target Release17.1.1
JIRA

Jira Legacy
serverJIRA (pbspro.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId32008a99-7831-3ff8-9638-3db0cd01164d
keyPP-261

Document statusInitial Version
Document owner
Designer
Developers
QA
Forum Discussionhttp://community.pbspro.org/t/pp-261-micro-second-time-stamp-for-daemon-logging/467
Interface1: New switch in PBS Configuration: PBS_LOG_HIGHRES_TIMESTAMP
    • Visibility: Public
    • Change Control: Stable
    • SynopsisPBS_LOG_HIGHRES_TIMESTAMP
    • Details: This  
      • This is new parameter for pbs.conf file, using this parameter admin can control high resolution logging in PBS daemons logs.
        • Possible value for this parameter is 1(enabled) or 0(disabled).
        • By default high resolution will be disabled in PBS.
       If
      • If high resolution is enabled then log's datetime format will be DD/MM/YYYY HH:MM:SS.XXXXXX where XXXXXX will be microsecond.  XXXXXX will always be 6 digits (proceeded by zeros if need be).
      • If high resolution is disabled then no change in current log's datetime format (i.e. DD/MM/YYYY HH:MM:SS). 
      • High resolution logging will NOT be used in Accounting logs for backward compatibility for PBS Analytics.
       This is a node level option.

...

      •   Also this feature does not apply if PBS Pro is configured to log via syslog.
      • If enabled/disabled in pbs.conf, it will apply to all daemons on that host.
        • If enabled on the server host, it will affect the server, scheduler, and the mom on that host
        • If enabled on an execution host, it will only affect the mom on that host only.
      • As with all pbs.conf variables, PBS_LOG_HIGHRES_TIMESTAMP can be overridden by an environmental variable of the same name.