[ntp:questions] NTP 4.2.4p5-RC1 Released
Redwood City, CA - 2008/05/20 - The NTP Public Services Project (http://support.ntp.org/) is pleased to announce that NTP 4.2.4p5-RC1, a Release Candidate of the NTP Reference Implementation from the NTP Project, is now available at http://www.ntp.org/downloads.html and http://support.ntp.org/download. Bug Fixes: * [Bug 982] ntpdate(and ntptimeset) buffer overrun if HAVE_POLL_H isn't set (dup of 908). http://bugs.ntp.org/982 * [Bug 857] ntpdate debug mode adjusts system clock when it shouldn't. http://bugs.ntp.org/857 * [Bug 532] nptdate timeout is too long if several servers are supplied. http://bugs.ntp.org/532 * [Bug 902] Fix problems with the -6 flag. http://bugs.ntp.org/902 * [Bug 698] timeBeginPeriod is called without timeEndPeriod in some NTP tools. http://bugs.ntp.org/698 * [Bug 987] Wake up the resolver thread/process when a new interface has become available. http://bugs.ntp.org/987 * [Bug 908] ntpdate crashes sometimes. http://bugs.ntp.org/908 * [Bug 1000] allow implicit receive buffer allocation for Windows. fixes startup for windows systems with many interfaces. reduces dropped packets on network bursts. additionally fix timer() starvation during high load. http://bugs.ntp.org/1000 * [Bug 957] Windows only: Let command line parameters from the Windows SCM GUI override the standard parameters from the ImagePath registry key. http://bugs.ntp.org/957 * [Bug 959] Refclock on Windows not properly releasing recvbuffs. http://bugs.ntp.org/959 * [Bug 977] Fix mismatching #ifdefs for builds without IPv6. http://bugs.ntp.org/977 * [Bug 990] drop minimum time restriction for interface update interval. http://bugs.ntp.org/990 * [Bug 993] Fix memory leak when fetching system messages. http://bugs.ntp.org/993 * [Bug 997] ntpdate buffer too small and unsafe. http://bugs.ntp.org/997 Other Changes: * Startup code for original LinuxPPS removed. LinuxPPS now conforms to the PPSAPI. * Update the copyright year. * Build system cleanup (make autogen-generated files writable). * Fixes for ntpdate: * ntpdate.c: Under Windows check whether NTP port in use under same conditions as under other OSs. * ntpdate.c: Fixed some typos and indents (tabs/spaces). * Correctly apply negative-sawtooth for oncore 12 channel receiver. The file-size of this Release Candidate is 3439745 bytes. An MD5 sum of this release is available at http://www.ntp.org/downloads.html and http://support.ntp.org/download. Please report any bugs, issues, or desired enhancements at http://bugs.ntp.org/. The NTP (Network Time Protocol) Public Services Project, which is hosted by Internet Systems Consortium, Inc. (http://www.isc.org/), provides support and additional development resources for the Reference Implementation of NTP produced by the NTP Project (http://www.ntp.org/). ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
[ntp:questions] Symmetricom BC635 reference clock for linux
Has anyone developed the reference clock to the symmetricom BC635PCI card under linux? There was chatter on this but the thread ended. The name Rob appeared in the thread an it appeared he developed the driver. I would greatly appreciate help getting this reference clock since symmetricom appears to have no interest in providing one Thanks Mike Hardy ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Symmetricom BC635 reference clock for linux
Michael Hardy wrote: Has anyone developed the reference clock to the symmetricom BC635PCI card under linux? There was chatter on this but the thread ended. The name Rob appeared in the thread an it appeared he developed the driver. I would greatly appreciate help getting this reference clock since symmetricom appears to have no interest in providing one Thanks Mike Hardy I think there is an NTP driver for this device. For the hardware device driver, you will have to look to Symmetricom or write your own. Writing a hardware device driver is not for the faint at heart! You need an excellent knowledge of how the hardware works and how the O/S you are using interfaces with devices. An error in a device driver has the potential to crash the system! I'm fairly certain that Symmetricomm offers some software support (device drivers, etc.) for some operating systems and hardware platforms but you will need to get the details from them. ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Synchronizing NTP in WAN and LAN
Deepak Pandian wrote: It seems the OS reads the time zone information from a configured file.Is there any other protocol which can instruct the clients connected to it on timezone. This depends on the OS. Some will require a reboot after such a change, as the file is read into an environment variable during startup. Others read the file every time. Some of those actually use a link to the file. For Windows, there may be something in group policies management, but note that the timezone is a property of each user. For Unix, any tool for remotely updating files, e.g. ftp, sftp, rsync, or even rsh, telnet, ssh, might be appropriate. Note that Unix users can override the timezone in their initialisation scripts, and you cannot predict how they will do this. Actually, why do you want to do this? For a normal modern Unix system, using the Olsen package, you should be setting the timezone when you install the system and updating the timezone database files when a significant legislation change changes the rules. Note, messing with the timezone files yourself may mean that an upgrade fails to update the file you've played with. Older Unix systems normally only need updating with legislation changes (provided you can specify the rules in terms of nth week or last week, but, unlike Olsen based systems, you cannot specify rule changes into the indefinite future. For Windows, legislation changes are implemented using Windows Update. If you are trying to move the clock an hour twice a year, with any operating capable of running ntpd, you are not using it properly. ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] SBC-ATT Time Servers
On May 23, 8:15 pm, Steve Kostecke [EMAIL PROTECTED] wrote: slightly reformatted so that it won't wrap on console news-readers... Thank you kindly. However, from the server which monitors it (added as a noselect server): remote refid st t when poll reach delay offset jitter === *nihil .GPS. 1 u 88 256 377 43.086 -3.273 1.211 adsl-71-145-171 217.160... 3 u 968 1024 377 81.478 -50.927 4.942 Just want to point out that this server did have other servers configured whose times were around the one that it was synchronized to, the one I did not edit out above. Thanks. ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Power-saving patch to NTP
Garrett Wollman wrote: In article [EMAIL PROTECTED], Martin Burnicki [EMAIL PROTECTED] wrote: AFAIK ntpd has to manage the binding to interfaces at least if autokey is enabled since the signature hash also includes the IP address of the interface via which a packet is sent. At least some operating systems (don't know about Linux) allow this to be controlled using a control message. For example, from the FreeBSD 6.3 ip(4) manual page: The source address to be used for outgoing UDP datagrams on a socket that is not bound to a specific IP address can be specified as ancillary data with a type code of IP_SENDSRCADDR. The msg_control field in the msghdr structure should point to a buffer that contains a cmsghdr structure fol- lowed by the IP address. The cmsghdr fields should have the following values: cmsg_len = sizeof(struct in_addr) cmsg_level = IPPROTO_IP cmsg_type = IP_SENDSRCADDR For convenience, IP_SENDSRCADDR is defined to have the same value as IP_RECVDSTADDR, so the IP_RECVDSTADDR control message from recvmsg(2) can be used directly as a control message for sendmsg(2). The IPV6_PKTINFO message is used for analogous functions in IPv6. -GAWollman We are aware of sendmsg(), recvmsg() and friends. The problem, however, is that there are many platforms that do not support this yet. It's a major effort to deal with this. Danny ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Power-saving patch to NTP
Martin Burnicki wrote: Garrett, Garrett Wollman wrote: In article [EMAIL PROTECTED], Martin Burnicki [EMAIL PROTECTED] wrote: AFAIK ntpd has to manage the binding to interfaces at least if autokey is enabled since the signature hash also includes the IP address of the interface via which a packet is sent. At least some operating systems (don't know about Linux) allow this to be controlled using a control message. For example, from the FreeBSD 6.3 ip(4) manual page: The source address to be used for outgoing UDP datagrams on a socket that is not bound to a specific IP address can be specified as ancillary data with a type code of IP_SENDSRCADDR. The msg_control field in the msghdr structure should point to a buffer that contains a cmsghdr structure fol- lowed by the IP address. The cmsghdr fields should have the following values: cmsg_len = sizeof(struct in_addr) cmsg_level = IPPROTO_IP cmsg_type = IP_SENDSRCADDR For convenience, IP_SENDSRCADDR is defined to have the same value as IP_RECVDSTADDR, so the IP_RECVDSTADDR control message from recvmsg(2) can be used directly as a control message for sendmsg(2). The IPV6_PKTINFO message is used for analogous functions in IPv6. -GAWollman That's interesting. However, I'm neither familiar with those techniques, nor do I know whether such an approach would be useful for ntpd, especially since ntpd is targeted for multiple platforms (Frank? Danny?) Martin See BIND9 which uses it where possible. The requirements are different on NTP but there are different issues that need to be addressed. Danny ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
