Launchctl Error Unloading Org.ntp.ntpd
enter a title. You can not post a blank message. Please type your message and try again. This discussion is locked Virgule Level 1 (55 points) Q: Bogus ntpd does not respect Date & Time setting /usr/sbin/ntpd regularly connect to time.apple.com even tho the "Set date and time automatically" is disabled in the System Preferences panel. It performed 3 time resets within the last 24 hours alone.I would very much like to know why...Thanks you very much in advance.signed, Andrew from Canada Core Duo Mac Mini, Mac OS X (10.5.6), iPod touch 8GB Posted on Mar 16, 2009 5:03 PM I have this question too Close Q: Bogus ntpd does not respect Date & Time setting All replies Helpful answers by Virgule, Virgule Mar 16, 2009 5:22 PM in response to Virgule Level 1 (55 points) Mar 16, 2009 5:22 PM in response to Virgule oh my.. the Date & Time panel does not even use ntpd. It use ntpdate. Is there anything left working as expected around here? :POriginal question remain: Why is ntpd doing it's thing many times per day even tho I disabled this function long ago? Helpful (0) Reply options Link to this post by R C-R, R C-R Mar 17, 2009 4:26 AM in response to Virgule Level 6 (17,700 points) Mar 17, 2009 4:26 AM in response to Virgule Virgule wrote:Original question remain: Why is ntpd doing it's thing many times per day even tho I disabled this function long ago?This is probably not really a topic best discussed in the Mac OS X v10.5 Leopard > Installation and Setup forum, but for starters, how specifically did you disable ntpd? Have you read the man pages for ntpd, ntpdate, & ntp.conf & checked or changed any associated files? Where specifically do you see indications that ntpd is "doing it's thing"? Helpful (0) Reply options Link to this post by Virgule, Virgule Mar 17, 2009 8:49 AM in response to R C-R Level 1 (55 points) Mar 17, 2009 8:49 AM in response to R C-R I did my best to post in the most appropriate subforum.
the date and time on the with the date and time commands every once in a while? Just like a cheap watch, the clock chip really wasn't very accurate so you were trained to accept the need to correct the clock periodically. In the mid-90's or so, you first connected to the Internet and computers could synchronize clocks across the network. Remember the old rdate command in Unix? Yeah, good times.Long before then, D. L. Mills wrote RFC-958, "Network Time Protocol (NTP)", and started what has become the de facto standard technique for synchronizing computers across networks. It's become so prevalent https://discussions.apple.com/thread/1943551?start=0&tstart=0 that even Windows includes an NTP client! (Of course with Windows, you configure it with some crazy registry settings instead of sensible config files.) NTP has matured to the point where most computer users don't think twice about the computer's clock because it just works.But, why do we care how accurate the computer's clock truly is? We're not measuring particle physics experiments here, I'm just reading emails! Well, maybe one or more http://www.atmythoughts.com/living-in-a-tech-family-blog/2014/2/28/what-time-is-it of these reasons might be something you care about:So the kids can’t use the computer’s clock as excuse for not: showering, feeding the pets, getting homework done, going to bed.Some network applications are sensitive to gross time differences between computer clocks.It’s 2014 and the clock on the VCR is still flashing -Blinking twelve problem. We have the technology to do better than this.Symptoms on Mac OS XOut of the boxI think we all expect modern operating systems to arrive with a reasonably good default configuration that gets you up and running quickly. Fresh out of the box, your Apple computer is a pretty quick study and only asks a few basic questions before it's connected to the Net. Computer clock synchronization is straightforward and Mac OS X does have reasonable default settings. Your Mac running Mavericks synchronizes with a region-specific Apple Network Time Protocol server. In my case, that is time.apple.com which is a fine NTP server. Note that the time.apple.com FQDN represents a pool of NTP servers. Execute “dig +short time.apple.com” to see evidence of that. Your Mac boots up, starts the NTP process, and your computer’s clock synchronizes without any work on your part. No more blinking twelves.Unfortunately, your Mac will not remain in sync for long. While setting up my
inHidden fieldsSearch for groups or messages