similar to: What besides Postfix should not start until system time set?

On 04/20/2017 05:16 PM, Warren Young wrote: > On Apr 20, 2017, at 3:00 PM, Robert Moskowitz <rgm at htt-consult.com> wrote: >> So I have learned that Postfix should delay until Chronyd has moved the system time from 0 to current. > I think it?s more the case that CentOS is written with the assumption that you?re running it on a host with a battery-backed RTC, so that system time

________________________________________ From: Robert Moskowitz [rgm at htt-consult.com] Sent: Thursday, April 20, 2017 5:00 PM To: CentOS mailing list Subject: [CentOS] What besides Postfix should not start until system time set? > > So I have learned that Postfix should delay until Chronyd has moved the > system time from 0 to current. Something you might consider to make the

I have read: http://thegeekdiary.com/centos-rhel-7-chrony-vs-ntp-differences-between-ntpd-and-chronyd/ My server is up all the time and will serve time to internal systems (via DHCP options). Caveat is that my server is an armv7 (Cubieboard2) which does not have an RTC (no battery). So whenever the system boots, the time is ZERO (Dec 31, 1969 or some such). Chrony fixes this really fast;

On 05/02/17 16:15, Richard wrote: > >> Date: Sunday, February 05, 2017 10:26:05 -0500 >> From: Robert Moskowitz <rgm at htt-consult.com> >> >> I have read: >> http://thegeekdiary.com/centos-rhel-7-chrony-vs-ntp-differences-bet >> ween-ntpd-and-chronyd/ >> >> My server is up all the time and will serve time to internal >> systems (via

> Date: Sunday, February 05, 2017 10:26:05 -0500 > From: Robert Moskowitz <rgm at htt-consult.com> > > I have read: > http://thegeekdiary.com/centos-rhel-7-chrony-vs-ntp-differences-bet > ween-ntpd-and-chronyd/ > > My server is up all the time and will serve time to internal > systems (via DHCP options). > > Caveat is that my server is an armv7

Hi All, Just noticed a funny time jump on a testing CentOS 7 VM. Specifically the system time jumps around by a few hours during system boot. The below is a selection from /var/log/messages during boot: Jan 19 12:49:57 arr-data-dev chronyd[716]: Frequency -0.829 +/- 0.007 ppm read from /var/lib/chrony/drift Jan 19 12:49:57 arr-data-dev polkitd[720]: Started polkitd version 0.112 Jan 19

On Apr 20, 2017, at 3:00 PM, Robert Moskowitz <rgm at htt-consult.com> wrote: > > So I have learned that Postfix should delay until Chronyd has moved the system time from 0 to current. I think it?s more the case that CentOS is written with the assumption that you?re running it on a host with a battery-backed RTC, so that system time isn?t wildly off at boot time. This includes VMs,

On 12/28/16, 3:28 PM, "CentOS on behalf of Robert Moskowitz" <centos-bounces at centos.org on behalf of rgm at htt-consult.com> wrote: On 12/28/2016 06:13 PM, Greg Cornell wrote: > On 12/28/16, 3:09 PM, "CentOS on behalf of Robert Moskowitz" <centos-bounces at centos.org on behalf of rgm at htt-consult.com> wrote: > > > > On 12/28/2016 06:05 PM, J

I am trying to hwclock to set the time. (hwclock -w) this is what I get on standard 5.2 x86_64. hwclock --debug hwclock from util-linux-2.13-pre7 hwclock: Open of /dev/rtc failed, errno=19: No such device. No usable clock interface found. Cannot access the Hardware Clock via any known method. [root at devcentos5x64 src]# ls -l /dev/rtc crw------- 1 root root 10, 135 Feb 6 13:32 /dev/rtc Any

I am getting this error: hwclock --debug hwclock from util-linux-2.13-pre7 hwclock: Open of /dev/rtc failed, errno=16: Device or resource busy. No usable clock interface found. Cannot access the Hardware Clock via any known method. [root at devcentos5x64 src]# uname -a Linux devcentos5x64.msgnet.com 2.6.18-128.el5 #1 SMP Wed Jan 21 10:41:14 EST 2009 x86_64 x86_64 x86_64 GNU/Linux rpm -qa | grep

AFAIK the only thing needed to make your host an NTP server using chrony is to set the allow line to the network address in CIDR format of the network you want to be served, and uncomment it. The restart chronyd. You also need to ensure that port 123 (NTP) is open to your internal network on your filrewall. I have a CentOS 6 box that is an NTP server for my network. CentOS 7 works the same

This is for centos 7 that has chronyd 2.1.1 I am looking into how to use chronyd as my local ntp server. On my old servers with ntpd I had local access control lines like: restrict 192.168.128.0 mask 255.255.255.0 nomodify notrap But in looking for documentation on chronyd I did not find anything on this at: https://chrony.tuxfamily.org/doc/2.1/manual.html In the actual /etc/chronyd.conf

Hi all, I am having an issue with some older CentOS 5.3 servers. Every time the server boots, it gives the error "Cannot access the hardware clock by any known method", and then promptly sets the time 5 hours behind the hardware clock, down to the second. After the system is up. "hwclock" works fine. hwclock --debug does not show any error at all. The hardware clock is

On 28/05/17 23:56, Leon Fauster wrote: >> Am 28.05.2017 um 12:16 schrieb Robert Moskowitz <rgm at htt-consult.com>: >> >> >> >> On 05/28/2017 04:24 AM, Tony Mountifield wrote: >>> In article <792718e8-f403-1dea-367d-977b157af82c at htt-consult.com>, >>> Robert Moskowitz <rgm at htt-consult.com> wrote: >>>> On 05/26/2017

> Am 29.05.2017 um 05:46 schrieb Robert Moskowitz <rgm at htt-consult.com>: > > > > On 05/28/2017 06:57 PM, Rob Kampen wrote: >> On 28/05/17 23:56, Leon Fauster wrote: >>>> Am 28.05.2017 um 12:16 schrieb Robert Moskowitz <rgm at htt-consult.com>: >>>> >>>> >>>> >>>> On 05/28/2017 04:24 AM, Tony

My Centos7 system does not have a battery for the clock (like most armv7 SOCs), thus I rely on that at some point in boot time, chronyd sets the time. If a file is updated prior to chronyd accomplishing its task (or network connectivity is down), the file ends up with a timestamp of "Dec 31 1969". I notice that occasionally, after a reboot, /etc/aliases.db reverts to this time,

Hi all, One of our domU VMs (CentOS 5.6 x86_64) runs a cobol application, which in turn called ''clock'' to get timestamps. Changing this is non-trivial. When I try to call ''clock --debug'' I get: [root@vm0010 ~]# clock --debug hwclock from util-linux-2.13-pre7 hwclock: Open of /dev/rtc failed, errno=19: No such device. No usable clock interface found.

Hi there! I just fresh-installed Xen on new server, Xeon E5-2620, and noticed following thing: node1 ~ # xl info -n host : node1 release : 3.8.8 version : #1 SMP Tue Apr 23 20:54:17 MSK 2013 machine : x86_64 nr_cpus : 6 max_cpu_id : 5 nr_nodes : 1 cores_per_socket : 6 threads_per_core

Hi, I'm seeing the following issue when attempting to update the guest's clock on a running fc32 guest (using guest agent): ``` [root@virt-launcher-vmi-masquerade-mh2xm /]# virsh domtime 1 --pretty Time: 2020-04-30 23:27:29 [root@virt-launcher-vmi-masquerade-mh2xm /]# virsh domtime 1 --sync error: internal error: unable to execute QEMU agent command 'guest-set-time': hwclock

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.16.1"> </HEAD> <BODY> Hello All, I have a problem with hwclock on centos 5.3. in xen guest environment<FONT