Accidentally, I fell asleep and my Porteus box was kept running, and that in the night of Summertime +1 hour switching back to Normal Time aka Wintertime +/-0 hour. Curious as I am, I wanted to see some log info when my system adjusted its time. When I awoke one of my radio controlled clocks received the info and adjusted itself to 03:12 - while the other digital clock in the bedroom where my Linux box also sits kept saying 04:12.
Porteus also adjusted its time and showed 03:12.
But /var/log/messages not shows any info on adjusting the time. Here are the complete logs. I just shortened the 4 dbus-daemon entries about "Activating service name='org.freedesktop.thumbnails.Thumbnailer1'" since I presume they are of no consequence in this matter.
Code: Select all
Oct 30 23:28:09 porteus syslogd[706]: -- MARK --
Oct 30 23:48:09 porteus syslogd[706]: -- MARK --
Oct 31 00:08:09 porteus syslogd[706]: -- MARK --
Oct 31 00:28:09 porteus syslogd[706]: -- MARK --
Oct 31 00:48:09 porteus syslogd[706]: -- MARK --
Oct 31 01:08:09 porteus syslogd[706]: -- MARK --
Oct 31 01:24:12 porteus dbus-daemon[1705]: […]
Oct 31 01:24:13 porteus dbus-daemon[1705]: […]
Oct 31 01:38:22 porteus dbus-daemon[1705]: […]
Oct 31 01:38:22 porteus dbus-daemon[1705]: […]
Oct 31 02:08:09 porteus syslogd[706]: -- MARK --
Oct 31 02:28:09 porteus syslogd[706]: -- MARK --
Oct 31 02:48:09 porteus syslogd[706]: -- MARK --
Oct 31 02:08:09 porteus syslogd[706]: -- MARK --
Oct 31 02:28:09 porteus syslogd[706]: -- MARK --
Oct 31 02:48:09 porteus syslogd[706]: -- MARK --
Oct 31 03:08:09 porteus syslogd[706]: -- MARK --
Code: Select all
root 38707 2021-10-30 17:23 Xorg.0.log
root 5339 2021-10-30 17:23 debug
root 23394 2021-10-30 17:37 syslog
root 1835 2021-10-30 19:30 cron
root 410124 2021-10-31 03:39 messages
_________________________________________
And why is porteus syslogd[706] putting its "-- MARK --" always at the exact same time?
Should it not adjust to the 20 minutes after another process posted its log?
Here "Oct 31 01:38:22 porteus dbus-daemon[1705]" being that log. Why is "syslogd[706]" not adjusting its 20 minutes and printing its next --MARK-- at "Oct 31 01:58:23" ?
The only time "mark" is mentioned in man syslogd(8) is this:
Code: Select all
-m interval
Select the number of minutes between “mark” messages; the default
is 20 minutes. Setting this to zero disables log marks.
Fun fact: while I received no answer here, due to the need of rebooting ( "Loading vmlinuz... failed. Bad file number" ) my hardware clock was again … "adjusted" - of course this time from the already correct Western European Winter time - to one hour too much.
![Wall :wall:](./images/smilies/wall.gif)
Still no clue which system part being responsible…
![Crazy :crazy:](./images/smilies/crazy.gif)
At least this year's winter time adjustment keeps me entertained.