Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: [SOLVED] RTC (runit) (Read 685 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

[SOLVED] RTC (runit)

My clock says:
Code: [Select]
sudo hwclock --show
[sudo] password for root: 
2021-06-11 15:14:49.061980-03:00

But, actually it's 2021-06-14 09:26 (São Paulo/Brazil).

I tried
Code: [Select]
sudo ln -sf /usr/share/zoneinfo/Brazil/East /etc/localtime

Code: [Select]
sudo hwclock --systohc --verbose
Code: [Select]
hwclock from util-linux 2.37
System Time: 1623435436.842137
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Last drift adjustment done at 1623435429 seconds after 1969
Last calibration done at 1623435429 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
RTC type: 'rtc_cmos'
Using delay: 0.500000 seconds
missed it - 1623435436.842355 is too far past 1623435436.500000 (0.342355 > 0.001000)
1623435437.500000 is close enough to 1623435437.500000 (0.000000 < 0.002000)
Set RTC to 1623435437 (1623435436 + 1; refsystime = 1623435436.000000)
Setting Hardware Clock to 18:17:17 = 1623435437 seconds since 1969
ioctl(RTC_SET_TIME) was successful.
Not adjusting drift factor because the --update-drift option was not used.
New /etc/adjtime data:
0.000000 1623435436 0.000000
1623435436
UTC

It didn't work.


I'm running runit, what should I do?

The problem started when I interrupted texlive-full install.

Re: RTC fix (runit user)

Reply #1 –
Install ntp-runit or openntpd-runit and enable it. Once the clock syncs, use hwclock --systohc. Or install ntpdate and run ntpdate 0.pool.ntp.org from cron every hour or so, depending on your clock drift.
 

Re: RTC fix (runit user) [SOLVED]

Reply #2 –
ntp worked, on reboot. Thank you.