Sponsored Content
Full Discussion: ntp server setup
Top Forums UNIX for Dummies Questions & Answers ntp server setup Post 302189784 by parrisjr on Sunday 27th of April 2008 10:09:31 PM
Old 04-27-2008
ntp server setup

Not connected to the internet so I would like to set up 1 unix machine to be the ntp server and have it sync time to about 30 other machines that are all on an private 10net network?Smilie
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Ntp Server

Hi. i was wondering if anyone can show me or direct me on setting up a ntp server under redhat.. Is there any howtos so i can get familar to it "any good sites" (3 Replies)
Discussion started by: souldier
3 Replies

2. Solaris

ntp server and ntp client

All, How do you set a Solaris 9 server which received ntp updates from a ntp server to broadcast them on a local subnet. I have created a /etc/inet/ntp.conf file to receive the updates from a server on network and need to make this server become like a ntp relay from the main server. Any... (1 Reply)
Discussion started by: bubba112557
1 Replies

3. AIX

NIM server setup on etherchannel setup environment

I know that IBM's official stance is that NIM does not work on etherchannel environment, but has anyone able to get around it? I'm working on a p5-590 LPAR system, and the NIM master and clients are all on the same frame. Any help is appreciated. (1 Reply)
Discussion started by: pdtak
1 Replies

4. IP Networking

server is not getting synchronized with ntp server

Hello Guys, i have a problem my local server is not getting synchronized with ntpd server. 1)ntpq -p is giving the following output remote refid st t when poll reach delay offset jitter ============================================================================== ... (9 Replies)
Discussion started by: mannam srinivas
9 Replies

5. Red Hat

NTP server

Hi All.... I need to configure NTP server in my network, which is heterogeneous, containing Linux as well as windows systems. I'm planning to configure it on RHEL 5.0. What are the prerequisites for this and do I need to register this server? Can anyone give me as many information as... (1 Reply)
Discussion started by: Amol21
1 Replies

6. UNIX for Dummies Questions & Answers

How to setup NTP on unix and linux servers?

I have a hostname/ip of our network time server. What are the steps to take to set each server up to synchronize the clocks? Thanks (4 Replies)
Discussion started by: ChadKam
4 Replies

7. Linux

How often does Linux NTP server update its time with the external NTP server?

All here, thank you for listening. Now I've set up a Linux NTP server by adding a external windows NTP server in /etc/ntp.conf. Then I start the ntpd daemon. But how often does the Linux NTP server update its time with the external NTP server? I've looked up everywhere but found no information... (1 Reply)
Discussion started by: MichaelLi
1 Replies

8. HP-UX

Setting up NTP HP-UX clients from solaris NTP server

Hi I wonder if its possible to setup NTP clients running HP-UX o.s. from a solaris 10 NTP server? FR (3 Replies)
Discussion started by: fretagi
3 Replies

9. Red Hat

Ntp client sync with local over ntp server

Hi, I have two ntp servers in my cluster and I want all the nodes in my cluster to sync with either of the ntp servers or just one. Unfortunately it keep rotating the sync, between my ntp server 1, ntp server 2 and local. Is there anyway I can change the sync to avoid local? # ntpq -p ... (3 Replies)
Discussion started by: pjeedu2247
3 Replies

10. Linux

What is the best OS for NTP server?

Hello I need to create NTP server for all my devices, What is the best OS for NTP Server? "CentOS, Redhat, Ubuntu " I tried before Ubuntu but some of device not detect the server Need your recommendation Thank you (2 Replies)
Discussion started by: moudmm
2 Replies
TIMED(8)						    BSD System Manager's Manual 						  TIMED(8)

NAME
timed -- time server daemon SYNOPSIS
timed [-dtM] [-i network | -n network] [-F host ...] DESCRIPTION
The timed utility is a time server daemon which may be invoked at boot time via launchd(8). (See launchd.plist(5) for more information about configuring daemons to run at boot.) It synchronizes the host's time with the time of other machines, which are also running timed, in a local area network. These time servers will slow down the clocks of some machines and speed up the clocks of others to bring them to the average network time. The average network time is computed from measurements of clock differences using the ICMP timestamp request message. The following options are available: -d Enable debugging mode; do not detach from the terminal. -i network Add network to the list of networks to ignore. All other networks to which the machine is directly connected are used by timed. This option may be specified multiple times to add more than one network to the list. -F host ... - Create a list of trusted hosts. - Can take one or more parameters. - timed will only accept trusted hosts as masters. If it finds an untrusted host claiming to be master, timed will suppress incoming messages from that host and call for a new election. - Use real host names (resolvable by RDNS) not aliases (eg in named(8) parlance: use A names, not C names). - Use full names eg time1.domain.com not time1. - -F automatically includes the functionality of -M ( so -M does not need to asserted). - If -F is not specified, all hosts on connected networks are treated as trustworthy. -M Allow this host to become a timed master if necessary. -n network Add network to the list of allowed networks. All other networks to which the machine is directly connected are ignored by timed. This option may be specified multiple times to add more than one network to the list. -t Enable tracing of received messages and log to the file /var/log/timed.log. Tracing can be turned on or off while timed is running with the timedc(8) utility. The -n and -i flags are mutually exclusive and require as arguments real networks to which the host is connected (see networks(5)). If nei- ther flag is specified, timed will listen on all connected networks. A timed running without the -M nor -F flags will always remain a slave. If the -F flag is not used, timed will treat all machines as trust- worthy. The timed utility is based on a master-slave scheme. When timed is started on a machine, it asks the master for the network time and sets the host's clock to that time. After that, it accepts synchronization messages periodically sent by the master and calls adjtime(2) to per- form the needed corrections on the host's clock. It also communicates with date(1) in order to set the date globally, and with timedc(8), a timed control utility. If the machine running the master becomes unreachable, the slaves will elect a new master from among those slaves which are running with at least one of the -M and -F flags. At startup timed normally checks for a master time server on each network to which it is connected, except as modified by the -n and -i options described above. It will request synchronization service from the first master server located. If permitted by the -M or -F flags, it will provide synchronization service on any attached networks on which no trusted master server was detected. Such a server propagates the time computed by the top-level master. The timed utility will periodically check for the presence of a master on those networks for which it is operating as a slave. If it finds that there are no trusted masters on a network, it will begin the election process on that network. One way to synchronize a group of machines is to use ntpd(8) to synchronize the clock of one machine to a distant standard or a radio receiver and -F hostname to tell its timed to trust only itself. Messages printed by the kernel on the system console occur with interrupts disabled. This means that the clock stops while they are print- ing. A machine with many disk or network hardware problems and consequent messages cannot keep good time by itself. Each message typically causes the clock to lose a dozen milliseconds. A time daemon can correct the result. Messages in the system log about machines that failed to respond usually indicate machines that crashed or were turned off. Complaints about machines that failed to respond to initial time settings are often associated with ``multi-homed'' machines that looked for time masters on more than one network and eventually chose to become a slave on the other network. WARNINGS
Temporal chaos will result if two or more time daemons attempt to adjust the same clock. If both timed and another time daemon are run on the same machine, ensure that the -F flag is used, so that timed never attempts to adjust the local clock. The protocol is based on UDP/IP broadcasts. All machines within the range of a broadcast that are using the TSP protocol must cooperate. There cannot be more than a single administrative domain using the -F flag among all machines reached by a broadcast packet. Failure to fol- low this rule is usually indicated by complaints concerning ``untrusted'' machines in the system log. FILES
/var/log/timed.log tracing file for timed /var/log/timed.masterlog log file for master timed SEE ALSO
date(1), adjtime(2), gettimeofday(2), icmp(4), networks(5), ntpd(8), timedc(8) R. Gusella and S. Zatti, TSP: The Time Synchronization Protocol for UNIX 4.3BSD. HISTORY
The timed utility appeared in 4.3BSD. BSD
February 11, 2008 BSD
All times are GMT -4. The time now is 06:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy