Time Synchronization User's Guide

HP NonStop Time Synchronization User’s Guide Page 46 of 81

5. Running TimeSync

This section describes how to run TimeSync on all supported platforms – Guardian, OSS,

Linux, and Windows. Because there are generally multiple mechanisms for starting

TimeSync on any given system, it is important to understand how each mechanism works

- and how it impacts the TimeSync configuration - before you run TimeSync the first time.

5.1 Starting TimeSync on Guardian

The steps for starting TimeSync on Guardian differ depending upon whether you have

configured TimeSync to run under the control of the persistence manager or not. In either

case, though, starting TimeSync is simple. In addition, there are no specific changes that

need to be made to the configuration file based on the method used.

 If TimeSync is not configured to run under the control of the persistence manager,

then you can start it as you would any other application process. Since the goal is for

TimeSync to run continuously in the background, HP recommends that you start the

process nowait and assign a dedicated home terminal (e.g. $ZHOME). If TimeSync

will run with client mode enabled, it must be started with SUPER group authority in

order to update the local system time.

For example, if TimeSync was installed to $SYSTEM.ZTIMES, the commands would be:

TACL> logon super.super

…

TACL> run $system.ztimes.timesync/name $TIME, nowait, term $ZHOME/

If the TimeSync configuration file is not named TSCONF, or does not reside in the

program subvolume, you can supply the file location and name using the –conf

command-line option.

 If TimeSync is configured to run under the control of the persistence manager, which

is recommended by HP, then it can be started directly from SCF, and will also be

started automatically at system startup. If TimeSync will run with client mode

enabled, it must be started with SUPER group authority in order to update the local

system time.

For example, if TimeSync was configured as a persistent process with name

#TimeSync, the commands would be:

TACL> scf

1-> assume process $zzkrn

2-> start #TimeSync