Wed, 29 Sep 2004
Round Robin Network Time Protocol
A little bit of online technology I've been using for the last couple of
months is the pool.NTP service
provided at (surprisingly) pool.ntp.org. NTP is used to keep your local system
clocks synchronised by using some of the bigger, more accurate clocks such as
atomic or radio clocks.
Traditionally you would add three or four server names/IP addresses to your NTP configuration file and the time would be pulled down and used, the downside to this included the need to ensure the remote servers were still available and the issue of being a burden as the teeming hordes of NTP clients hit the same servers again and again.
The pool.ntp.org servers get around this problem by using round-robin DNS to make both the client configuration easy and reduce the strain on the servers themselves. In the config file instead of adding different servers you add the same entry each time, in my case I add 'uk.pool.ntp.org', if you try pinging this name then each couple of tries you will receive the response from a different IP address. While this may not seem very helpful from the client side (you still have to add the config entries anyway, unless you use Debian :)) from a server operators perspective it helps spread the traffic, instead of the first few listed servers getting hit by everyone the round robin helps distribute the load.
If you've read this far then you probably run your own ntp client or server. If you use a client then change the config to use the pooled NTP, if you run a server then please consider adding yourself to the available servers.
Like this post? - Digg Me! | Add to del.icio.us! | reddit this!
Posted: 2004/09/29 19:49 | /tools/online | Permanent link to this entry | This entry + same date
/etc/release -- Consistency, never heard of it!
If you are working on a modern Unix machine (no, thats not an oxymoron)
then it's annoying difficult to determine the operating system name and
version running. Where you should just be able to type '/etc/release' and
get the relevant details you instead need to either guess or brute-force your
way through the possibilities. Debian stores this info in
'/etc/debian_version', Redhat in '/etc/redhat_release'. You know the world
is going to end when Solaris makes the most sense and puts this information
in '/etc/release'. Why is this better? Because it doesn't assume my scripts
know where they are running, they can determine that from the contents of
the file itself!
A warning to one and all, this is going to become my new crusade ;)
Like this post? - Digg Me! | Add to del.icio.us! | reddit this!
Posted: 2004/09/29 19:30 | /operatingsystems/linux | Permanent link to this entry | This entry + same date
Copyright © 2000-2005 Dean Wilson
