ntp problems
in [Linux Networking]
|
Prev: ntp problems
Next: gateway setup
From: Bonno Bloksma on 21 Apr 2010 00:41 Hi, >>> I am confused. You have Linux machines on which you want to have >>> accurate ( say better than 1msec) time, and some network devices which >>> you want time to say 1 sec. So on the Linux machines you can run ntpd or >>> chrony with some network sources (eg pool.ntp.org sources). >> >> I'de like to have a good timesource in my network. For those machines/devices capable I would >> like >> those to have a proper time by using the (s)ntp protocol. >> For machines/devices that only understand the old time protocol I want them to be able to use my >> Linux servers as a time source too. The ones using the older time protocol are usualy the ones >> where >> a few (hundred) miliseconds do not matter. >> >>> If your >>> "network devices" only understand the time, not the ntp protocol, you >>> could always run the time servers. >> >> Ok, which daemon do I install on my Linux server so it will provide the local time, which has >> been >> set acurately by the ntp daemon, to other devices via the older time protocol? >> I do NOT want that daemon to modify the time of my Linux servers, it is to use the local time as >> a >> source. >> Did I make more sense this time? >> >>> Not sure what you mean by "entire >>> xinetd environment". You just run one daemon. Or you can run the time >>> daemon directly. >> >> I probably do not know enough about (x)inet, I have allways understood it to be some framework >> that >> launches other daemons. If I don't need the complete framework to run just one daemon then why >> should I do so? Is there an advantage to that? >> >>> Either way. But since the Linux machine is already >>> running ntp, use ntp on the "network devices" or use ntpdate from >>> crontab. It is definitely a second best-- the time becomes a sawtooth, >>> as the local clock is stepped. >> >> You are right, I don't want the local clock modified by the older time protocol daemon. >> >> Bonno Bloksma > > > If your servers are running Debian Lenny, they probably are already > using inetd as the network super-server. > > Check with > > ps -ef > > if there is an inetd process running. > > Then, check the file /etc/inetd.conf for the lines > > time stream tcp nowait root internal > #time dgram udp wait root internal > > If they are like above, the time service is enabled for TCP but > not for UDP. Change the lines as you feel needed and re-start inetd. There was only a tcp line and it was commented out. I now have both a tcp and udp time setup. Restarted inetd and it all works :-) > > The time server takes its reference from the host clock, so it is OK, > if you have a synchronized NTP running on the server. > > I'd set up NTP daemons (ntpd) on all servers, peer them together and > with some outside references. One good candidate is pool.ntp.org. > Yup, that is the way I have it set up. Thanks for all the help, once you know the way it is supposed to be done, it is so simple. But to find out how to do it..... :-) And there wasn't a HOWTO for this, or at least I did not find it. Bonno Bloksma
From: Mart Frauenlob on 21 Apr 2010 03:12 On 21.04.2010 01:48, Sidney Lambe wrote: > My killfile is feeding well on this thread. Another batch of > dickless losers who get their little rocks off insulting people > while they hide behind the Internet. > > Scum like this are a dime-a-dozen on the Usenet. > > Sid You're so full of hate, it really is sad to see :/ Don't you see, you are the one insulting in the first place in all the posts I've read from you yet. Then people react on you with insulting back, which causes more insulting from you, and so on.... Will it ever stop? Do you want to spend the rest of your life in flame-wars? I got some homework for you! Every time you are about to insult someone, rest for a moment, and write the exact opposite. Write as friendly, respectful and loving as you can. See if it changes things... Wish u well Mart
From: Jon Solberg on 21 Apr 2010 03:20 On 2010-04-21, Mart Frauenlob <mart.frauenlob(a)chello.at> wrote: > On 21.04.2010 01:48, Sidney Lambe wrote: > >> My killfile is feeding well on this thread. Another batch of >> dickless losers who get their little rocks off insulting people >> while they hide behind the Internet. [...] > > You're so full of hate, it really is sad to see :/ [...] ___________________________ /| /| | | ||__|| | Please don't | / O O\__ feed | / \ the trolls | / \ \ | / _ \ \ ---------------------- / |\____\ \ || / | | | |\____/ || / \|_|_|/ | __|| / / \ |____| || / | | /| | --| | | |// |____ --| * _ | |_|_|_| | \-/ *-- _--\ _ \ // | / _ \\ _ // | / * / \_ /- | - | | * ___ c_c_c_C/ \C_c_c_c____________ -- Jon Solberg (remove "nospam." from email address)
From: Sidney Lambe on 21 Apr 2010 04:29 On comp.os.linux.networking, Sidney Lambe <sidneylambe(a)nospam.invalid> wrote: > On comp.os.linux.networking, David Schwartz <davids(a)webmaster.com> wrote: >> On Apr 19, 5:26=A0pm, Sidney Lambe <sidneyla...(a)nospam.invalid> wrote: >> >>> >> And if rdate -p 127.0.0.1 fails that there is a problem? >> >>> > It would be surprising if it succeeded since most Linux boxes >>> > stopped supporting that protocol around the same time they >>> > stopped running 'inetd' by default. >> >>> You are mistaken. It comes with the latest Debian, for starters: >>> >>> http://packages.debian.org/lenny/rdate >>> >>> (This will work just fine on any distro. Is a simple utility >>> needing only the basic libs to function.) >> >> Even if you have 'rdate', 'rdate -p 127.0.0.1' will fail if you're not >> running the 'rdate' server. When most distributions stopped enabling >> 'inetd' by default, they generally also stopped providing 'rdate' >> service by default. This applies whether or not you have a client or >> server installed. > > I don't run a timeserver here. I set the gateway computer's clock > using rdate and then use scripts calling date on the other > boxes on the LAN to read and set their time from the gateway > box. I just discovered my memory was faulty. Each box on the LAN hits the pool once an hour at different times using rdate. Been working just fine for years. The orignal scripts that worked as described above are in the same file, commented out. Don't remember when I abandoned them. I laughed when I read the OP saying that it was all so simple. Right. Everything is once you know how to do it. Sure didn't seem simple to him when he posted here after being unable to make it work for so long. And ntpd sure isn't simpler than cron calling simple rdate scripts. I've never had ANY problems and never will. And it takes a tiny fraction of the system resources by comparison. Sid
From: Sidney Lambe on 21 Apr 2010 05:08
On comp.os.linux.networking, unruh <unruh(a)wormhole.physics.ubc.ca> wrote: > On 2010-04-19, Bonno Bloksma <bbloksma(a)xs4all.nl> wrote: >> Hi, >> >> Using Debian Lenny, default install of ntp on several servers. >> The only change applied on most servers is to add a line to a nearby startum 2 server. >> Somehow is looks as if the ntp server is running ok but clients cannot connect. >> >> Can I assume rdate is a proper ntp client? > > No. rdate has absolutely nothing to do with ntp. It is an ancient time > deamon/proceedure. > > >> And if rdate -p 127.0.0.1 fails that there is a problem? > > No, rdate has nothing to do with ntp. It does NOT use the ntp protocol. > YOu could try ntpdate. > > From man rdate: -n Use SNTP (RFC 2030) instead of the RFC 868 time protocol. Open mouth, insert foot. And this is the second time (at least) this has been posted on this thread. Sid |