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.

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.

Red Hat 7.2 (kernel version 2.4.7-10) inludes the network time protocol daemon (ntpd) version 4.1.0. I would like to configure the ntpd as a 'client' only, i.e. to receive time updates from a time server, but not to function as a timeserver.

Originally posted by acid_kewpie well ntpd IS a daemon i.e. a server, to recive updates just use rdate on a cron job pr such like

rdate -s tick.august.net

Thanks, Chris!

I also found a more elegant solution by looking at the NTP RFC (1305 - http://www.faqs.org/rfcs/rfc1305.html for details) and at the following URL: http://www.scd.ucar.edu/nets/intro/s...tools/ntp.html - once the default functionality of the daemon and the configurations of the daemon are understood, things become much easier. In a nutshell, the daemon defaults to a Stratum 3 time server, and as long as the daemon is pointed to a higher stratum server / device, then there are no problems using the daemon to retrieve time synchronization. Further, by using the daemon as a Stratum 3 time server, the daemon is also available to provide synchronization for local devices such as workstations and laptops.