Thread: Bounty - Date/Time/NTP module for trixbox front-end

You're right, I wasn't really thinking and I gave bad advice -- good call. This did get me looking, though, and I never did before. It looks like ntpd is installed and enabled by default in trixbox 2.4, at least. As long as you set your time in your system bios to something within a few minutes of the "real" time before install, and set your time zone correctly it should synchronize with the Internet. It uses the ntp pool...

The NTP service should always keep the time correct. Are you running trixbox in a Virtual Machine or something?

what if you do this and wait a bit then type ntpq -p and the * is next to local instead? does this mean it is only syncing w/ the bios? if so how do we eliminate looking at the bios and only use online syncing?

Yes, and I can also run yum -y update from the command line, so what's the point of the package manager in trixbox? It's all about ease of use and consolidation. If I am sitting at the main trixbox screen and realise the time isn't right, why should I go run a terminal to log in when I can just open the time/date module and click "Refresh" or whatever? Time is money, as the saying goes .. and anything which can be...

An NTP daemon that continuously keeps the time in sync in the background is a much better option. When you run a cron job once a day (or even more often) you will have sudden jumps in time (even if only a second or two), which is absolutely NOT what you want on an Asterisk system!! It can cause unexpected behaviour and of course, things like CDRs, billing etc. are affected by it as well. So, better do this right and use a daemon that...

This has been my preferred method for years in a Linux environment. Very simply, non-bulky. I just create a file in /etc/cron.weekly pico /etc/cron.weekly/update_time #!/bin/sh TIMESERVER="time-b.nist.gov" rdate -s $TIMESERVER > dev/null 2> &1 hwclock --systohc > dev/null 2> &1 Save the file and then give it permission... chmod 755 /etc/crons.weekly/update_time

Hello, My Trixbox server is losing time (about 30 sec a day) from the actual time. By doing Kodak's suggestion above: service ntpd stop ntpdate -u 0.pool.ntp.org service ntpd start then, to seal the deal, after it synchronizes do: hwclock --systohc this works, however the Trixbox time and the server time doesn't stay synced (still loses about 30 sec a day from when I have done this). I then took another suggestion above, by creating...

If you're running xen read through this website to correct time in the Dom0 otherwise time will be off. http://www.hanckmann.net/?q=node/29