I don’t think that the grid frequency is used for PC timekeeping. You have internal timekeeping circuits. AC power stops at the PSU, and I don’t think that there’s any cable over which a time protocol flows from the PSU to the motherboard.
I remember reading someone on some service…maybe it was Steam?..saying that some wildly disproportionate percentage of their users had January 1 as their birthday. As in, people didn’t even want to bother setting the month and day, which defaulted to January 1, just cranked the year back to whatever was required to avoid age-restriction hurdles.
Honestly, it might not be a terrible idea to give them a bogus date, if you’re concerned about privacy and want to encourage poisoning data that data-miners are using.
If they require some sort of actual validation, like an ID document, then I get you.
https://en.wikipedia.org/wiki/Buffalo_buffalo_Buffalo_buffalo_buffalo_buffalo_Buffalo_buffalo
“Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo buffalo” is a grammatically correct sentence in English that is often presented as an example of how homonyms and homophones can be used to create complicated linguistic constructs through lexical ambiguity. It has been discussed in literature in various forms since 1967, when it appeared in Dmitri Borgmann’s Beyond Language: Adventures in Word and Thought.
https://en.wikipedia.org/wiki/Lion-Eating_Poet_in_the_Stone_Den
“Lion-Eating Poet in the Stone Den” is a short narrative poem written in Literary Chinese, composed of around 92 to 94 characters (depending on the specific version) in which every word is pronounced shi ([ʂɻ̩]) when read in modern Standard Chinese, with only the tones differing.[1]
“Shī Shì shí shī shǐ”
Shíshì shīshì Shī Shì, shì shī, shì shí shí shī.
Shì shíshí shì shì shì shī.
Shí shí, shì shí shī shì shì.
Shì shí, shì Shī Shì shì shì.
Shì shì shì shí shī, shì shǐ shì, shǐ shì shí shī shìshì.
Shì shí shì shí shī shī, shì shíshì.
Shíshì shī, Shì shǐ shì shì shíshì.
Shíshì shì, Shì shǐ shì shí shì shí shī.
Shí shí, shǐ shí shì shí shī shī, shí shí shí shī shī.
Shì shì shì shì.
“Lion-Eating Poet in the Stone Den”
In a stone den was a poet called Shi Shi, who was a lion addict, and had resolved to eat ten lions.
He often went to the market to look for lions.
At ten o’clock, ten lions had just arrived at the market.
At that time, Shi had just arrived at the market.
He saw those ten lions, and using his trusty arrows, caused the ten lions to die.
He brought the corpses of the ten lions to the stone den.
The stone den was damp. He asked his servants to wipe it.
After the stone den was wiped, he tried to eat those ten lions.
When he ate, he realized that these ten lions were in fact ten stone lion corpses.
Try to explain this matter.
I have not done so in the traditional sense in quite some years. My experience was that it was an increasing headache due to crashing into a wide variety of anti-spam efforts. Get email past one and crash into another.
Depending upon your use case – using the “forward to a smarthost” feature in some mail server packages to forward to a mailserver run by a SMTP service provider with whom you have an account might work for you. Then it still looks to local software like you have a local mailserver.
If I were going to do a conventional, no-smarthost mailserver today, I think that I would probably start out by setting up a bunch of spam-filtering stuff — SpamAssassin, I dunno what-all gets used these days on a “regular” account — and then emailing stuff from my server and seeing what throws up red flags. That’d let me actually see the scoring and stuff that’s killing email. Once I had it as clean as I could get it, I’d get a variety of people I know on different mail servers and ask them to respond back to a test email, and see what made it out.
I’d also bet against the CMOS battery, if the pre-reboot logs were off by 10 days.
The CMOS battery is used to maintain the clock when the PC is powered off. But he has a discrepancy between current time and pre-reboot logs. He shouldn’t see that if the clock only got messed up during the power loss.
I’d think that the time was off by 10 days prior to power loss.
I don’t know why it’d be off by 10 days. I don’t know uptime of the system, but that seems like an implausible amount of drift for a PC RTC, from what I see online as lilely RTC drift.
It might be that somehow, the system was set up to use some other time source, and that was off.
It looks like chrony is using the Debian NTP pool at boot, though, and I donpt know why it’d change.
Can DHCP serve an NTP server, maybe?
kagis
This says that it can, and at least when the comment was written, 12 years ago, Linux used it.
https://superuser.com/questions/656695/which-clients-accept-dhcp-option-42-to-configure-their-ntp-servers
My Debian trixie system has the ISC DHCP client installed in 2025, so might still be a factor. Maybe a consumer broadband router on your network was configured to tell the Proxmox box to use it as a NTP server or something? I mean, bit of a long shot, but nothing else that would change the NTP time source immediately comes to mind, unless you changed NTP config and didn’t restart chrony, and the power loss did it.