Skip to main content ↑ ↓
Topic: Problems to set time and conflict with debian systems  (Read 7505 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: Problems to set time and conflict with debian systems

Reply #45 –
I have on average between 6-8 distros running one a machine, sharing some partitions, home var tmp, half are devuan/ian based and half arch based.  I have seen the problem before a few times, but can't remember each time what I did to adjust and it worked itself out.
So something that was done in Mint to correct the MS problem (probably the source of the problem) is still there causing the problem now.  Instead of really fixing it then it somehow it was patched to cope with MS stupidity.  It needs to get undone.  Look above and you will see that in some places 5hrs are added to UTC and in some subtracted.

Re: Problems to set time and conflict with debian systems

Reply #46 –
Set in the Bios the hardware clock to UTC time.  Set in each OS the timezone accoding to the database.  If mint is fucking everything up by reseting your hardware clock to real time without telling you then don't use it.

Re: Problems to set time and conflict with debian systems

Reply #47 –
Quote
Set in the Bios the hardware clock to UTC time.

But the problem is that the Bios do not have any option to set time in UTC, as i said before, it just gives this option: 'system time'.

Yes, i think that it is better to uninstall Mint, but first i have to see how these arches are going to work in this hardware because is not my first time with arch, i was using Antergos and Manjaro and there were problems all the time. Any way thank you very much to all of you for the help!
Mate
Desktop: xfce

Graphics: AMD Radeon HD 7640G integrated graphics
GPU: AMD/ATI Trinity [Radeon HD 7640G]

Re: Problems to set time and conflict with debian systems

Reply #48 –
Well, don't uninstall it, just don't boot it anymore :)
Ok, you can't set UTC on bios, but you must be able to set the time, right?  So the time should be -5 EST.  If it is 13:00 there now set it for 18:00.
Then see what Artix does.
If all is OK, then look at what Minty is doing.

Re: Problems to set time and conflict with debian systems

Reply #49 –
Mint is evidently doing a hwclock set of whatever it thinks local time is...

Re: Problems to set time and conflict with debian systems

Reply #50 –
No way ... when comeback to arch the time was wrong again. To me it's over.

Thanks!
Mate
Desktop: xfce

Graphics: AMD Radeon HD 7640G integrated graphics
GPU: AMD/ATI Trinity [Radeon HD 7640G]

Re: Problems to set time and conflict with debian systems

Reply #51 –
We gave it a hell of a try, collectively.
It seems as tz is a very Keotic business in linux.
With microsoft you just let it allow the clock with ms server or nist, and who knows what other rights you are passing over to those servers, but your clock is ticking.
Let's say some server intentinally makes your clock 0.123456789 seconds ahead of the server.  In a tor network you would stand out like a shore thumb because of your time deviation.  Need I say more?

One last thing to check is your "services" on systemd list.  Which ones are active and if one of them is a clock adjusting "service".  Turn that bugger off.  I haven't been around systemd so long that I don't remember much of it, but there was some gui panel in the settings menu that you can activate and deactivate services.  Some were crucial to the system some were just the "hydra's" heads crawling all over your system.

Re: Problems to set time and conflict with debian systems

Reply #52 –
why not just let ntpd set the time?

Re: Problems to set time and conflict with debian systems

Reply #53 –
Quote from: mrbrklyn – on
why not just let ntpd set the time?
You mean in Artix? So it would automatically correct the time even if it was wrong - that would be a good idea I guess, and save finding what is wrong in Mint.
Quote from: fungalnet – on
One last thing to check is your "services" on systemd list.  Which ones are active and if one of them is a clock adjusting "service".  Turn that bugger off.  I haven't been around systemd so long that I don't remember much of it, but there was some gui panel in the settings menu that you can activate and deactivate services.  Some were crucial to the system some were just the "hydra's" heads crawling all over your system.
Mint Rosa is based on Ubuntu 14.04 which used Upstart not systemd. Anyone know anything about Upstart?  :)

The clock is probably getting set in early boot before auditd starts, although it would still tell you that is is happening in early boot and not at any other time, but if there was something else setting it later you could find out exactly what it was with audit if that is available and working in Mint:

Install "audit" package
Put these files (should be included in the audit package somewhere) in config dir /etc/audit/rules.d
10-base-config.rules  30-stig.rules  99-finalize.rules
(you might want to uncomment or comment some stuff in these, see the explanations in the files, there are man pages for auditd etc.)
Run
# augenrules
Enable the auditd service (if that isn't already done)
Reboot
Print out logged time-change stuff
# ausearch --start this-week --key time-change

It will probably give some info about time change rules being loaded regardless, but if it finds anything setting the time it will say what and when.
mrbrklyn's idea might be simpler though  :)

Re: Problems to set time and conflict with debian systems

Reply #54 –
set it with ntp with both