ntp problems
in [Linux Networking]
|
Prev: wireless WOL
Next: ntp problems
From: Mart Frauenlob on 20 Apr 2010 05:09 On 20.04.2010 10:35, Peter K�hlmann wrote: > Mart Frauenlob wrote: > >> On 20.04.2010 03:42, Sidney Lambe wrote: >> [...] >>> >>> Another fatheaded idiot telling me that something I have been doing >>> successfully for years doesn't work. >>> >>> I have just given him the score that tells me that his technical >>> advice is to be approached with caution. >>> >>> Sid >> >> Why are you so auto-aggressive? >> Why do you need to start flaming all the time? > > Simple: He is Alan Connor > > Easily one of the dumbest kooks on usenet of all time Well, that's just the negative projection in the reverse direction. Don't judge one as an idiot for judging others as idiots. You'd do just the same. That's moving around the hate. Characters are not static, they can change. Most likely this person didn't get enough love in hist life. Calling him dumb cannot create a constructive reaction.
From: Peter Köhlmann on 20 Apr 2010 06:07 Mart Frauenlob wrote: > On 20.04.2010 10:35, Peter Köhlmann wrote: >> Mart Frauenlob wrote: >> >>> On 20.04.2010 03:42, Sidney Lambe wrote: >>> [...] >>>> >>>> Another fatheaded idiot telling me that something I have been doing >>>> successfully for years doesn't work. >>>> >>>> I have just given him the score that tells me that his technical >>>> advice is to be approached with caution. >>>> >>>> Sid >>> >>> Why are you so auto-aggressive? >>> Why do you need to start flaming all the time? >> >> Simple: He is Alan Connor >> >> Easily one of the dumbest kooks on usenet of all time > > Well, that's just the negative projection in the reverse direction. > Don't judge one as an idiot for judging others as idiots. Just read "Sidneys" history in other newsgroups. He *is* Alan Connor. And that twit is easily one of the dumbest kooks in usenet history > You'd do just > the same. That's moving around the hate. > Characters are not static, they can change. > Most likely this person didn't get enough love in hist life. Well, I guess even his mother would be disgusted by that guy > Calling him dumb cannot create a constructive reaction. It is just the most polite way to describe "Sidney". He isn't smart. Dirt has a higher IQ -- I say you need to visit Clues 'R' Us. They are having a special on slightly used clues.
From: Bonno Bloksma on 20 Apr 2010 10:30
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 |