• [deleted]

  • Post #1
ntp and ntp-66serv has been updated.

# ntp changelog:
ntp.conf was rewritten to make it a little more easy to read and to understand.
/var/lib/ntp now owned by the group ID 'ntp'

# ntpd-66serv changelog:
add -g option: Allow the first adjustment to be Big

IMPORTANT

According pacman manual page, --overwrite should works on an empty directory, but it's not the case.
That mean after the update /var/lib/ntp group ID will not be corrected even if your /var/lib/ntp dir. is empty.

Recommended way is to change the owner group manually if your /var/lib/ntp contain files
chown ntp:ntp /var/lib/ntp
or if your /var/lib/ntp is empty just remove the ntp folder and update.

NOTE
Wait around one minut to get your local clock synchornized to the remote servers.

  • [deleted]

  • Post #2
update, yes again , but it's testing :P

First, ntp now run with userid:groupid ntp.
This is a good default choice for security.

Second,
I made a wrong decision about the -g option. I explain.
ntpd exits with a message to the system log if the offset exceeds the panic threshold, which is 1000 s by default.
When I decided to set this option I was thinking about some board like cubieboard without onboard RTC support.
However 66 and all the flexibility offered for the user make things simpler with 66-env.

The choice we have to made for a default service configuration is not easy, it must work but our choices must not prevail over those of the user.
Thx 66, thx eric for this awesome tools :)

Powered by Obarun