Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
There is less than 12 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I've should synchronize my LAN. Problem is that I have to this a quite powerless box - Dell Gn+ P200MHz MMX with 64MByte RAM, which have also quite high load (message concentration from several channels, and synchronize end points to his own clock). I've a /uBlox GPS as time source. Which NTP server to choose, what using the less resources. I'm using Debian stbale 3.1 and the easiest way to use "debianized" packages: chrony, simple NTP and BSD NTP.
May be, the best solution for me, periodically (every day) get the time from GPS, simply set timer of my box and others would get time from time or daytime service through inetd (box does not connected to internet anyway). I do not need to high precise clock - some seconds would be enough.
But of course the NTP would be a more professional solution ...
how would you expect any ntp server to use any resources worth mentioning? even with 100 machines connecting to it, the server would typically only recieve an ntp request once every 10 seconds once the clients settle down...
acid_kewpie - thanks to your reply, but my english also as worth as my box. The LAN what should be served about 12 boxes. I'm not afraid about requests but the memory consuption - 64 MByte total and free about 10 MByte! Also, I've should using interface to connect GPS. I look through some descriptions about NTP servers are listed. all of them seem to be quite complex, with a lot of configuring to do, but no information about memory consuption or resources are used. I wait suggetions from guys who look on thaose NTP servers in live, I only heard about them, and don't have time to try all of them
I do not have apropriate router. The preferrable place for NTP is in this box - it is working like a kind router/gateway - I called it as "concentrator". This box collecting messages from several hundreds of equipment, and those equipment are also synchromized with this box, which is made by underlying protocol automatically (or may be nested).
i just don't think you have a thing to be concerned about. ntp is a tiny thing in all respects other than importance... only issue i would think of is that the box it is running on itsel fneeds a solid and reliable clock to minimize additional drift.
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
OpenNTPD is quite small, much smaller than ISC NTPd. There is a portable version of the source code for Linux.
You can see that the goals are mostly about security and simplicity. The man page for ntp.conf is very simple. The only options you would need are sensor (to tell it which device is your GPS) and listen on to tell it which IP addresses to accept queries on. That's it!
You can use a simple script to start the service:
### BEGIN INIT INFO
# Provides: openntpd
# Required-Start: network
# Required-Stop: network
# Default-Start: 2 3 5
# Default-Stop: 0 1 6
# Description: OpenNTPD Startup Service for Linux
### END INIT INFO
case "$1" in
if [ -f $NTPD_CONFIG ]; then
if [ -x $OPENNTPD_BIN ]; then