How to configure sntp client with multiple time sources?

Login or Register for Dates, Times and to Reply

 
Thread Tools Search this Thread
# 1  
How to configure sntp client with multiple time sources?

Hi,

What is the syntax to configure sntp client to have multiple time sources?
I tried to use the below syntax, but when the src1 is not reachable, the sntp does not even try to sync to src2:

Code:
# /usr/sbin/sntp -P no -r src1 src2
sntp: receive timed out after 3 seconds
sntp: receive timed out after 3 seconds
sntp: receive timed out after 3 seconds
sntp: receive timed out after 3 seconds
sntp: receive timed out after 3 seconds
sntp: not enough valid responses received in time

Also, it is not very clear if the sntp client will always use round robin when multiple sources or only if the first fails?

Thanks!
Login or Register for Dates, Times and to Reply

Previous Thread | Next Thread
Thread Tools Search this Thread
Search this Thread:
Advanced Search

10 More Discussions You Might Find Interesting

1. Red Hat

Firewalld - multiple services / sources?

If you have a system with one network interface, and you want to allow ssh from some addresses, freeipa-ldap from others, and https (which is part of freeipa-ldap) from another one; and you do not want to have a sea of rich rules... how do you do that? I can't tell if firewalld is just really... (2 Replies)
Discussion started by: jnojr
2 Replies

2. Proxy Server

Configure native ldap client on Solaris 10

Hi guys. First, sorry for my english, Im tried to write the best form but sure Im not do it. Im tried to configure the native ldap client on Solaris 10 but yet dosen't work. May be the problem is in the pam.conf or something like that. This is the line I was applied to configure the... (7 Replies)
Discussion started by: sultano
7 Replies

3. Solaris

Configure Solaris 10 as a RADIUS Client

Hello, I have a solaris 10 U 8 and want it to authenticate any user against a remote RADIUS server and return it's appropriate privileges on the system First is it possible? and if yes, How I can do it? please a consider I'm a little "newbie" on Solaris world Thanks in advance! (0 Replies)
Discussion started by: basim
0 Replies

4. Shell Programming and Scripting

unable to configure NIS client server

Dear all, I am using solaris 10 OS. I configured NIS server and i also configured NIS client server but when i use the command ypinit -s sunserv1 in NIS client it is showing me the below error. Enumerates maps from sunserv1. please check that it is running. (2 Replies)
Discussion started by: bhargav90
2 Replies

5. Solaris

Cannot configure NTP client

Hi, I am trying to configure NTP client on my Solaris server, but I am getting error like: Jan 13 10:53:33 SPOTS ntpdate: no server suitable for synchronization foundMy ntp.conf file: bash-3.00# pwd /etc/inet bash-3.00# bash-3.00# bash-3.00# cat ntp.conf # ident "@(#)ntp.client... (5 Replies)
Discussion started by: nypreH
5 Replies

6. AIX

aix-configure nim client

:b:Hi... I need help to configure nim client on nim server.. can i define aix 5.3.4.0 on aix 5.3.7.0 nim server.. while i m configuring nim client on nim server its getting msg that images not same.. i need to confirm that both version should be same or not.. Thanks.. (5 Replies)
Discussion started by: sumathi.k
5 Replies

7. Solaris

How to Configure NIS Client for Solaris7 x86

HI Unix Gurus i am new to Solaris OS, i want to configure NIS CLient for Solaris 7 x86 Machine. i need what are the step and how to configure it in that machine.. please let me know Thanks in Advance Regards ..kiruba.. (2 Replies)
Discussion started by: nkkirubakaran
2 Replies

8. SCO

configure client for internet !

i m using SCO unix openserver 5.0.... on my client machine. i have assign static IP to it and can ping the server. but now i want to connect internet on it through LAN , don't know how to do that?/ like in redhat linux we add dns or gatway entry to the /etc/resolv.conf don't know about SCO unix... (2 Replies)
Discussion started by: alamlinux
2 Replies

9. Red Hat

How to configure a Redhat 9.0 as NIS+ client

I would like to know how to configure a Redhat 9.0 as NIS+ client. I have seen the post of larry, but it is not enough information for me to do the configuration. Could anyone tell me how to do it? Please help! Thank you! (3 Replies)
Discussion started by: alexhon
3 Replies

10. IP Networking

Howto configure AIX DHCP Client ?

I use DHCP on my AIX box at home . I want to connect to my Cable ISP as a DHCP Client . the thing I did was this : smit Communications Applications and Services TCP/IP Use DHCP for TCPIP Configuration and Startup "Select the interface you want to use" en0 "Enter a hostname" OK after... (3 Replies)
Discussion started by: zumbi
3 Replies
XAllowDeviceEvents(3X11)					    X FUNCTIONS 					  XAllowDeviceEvents(3X11)

NAME
XAllowDeviceEvents - release queued events SYNTAX
int XAllowDeviceEvents(Display *display, XDevice *device, int event_mode, Time time); ARGUMENTS
display Specifies the connection to the X server. device Specifies the device from which events are to be allowed. event_mode Specifies the event mode. You can pass AsyncThisDevice, SyncThisDevice, ReplayThisDevice, AsyncOtherDevices, SyncAll, or Asyn- cAll. time Specifies the time. You can pass either a timestamp or CurrentTime. DESCRIPTION
The XAllowDeviceEvents function releases some queued events if the client has caused a device to freeze. It has no effect if the specified time is earlier than the last-grab time of the most recent active grab for the client and device, or if the specified time is later than the current X server time. The following describes the processing that occurs depending on what constant you pass to the event_mode argument. AsyncThisDevice If the specified device is frozen by the client, event processing for that device continues as usual. If the device is frozen multiple times by the client on behalf of multiple separate grabs, AsyncThisDevice thaws for all. AsyncThisDevice has no effect if the specified device is not frozen by the client, but the device need not be grabbed by the client. SyncThisDevice If the specified device is frozen and actively grabbed by the client, event processing for that device continues normally until the next key or button event is reported to the client. At this time, the specified device again appears to freeze. However, if the reported event causes the grab to be released, the specified device does not freeze. SyncThisDevice has no effect if the specified device is not frozen by the client or is not grabbed by the client. ReplayThisDevice If the specified device is actively grabbed by the client and is frozen as the result of an event having been sent to the client (either from the activation of a GrabDeviceButton or from a previous AllowDeviceEvents with mode SyncThisDevice, but not from a GrabDevice), the grab is released and that event is completely reprocessed. This time, however, the request ignores any passive grabs at or above (toward the root) that the grab-window of the grab just released. The request has no effect if the specified device is not grabbed by the client or if it is not frozen as the result of an event. AsyncOtherDevices If the remaining devices are frozen by the client, event processing for them continues as usual. If the other devices are frozen multiple times by the client on behalf of multiple grabs, AsyncOtherDevices "thaws" for all. AsyncOtherDevices has no effect if the devices are not frozen by the client. SyncAll If all devices are frozen by the client, event processing (for all devices) continues normally until the next button or key event is reported to the client for a grabbed device, at which time all devices again appear to freeze. However, if the reported event causes the grab to be released, then the devices do not freeze. If any device is still grabbed, then a subse- quent event for it will still cause all devices to freeze. SyncAll has no effect unless all devices are frozen by the client. If any device is frozen twice by the client on behalf of two separate grabs, SyncAll thaws for both. A subsequent freeze for SyncAll will only freeze each device once. AsyncAll If all devices are frozen by the client, event processing for all devices continues normally. If any device is frozen multiple times by the client on behalf of multiple separate grabs, AsyncAll thaws for all. AsyncAll has no effect unless all devices are frozen by the client. AsyncThisDevice, SyncThisDevice, and ReplayThisDevice have no effect on the processing of events from the remaining devices. AsyncOtherDe- vices has no effect on the processing of events from the specified device. When the event_mode is SyncAll or AsyncAll, the device parame- ter is ignored. It is possible for several grabs of different devices by the same or different clients to be active simultaneously. If a device is frozen on behalf of any grab, no event processing is performed for the device. It is possible for a single device to be frozen because of several grabs. In this case, the freeze must be released on behalf of each grab before events can again be processed. XAllowDeviceEvents can generate a BadDevice or BadValue error. DIAGNOSTICS
BadDevice An invalid device was specified. The specified device does not exist or has not been opened by this client via XOpenInputDe- vice. This error may also occur if the specified device is the X keyboard or X pointer device. BadValue An invalid mode was specified on the request. SEE ALSO
XGrabDevice(3X11) Programming With Xlib XFree86 Version 4.7.0 XAllowDeviceEvents(3X11)

Featured Tech Videos