There is some evidence that the system updates the hwclock, but keeping the command to copy the system time to the RTC until that is better understood. Does this need to be in the shutdown script?
we have /udev script as well, what is running that?
Better cleanup of fake hwclock:
sudo apt-get remove fake-hwclock
sudo update-rc.d -f fake-hwclock remove
sudo rm /etc/fake-hwclock.data
Better pd-status using:
timedatectl status
To debug logs need setting in conf file and create directory to get it to work:
sudo nano /etc/systemd/journald.conf
Storage=persistent
AND
sudo mkdir -p /var/log/journal THEN reboot
question: sudo apt-get install bootlogd needed? not completely sure on this one
https://www.digitalocean.com/community/tutorials/how-to-use-journalctl-to-view-and-manipulate-systemd-logs
There is some evidence that the system updates the hwclock, but keeping the command to copy the system time to the RTC until that is better understood. Does this need to be in the shutdown script?
we have /udev script as well, what is running that?
Better cleanup of fake hwclock:
sudo apt-get remove fake-hwclock
sudo update-rc.d -f fake-hwclock remove
sudo rm /etc/fake-hwclock.data
Better pd-status using:
timedatectl status
To debug logs need setting in conf file and create directory to get it to work:
sudo nano /etc/systemd/journald.conf
Storage=persistent
AND
sudo mkdir -p /var/log/journal THEN reboot
question: sudo apt-get install bootlogd needed? not completely sure on this one
https://www.digitalocean.com/community/tutorials/how-to-use-journalctl-to-view-and-manipulate-systemd-logs