Hi,
Have never run xntpd before. I have my ntp.conf file configured with server, trace file and drift file. I commented out the "broadcastclient" entry since I only want to get the time from a single source. Port 123 is in the /etc/services file for tcp and udp. Port 123 has been enabled in the ISA firewall so it can get to the outside time server.
Can I cause any damage bringing this up during the middle of the day when there are many users on the system if it doesn't run correctly?
After my research, I am assuming that I run "startsrc -s xntpd" to start and then run "stopsrc -s xntpd" to stop the daemon if there is a problem.
If all runs well, then I uncomment the xntpd startup in /etc/rc.tcpip to run the daemon upon system boot. Correct?
Thanks in advance for any input or advice anyone can give me.
Last edited by DenD; 12-21-2005 at 05:56 PM..
Reason: typo
I copied the script from an AskUbuntu post -
#!/bin/bash
### BEGIN INIT INFO
# Provides: tomcat7
# Required-Start: $network
# Required-Stop: $network
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start/Stop Tomcat server
### END INIT INFO
... (14 Replies)
Hi, I want to setup xntpd with two sources ntp servers. I added to /etc/ntp.conf:
server IP1
server IP2
but, when the server lost the connection with the first, it doesn't connect the second.
#/home/s03isga0 # ntpq -p
remote refid st t when poll reach delay ... (4 Replies)
Hi,
Does anyone know how to make sure that the slewing option in solaris 10 is on. From the man page I believe I had to add "slewalways yes" to the ntp.conf file and restart the service, but I don't know if its has gone into effect or not.
Thanks (3 Replies)
AIX 5.3-5300.09.06.1013 (AIX 5.3 TL9 SP6)
# startsrc -s xntpd -a "-x"
(with -x at the end of the xntpd line in /etc/rc.tcpip, too.)
will run for 5-15 minutes, and then die.
# errpt -a
with a search on xntpd gives me this:
------------------------------------------------
LABEL: ... (7 Replies)
Dear All,
I installed the Solaris 2.10 (05/09) download on a Sparc platform, and wanted to configure the network time protocol daemon (xNTPD) to work as an NTP client.
Of course there are many web sites that trumpet the advise to simply copy the ntp.client file to the ntp.conf file, and then... (2 Replies)
Hi,
I am Solaris 9 developer and notice that the documentation does not provide a clear notion of the inherent concurrency in routines defined as "Async-Signal-Safe".
Routines defined as "MT-Safe" obviously have the best level of concurrency, compared to normal "Safe" interfaces.
I have... (1 Reply)
Hi:
I,am trying syncronise clock, but i canīt do it
In the server client put:
/etc/ntp.conf -> server namehost
-> resolver /etc/xntpres
/etc/tcp -> uncoment lines when say Xntpd
/etc/ xntpd
In the server as server clock:
/etc/ntp.conf -> peers hostname
if... (1 Reply)
PACEMAKER(8) BSD System Manager's Manual PACEMAKER(8)NAME
pacemaker -- clock drift adjustment daemon
SYNOPSIS
pacemaker [-d drift] [-b] [-e error] [-a interval] [-i] [-v] [-n]
DESCRIPTION
pacemaker adjusts the system clock periodically to compensate for clock drift. The clock drift is normally computed by ntpd(8), which writes
a clock drift value in /var/db/ntp.drift. By default, pacemaker will call adjtime(2) once per second to slew the system clock. The daemon
is started by launchd(8) only when the drift file is present or has just been created in the file system. pacemaker detects changes in the
file and re-calculates clock adjustment values appropriately. The daemon will exit if the drift file is deleted and is not re-created within
one minute.
As a fail-safe mechanism, pacemaker will reset the system clock using settimeofday(2) if the system clock requires adjustment exceeding the
maximum value that can be accomodated by adjtime to slew the clock. In practice, this extreme case should never occur.
The -d option allows the specification of either a floating-point drift value, or the path name of an alternate drift file. If a floating
point drift value is specified, pacemaker will use the given value and will not read a drift file.
To reduce power consumption, especially when the system is using internal battery power, it may be desirable to reduce the frequency of calls
to adjust the system's clock drift. The -e and -a options, together with the -b flag allow several ways to control the clock adjustment fre-
quency.
The floating point value following -e specifies a maximum error tolerance in seconds for the system clock. For example, a value of 0.001
specifies that the clock drift adjustment should only be done frequently enough to keep the system clock error within one millisecond, based
on the current clock drift rate.
Alternatively, the clock adjustment frequency can be specified exactly as a value in seconds following -a.
When both -e error and -a interval are provided, pacemaker will choose to adjust the system clock either every interval seconds, or less fre-
quently if the clock error will remain within error seconds.
The settings for -e and/or -a may be specified for operation of the system while using an external power source, and specified independently
for operation using internal batteries. By default, the values for -e and/or -a are used for both power configurations. If the -b flag pre-
cedes -e and/or -a, then the following settings apply only when the system is using internal battery power.
For example, starting pacemaker with the following parameters will cause it to adjust the clock every 2 seconds when the system is using
external power. When running on battery power, it will adjust the clock no more than once every 10 seconds, or less frequently if the clock
error remains less than five milliseconds.
pacemaker -a 2 -b -a 10 -e 0.005
When invoked on the command-line with -i, pacemaker prints a summary of internal parameters and then exits. The -v flag causes pacemaker to
print copies of its log messages to standard error. Note that this requires running the program from the command line rather than from
launchd. -n causes pacemaker to run without actually attempting to adjust the system clock.
FILES
/var/db/ntp.drift default clock drift file
SEE ALSO launchd(8), ntpd(8), adjtime(2), settimeofday(2).
HISTORY
The pacemaker daemon was introduced in OS X 10.9.
OS X March 9, 2013 OS X