Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
1)If your ip was 172.16.86.176, find out your defaultrouter ip or subnet ip, I would presume it will be 172.16.86.1. Add this subnet ip into your /etc/ntp.conf at the end of the page:
server 172.16.86.1 # local clock
restrict 172.16.86.1 noquery nomodify notrap
2)add 172.16.86.1 into /etc/ntp/step-tickers
3)service ntpd restart
4)ntpq -pn to see if it resolved?
Another way is to run rdate -s with 1 of your Unix server.
If you know any Cisco switch's ip that is closed to your server, you can also use that ip to add to those files above. Good luck.
Sorry did not read carefully your questions. Since you did not have network connections, just use the date command. date M/D/H/Minutes. Why would you want to configure ntp to sync with another local server when you don't have network?
When I do date it showed me the time just one half minutes off with the time server, I think this time difference is ok for it to sync? And I change the time of the client clock to match the NTP server time but with no luck ti gives me the same error when I do ntpdate.
I do have a LAN which has several Redhat clients and few Redhat servers and these are not connected to the internet that what I meant (Sorry).
172.16.86.176: Server dropped: strata too high
server 172.16.86.176, port 123
stratum 16, precision -17, leap 11, trust 000
says it all: The server 172.16.86.176 thinks its time is unrelyable.
Just make it "Stratum 3" or so.
Here is the relevant
Originally Posted by file://localhost/usr/share/doc/ntp-doc/html/notes.html
Time is distributed through a hierarchy of NTP servers, with each server adopting a stratum which indicates how far away from an external source of UTC it is operating at. Stratum-1 servers, which are at the top of the pile (or bottom, depending on your point of view), have access to some external time source, usually a radio clock synchronized to time signal broadcasts from radio stations which explicitly provide a standard time service. A stratum-2 server is one which is currently obtaining time from a stratum-1 server, a stratum-3 server gets its time from a stratum-2 server, and so on. To avoid long lived synchronization loops the number of strata is limited to 15.