On 11/7/18 2:36 PM, Ed Greshko wrote: > On 11/8/18 5:31 AM, Stephen Morris wrote: >> Thanks Ed, I issued that command and fed the output into grep to search for tun0, and >> found messages saying that the device was successfully activated, and then about 30 >> seconds later a message saying the connection timed out, and then almost a further 30 >> seconds for the connection to actually shutdown. I'll have to contact the vendor to see >> if the 10 year renewal period on my lifetime membership has been reached. > > Well, in order to examine the totality of the session it would note the time (I put a > digital clock widget on screen) the VPN was activated and the time it disconnected. I > would then use the --since and --until parameters to extract the info. > > I just started and then stopped a connection and used.... > > journalctl -b 0 --since 06:19:00 --until 06:19:25 > session > > So, I can see the whole process. FWIW, I manually disconnected at 06:19:15. > >> >> >> Just one question on the journalctl output, when I issued journalctl -b 0, the messages >> displayed had the correct day timestamp but the time displayed in GMT time (with today >> being Nov 08 and the machine being booted at 07:16, the messages displayed by journalctl >> were timestamped Nov 08 18:16, if this time really is GMT time it should have been Nov >> 07 18:16), but when I issued the command journalctl -b 0 | grep -i tun0 the messages >> displayed were correctly timestamped with the current date and local time. Is there >> really two different time formats in use or is there something else at play, like at >> initial boot time the system is running on GMT time and then at a later point in the >> boot process or when KDE starts the system is running in local time? If it is the case >> the next question then becomes why is the day wrong in the GMT representation. >> > > I have never seen that behavior. But, I have my HW clock set to GMT. I seem to recall > this to be the preferred setting and you may have issues with time stamps if set otherwise. Yes, HW clock set to GMT (well, technically UTC) for Linux is standard. The local time is computed based on your timezone. I have the HW clock set to UTC on all my machines and I see the correct local time in my logs. A UTC hardware clock will confuse the hell out of Windows. If you dual- boot Windows and Linux, this will cause some head scratches. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - The trouble with troubleshooting is that trouble sometimes - - shoots back. - ---------------------------------------------------------------------- _______________________________________________ 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
