What would be the equivalent of command " # timedatectl set-ntp true " of arch linux in Obarun to synchronize time?
i don't know what this Fu@ ^@ ~ system:D command do, i guess you want to use ntpd.
simply (as root)
# pacman -S openntpd ntpd-s6serv
then enable the service
# s6opts enable ntpd
eric wrotei don't know what this Fu@ ^@ ~ system:D command do, i guess you want to use ntpd.
simply (as root)
# pacman -S openntpd ntpd-s6serv
then enable the service
# s6opts enable ntpd
Thank you dear eric but this did not help , my system time is not accurate,not synchronizing . Any further suggestionsplease?
Fixed time synchronization by putting following contents into the ntpd.conf file

# $OpenBSD: ntpd.conf,v 1.14 2015/07/15 20:28:37 ajacoutot Exp $
#
# See ntpd.conf(5) and /etc/examples/ntpd.conf

servers pool.ntp.org
sensor 0.0.0.0
constraints from "https://www.google.com"

# Associate to public NTP pool servers; see http://www.pool.ntp.org/
server 0.pool.ntp.org iburst
server 1.pool.ntp.org iburst
server 2.pool.ntp.org iburst
server 3.pool.ntp.org iburst

listen on *

Hope these are corretc
3 months later
I don't get it

If you add those 4 servers in /etc/ntpd.conf you get errors

The site talks about a /var/lib/ntp/ntp.drift file

If you have figured it out let me know
/var/lib/openntpd/db/ntpd.drift

but still I get

$ sudo ntpd
constraint configured without libtls support

and don't know where to get libtls support
just use the default servers
servers pool.ntp.org
in your /etc/ntpd.conf or use one from this list http://www.pool.ntp.org/zone/@ . comment your constraints line if you don't want the warning. This warning is given because you don't use libressl, see the patch here : https://github.com/openntpd-portable/openntpd-portable/blob/master/patches/0009-Notify-the-user-when-constraint-support-is-disabled.patch.

Note : https://wiki.archlinux.org/index.php/OpenNTPD
10 days later
I have been fighting this for a while now and I have just given up.
My s6.conf on the time zone has the correct time zone, the ntpd starts and stops fine, when I start it it synchronizes the clock but always takes it to UTC, no matter what I do. It must be hw related as in all other boxes I don't have such a problem.
a year later
I am re-activating this old thread

I have following packages installed on current Obarun
openntpd and openntpd-66serv

How do I enable and make openntpd to synchronize time for me?
openntpd never worked for me in the past, I used ntpclient, but recently JM worked on ntp and now I use ntpd and it works great all the time.
As root and having root as your tree that is active,
# 66-enable -t root -C -S openntpd
Give it a few minutes. If it doesn't work try ntpd
# 66-disable -t root -S openntpd
# pacman -Rnsu openntpd-66serv openntpd
# pacman -S ntpd-66serv
# 66-enable -t root -C -S ntpd
fungalnet wroteopenntpd never worked for me in the past, I used ntpclient, but recently JM worked on ntp and now I use ntpd and it works great all the time.
As root and having root as your tree that is active,
# 66-enable -t root -C -S openntpd
Give it a few minutes. If it doesn't work try ntpd
# 66-disable -t root -S openntpd
# pacman -Rnsu openntpd-66serv openntpd
# pacman -S ntpd-66serv
# 66-enable -t root -C -S ntpd
This did not help , system time is still not correct
Have you edited your /etc/66/boot.conf
there are 2 time related variables.
Example:


# # Set RTC [UTC|localtime]. <------ 2 options
HARDWARECLOCK=localtime
# # Set timezone, availables timezones at /usr/share/zoneinfo.
TZ=Asia/Jakarta
  • [deleted]

Hi saleem

ntpd exits with a message to the system log if the offset exceeds the panic threshold, which is 1000 s by default.
So, the first time, add the option -g to the environment variable and remove it after that.
fungalnet wroteHave you edited your /etc/66/boot.conf
there are 2 time related variables.
Example:


# # Set RTC [UTC|localtime]. <------ 2 options
HARDWARECLOCK=localtime
# # Set timezone, availables timezones at /usr/share/zoneinfo.
TZ=Asia/Jakarta
Yes I had set these two settings prior to enabling ntpd
jean-michel wroteHi saleem

ntpd exits with a message to the system log if the offset exceeds the panic threshold, which is 1000 s by default.
So, the first time, add the option -g to the environment variable and remove it after that.

Hello jean-michel

I will check this and report back
5 months later
Old issue still persists

did this

# pacman -S ntpd-66serv
# 66-enable -t root -C -S ntpd

then did this to /etc/ntp.conf file

server 0.pool.ntp.org iburst
server 1.pool.ntp.org iburst
server 2.pool.ntp.org iburst
server 3.pool.ntp.org iburst

TZ is set to

TZ=Asia/Karachi

removed connman and installed/enabled networkmanager because I read somewhere that connman does not sysnchronize time

Despite all these steps my clock is not synchronizing

any more suggestions please?
Those servers is part of an international pool of servers and didn't work for me either, but closer/local ones did.
So edit your /etc/ntp/ntpd.conf

From: https://www.pool.ntp.org/zone/in

server 0.in.pool.ntp.org
server 1.in.pool.ntp.org
server 2.in.pool.ntp.org
server 3.in.pool.ntp.org

or from https://www.pool.ntp.org/zone/pk

server 0.asia.pool.ntp.org
server 1.asia.pool.ntp.org
server 2.asia.pool.ntp.org
server 3.asia.pool.ntp.org


Somehow I found out it helps to get started by setting the date manually to something close https://time.is
# date 012420402020.48 --> MMDDhhmmyyyy.ss Month Day hour minute year. seconds

Check back in a few minutes, it must have synchronized
22 days later
@ 400000005e47b42405783fb9 15 Feb 11:03:59 ntpd[974]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
@ 400000005e47c01f3539268f 15 Feb 11:55:06 ntpd[974]: frequency file /var/lib/ntp/ntp.drift.TEMP: Permission denied

66-stop/66-start
@ 400000005e47c5b717612ff8 15 Feb 12:18:58 ntpd[4809]: format error frequency file /var/lib/ntp/ntp.drift

Powered by Obarun