Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Help starting NTP daemon with Slackware

This is not going to work.  NTP relies upon exchanges involving port 123.  
With restrictions as draconian as you descrive, moving precise time
information would be very difficult.

There are several approaches.  The straightforward solution would be to
set up a local Stratum 1 time server, referenced to some hardware clock.  
These can be done for surprisingly little money, either with GPS receivers
( or even ordinary sound cards

One option you might consider is using HTTP timestamps for external
synchronization.  This would be less accurate than NTP, but it would get
through your firewall.  You could easily write a simple daemon that looked
like a hardware clock to the NTP daemon and checked HTTP timestamps.  
Obviously, the accuracy of the system to which you are referring would be
critical, so you would want to use a web server that is locked by NTP.

-- Mike

On 2000-06-20 at 19:44 -0400, Scott Ehrlich wrote:

> We have a Slackware 7 server which we want to use as the central time
> server for the LAN.   We also have set up a lot of security, permitting
> only ssh, smtp, and http.   There is no firewall.   I'm trying to figure
> out how to start an NTP daemon so the other servers can keep their
> respective times correct.

Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at (Subject line is ignored).

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /