Console spam: "com.apple.time: Interval maximum value"

It's an artifact caused by the 10.8.4 update. Ignore.

I don't know when it will be cleared up, but yes.

still there in mavericks.

Still in Mavericks as of 10.9.1.

This may be an actual fix: http://apple.stackexchange.com/questions/112679/ntpd-not-updating-time

Though, it turns out that deleting the SystemConfiguration folder did not help in my case, nor did another reboot with PRAM-Reset (held down opt-cmd-p-r for 3 reboots). Maybe it's important to first reset PRAM and only then delete that folder, but I'm not eager to go thru this again right now. If you try, make sure to follow that order and let us know if it helped.

The specified value, https://en.wikipedia.org/wiki/9223372036854775807, is the maximum signed 64-bit integer -- this may help the com.apple.time issue for Apple?

Ok, after digging a bit, I've found what cause this warning: the DOT @ the end of the NTP server name... I thing it is used to specify the interval from the GUI, but without a value (i.e. Apple, Europe, (time.euro.apple.com.)) it probably fall to the maximum signed int64 value.

If you trim that dot or specify a value after the dot, the warning goes away.

Moreno

Edit: I now have these console errors... sandbox...:

07/08/14 10:06:33,415 sandboxd[158]: ([196]) ntpd(196) deny file-read-data /private/var/run/resolv.conf

07/08/14 10:06:33,419 sandboxd[158]: ([196]) ntpd(196) deny file-read-data /private/var/run/resolv.conf

07/08/14 10:08:35,827 sandboxd[158]: ([196]) ntpd(196) deny file-read-data /private/var/run/resolv.conf

07/08/14 10:08:35,831 sandboxd[158]: ([196]) ntpd(196) deny file-read-data /private/var/run/resolv.conf

07/08/14 10:12:37,845 sandboxd[158]: ([196]) ntpd(196) deny file-read-data /private/var/run/resolv.conf

07/08/14 10:12:37,849 sandboxd[158]: ([196]) ntpd(196) deny file-read-data /private/var/run/resolv.conf

Ok, removed also the sandbox errors by allowing read access to resolv.conf in /System/Library/Sandbox/Profiles/system.sb.

Now ntpd sync fine and no more errors about com.apple.time interval.

l0v3r

I am a bit of an OS X numpty, so can I just check - did you simply edit system.sb with Nano or something and add resolv.conf to the allowed files list?

Presumably under "Allow access to special files"?

Sorry for delay,

I copied system.db somewhere in my user folder, such in Desktop, than edited with textedit; but you can simply edit it with nano from console if you prefer.

In system.db I added resolv.conf to the end of "allow file-read*" section in this way:

;;; Allow access to standard special files.

(allow file-read*

(literal "/dev/autofs_nowait")

(literal "/dev/random")

(literal "/dev/urandom")

(literal "/private/etc/master.passwd")

(literal "/private/etc/passwd")

(literal "/private/var/run/resolv.conf"))

The only downside is that after a system update the file revert back to system default and you need to apply the change again.

Cheers

Where in system.sb is this dot to be removed?

Eleanor

I'm just here to say the problem still exists in 10.9.5. Can anyone say if it's fixed in 10.10?