Re: VPN Interface not Remaining Active With Firewall?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 9/11/18 8:28 pm, Patrick O'Callaghan wrote:
On Fri, 2018-11-09 at 00:08 +0000, Rick Stevens wrote:
On 11/8/18 2:41 PM, Patrick O'Callaghan wrote:
On Fri, 2018-11-09 at 08:02 +1100, Stephen Morris wrote:
how is linux using GMT when everything is running local.
All Unix-based or Unix-derived systems, including Linux, use GMT
internally, and have done since the very first versions back in the
70s.
Uhm, they _assume_ GMT on the hardware clock. There is no way for the
kernel to verify it's on GMT if it's isolated.
Of course. That's what I mean. The GMT basis for all time measurement
in *nix is hardwired.

NTP (chronyd, ntpd,
ntpdate, whatever) will force the clock to GMT, but if you don't run
NTP I can see very weird stuff on file dates and logs because the
kernel will assume GMT on the system and translate it to local time.

Even if you set your hardware clock to local time, the internal
timestamps used for files will be stored as GMT and converted back when
displayed, according to your timezone environment. This also applies to
logs.
Which would explain any mondo weird timestamps in his log. I believe the
OP said there was a significant time jump in the log entries at some
point. I could see this if his clock isn't on GMT and was drug there
kicking and screaming by NTP. Logs produced before NTP got caught up
would assume the old, local hardware clock time (and be way off), then
the clock gets buggered by NTP and the log entries start making sense
from that point.

This is all surmise on my part, of course.
Yes, there is probably some interaction of that sort going on.

So given all this, when searching journalctl for boot messages across particular datetime ranges, how do you find them when the timestamps in the journals are blatantly wrong, potentially up until the desktop loads?


regards,

Steve



poc
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux