You are not logged in.
Pages: 1
I can't seem to set the proper time for my system(trying to use Openntpd)
rc.conf(top config):
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="US/Pacific"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
Openntpd setup:
# $OpenBSD: ntpd.conf,v 1.7 2004/07/20 17:38:35 henning Exp $
# sample ntpd configuration file, see ntpd.conf(5)
# Addresses to listen on (ntpd does not listen by default)
#listen on *
#listen on 127.0.0.1
#listen on ::1
# sync to a single server
#server ntp.example.org
# use a random selection of 8 public stratum 2 servers
# see http://twiki.ntp.org/bin/view/Servers/NTPPoolServers
#servers pool.ntp.org
server 0.us.pool.ntp.org
server 1.us.pool.ntp.org
server 2.us.pool.ntp.org
server 3.us.pool.ntp.org
Daemons:
DAEMONS=(syslog-ng !network netfs crond @acpid @alsa @openntpd @sshd @hal @fam wicd cups gdm)
Ask if you need any more details on my setup, thanks!
Offline
Not quite clear what your problem is. You cannot set the time at all? Or you don't get the proper time displayed?
In the latter case you may try if deleting /var/lib/hwclock/adjtime helps. It should contain a rather low correction value. You may also search the forum, there were several threads concerning time setting problems.
BTW, you should change your DAEMONS line to
DAEMONS=(syslog-ng hal !network netfs crond @acpid @alsa @openntpd @sshd @fam wicd cups gdm)
I.e. hal should be started as soon as possible and not be backgrounded as its services are needed by many daemons started afterwards.
Last edited by bernarcher (2009-08-11 20:55:27)
To know or not to know ...
... the questions remain forever.
Offline
Along the same lines as bernarcher went; you also have your network management daemon 'wicd' starting up after a couple of network reliant services, 'openntpd' and 'sshd'. I'd perhaps move my 'wicd' entry to earlier in the list and not background it (to make sure the network is up an working when 'openntpd' and 'sshd' are started).
My daemons array is currently like:
DAEMONS=(syslog-ng hal !network wicd alsa netfs openntpd crond cpufreq)
and includes both the 'openntpd' and 'wicd' daemons. This is a pretty stripped down installation as you can see and I don't even have any daemons being started backgrounded yet (that will probably change - it is quite a fresh install). I'll certainly background the 'openntpd' daemon because it causes quite a delay in my startup time (possibly 10 secs).
For completion here is my /etc/ntpd.conf (unchanged from original)
# $OpenBSD: ntpd.conf,v 1.7 2004/07/20 17:38:35 henning Exp $
# sample ntpd configuration file, see ntpd.conf(5)
# Addresses to listen on (ntpd does not listen by default)
#listen on *
#listen on 127.0.0.1
#listen on ::1
# sync to a single server
#server ntp.example.org
# use a random selection of 8 public stratum 2 servers
# see http://twiki.ntp.org/bin/view/Servers/NTPPoolServers
servers pool.ntp.org
and the localization section from my /etc/rc.conf
LOCALE="en_GB.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="Europe/London"
KEYMAP="uk"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
Everything here works great so I hope something here helps you get yours working correctly.
Offline
According to the wiki and personal experience, openntpd should NOT be backgrounded because it may cause the time to be set incorrectly. For some people it works fine, but if you're having problems try starting it in the foreground.
Offline
Hello.
I got the same problem before just type:
date time that you want to have
Last edited by SpeedVin (2009-08-12 08:54:58)
Shell Scripter | C/C++/Python/Java Coder | ZSH
Offline
Ok I moved my daemons array around..moving both hal(second in the array) and openntpd(after wicd, because wicd starts the network)
I'll report back if any failures, right now it says 12:56AM
Offline
Pages: 1