We would like to start using the timed daemon to keep the clocks
on our Rs/6000s in sync, and I have a few questions about setting
it up:
1) We have 19 320's, and 1 530. From the man page on timed, it
looks as though we need to run timed -M on one of our machines
to act as the master, then start up timed with no options on the
rest of the workstations. Is this correct?
2) If we would like to have one of our 320s' serve as a "backup"
time server, do we simply start up another timed -M on it?
3) Is the network (-n) options a requirement? Not all of our
machines are on the same (class c) network.
---------- ---------- ---------- --------- ---------- ----------
A: Yes, you are correct. For the system that you want to be the
Master time server, use the -M flag when timed is started. When the
timed daemon is initially started this way, it will first look to
see if there is a master timeserver on the network. If there is not,
it will become the master time server. Another system can be started
with the "-M" flag, to act as a backup master server in case the
first master time server becomes unavailable. All other systems
running the timed daemon will be slave time servers.
The "-n" flag is not required. This can be used to serve specific
networks in a multiple network environment. Not using this option, allows
the timed daemon to participate in time service on all networks that
the system is connected to.
---------- ---------- ---------- --------- ---------- ----------
This item was created from library item Q610277 3852K
Additional search words:
AIX ALTERNATE ARISC CUSTORG DAEMON IMPLEMENTING INDEX IX OCT92 OZNEW
RISC TIMED 3852K
WWQA: ITEM: RTA000027352 ITEM: RTA000027352
Dated: 11/1996 Category: RISCOHW
This HTML file was generated 99/06/24~12:43:10
Comments or suggestions?
Contact us