One more detail form boot log below

On 08/08/2018 09:27 AM, Robert Moskowitz wrote:
This is from the Centos-arm list.

I have this running on a number of Centos7-armfhp Cubieboards.

I have just tested it on Fedora-Minimal-armhfp-Rawhide-20180807.n.0-sda

The result in journalctl -b is below


-------- Forwarded Message --------
Subject: Re: [Arm-dev] Security auditing service
Date: Tue, 7 Aug 2018 10:36:32 +0000
From: Kristján Valur Jónsson <kristjan@rvx.is>
Reply-To: Conversations around CentOS on ARM hardware <arm-dev@centos.org>
To: Conversations around CentOS on ARM hardware <arm-dev@centos.org>


aproppos incorrect time, I wrote a fake-hwclock service for centos, available here:  
https://github.com/kristjanvalur/fake-hwclock


--
Kv,
Kristján Valur Jónsson, RVX

==========================================

Jun 22 11:12:15 localhost kernel: audit: type=1130 audit(1529680335.963:83): pi>
Jun 22 11:12:16 localhost systemd[1]: Received SIGRTMIN+20 from PID 372 (plymou>
Jun 22 11:12:16 localhost systemd[1]: Started Tell Plymouth To Write Out Runtim>
Jun 22 11:12:16 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 s>
Jun 22 11:12:16 localhost kernel: audit: type=1130 audit(1529680336.052:84): pi>
Jun 22 11:12:16 localhost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 se>
Jun 22 11:12:16 localhost kernel: audit: type=1131 audit(1529680336.079:85): pi>
Jun 22 11:12:16 localhost systemd-tmpfiles[610]: [/usr/lib/tmpfiles.d/mdadm.con>
Jun 22 11:12:16 localhost fake-hwclock[607]: 1
Jun 22 11:12:16 localhost fake-hwclock[607]: loading saved time 2018-08-08 08:5>
Aug 08 08:55:48 localhost fake-hwclock[607]: Wed Aug  8 08:55:48 EDT 2018
Aug 08 08:55:48 localhost kernel: audit: type=1130 audit(1533732948.014:86): pi>
Aug 08 08:55:48 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 s>
Aug 08 08:55:48 localhost systemd[1]: Started Fake Hardware Clock.
Aug 08 08:55:48 localhost systemd[1]: Reached target System Time Synchronized.

This gives you real time sooner than Chrony does.

Aug 08 08:55:49 localhost chronyd[641]: chronyd version 3.3 starting (+CMDMON +>
Aug 08 08:55:49 localhost chronyd[641]: Frequency -3.478 +/- 1.341 ppm read fro>
Aug 08 08:55:49 localhost chronyd[641]: Using right/UTC timezone to obtain leap>

...

Aug 08 08:56:28 localhost chronyd[641]: Selected source 108.61.73.243
Aug 08 08:56:28 localhost chronyd[641]: System clock TAI offset set to 37 secon>
Aug 08 08:56:28 localhost chronyd[641]: System clock wrong by 129.951151 second>
Aug 08 08:58:38 localhost chronyd[641]: System clock was stepped by 129.951151 >
Aug 08 08:58:39 localhost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 se>
Aug 08 08:58:45 localhost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 se>
Aug 08 08:59:44 localhost chronyd[641]: Selected source 23.131.160.7
Aug 08 09:03:04 localhost login[695]: pam_unix(login:auth): authentication fail>
Aug 08 09:03:04 localhost audit[695]: USER_AUTH pid=695 uid=0 auid=4294967295 s>
Aug 08 09:03:06 localhost login[695]: FAILED LOGIN 1 FROM ttyS0 FOR root, Authe>
Aug 08 09:03:06 localhost audit[695]: USER_LOGIN pid=695 uid=0 auid=4294967295 >