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.
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.
Having an unreliable NTP server - that is a windows clock not syncronised to anything - is it possible to ask the NTP deamon to sync to it no matter what? But not one off, regularly. Stepping time when needed.
but it won't work if the source clock is not stable. I understand that for working properly ntpd needs to see a stable and reliable clock on the other side. A CMOS clock is not, hence ntpd will reject the source.
What I'm wondering is: is there a way to tell ntpd to be less fussy about the source and just sync it (stepping won't be a problem) without rejecting it?
Ok, so let's rephrase the question: is there a way to tell NTPD to be less fussy and just sync the clock no matter what happens to the remote NTP? Cannot use a schedule instance of ntpdate. I appreciate that ntpd is designed to keep the clock synced to the millisecond, but this is not my need and for several reasons which are out of my reach I cannot change much on my systems.
it's a long story. I can amend the ntp.conf file, but nothing else.
The point is that I understand that when ntpd feels the source clock is unstable, it won't trust it anymore. I had a long conversation on this forum with a very kind forumer about the subject. It makes sense to me, but as said my server does not need to be precise down to the millisecond. I would be happy if it was down to 30 seconds. I agree that stepping time with ntpdate every x minutes would be ideal, but that's not an option. That's why I'm wondering if ntpd can be configured to follow a clock which would normally reject.