[14:09] <inetpro> good evening everyone
[14:09] <inetpro> or is it still afternoon
[14:25] <nlsthzn> inetpro: alo, evening here (basically :p)
[14:25] <inetpro> haha, how're you doing nlsthzn? :-)
[14:25] <nlsthzn> alive and kicking :) how about you?
[14:26] <inetpro> sweating
[14:26] <nlsthzn> summer arrived?
[14:28] <inetpro> yeah, winter -> summer without much of spring in between
[14:28] <inetpro> just hope it will bring some rain soon
[14:29] <inetpro> nlsthzn: btw, do you know by any means how KDE or Ubuntu time is syncronised in the back end these days?
[14:30] <inetpro> if I enable systemd systemd-timedated.service it dies by itself again even if I untick "Set date and time automatically"
[14:30] <nlsthzn> nope sorry 
[14:30] <inetpro> and there's no NTP or NTPDATE installed
[14:30] <nlsthzn> systemd ftw?
[14:31] <inetpro> on a server you just configure /etc/systemd/timesyncd.conf and restart systemd-timedated.service and it works
[14:31] <nlsthzn> so your systems time isn't automatic any more?
[14:31] <inetpro> well....
[14:32] <inetpro> on a machine able to communicate directly with the internet there's no problem
[14:33] <inetpro> problem is when you work inside a protected network
[14:33] <nlsthzn> https://www.freedesktop.org/software/systemd/man/systemd-timedated.service.html
[14:33] <inetpro> have a NTP server at the edge but obviously desktops don't know that
[14:33] <nlsthzn> seems if the service terminates itself if not used
[14:33] <nlsthzn> can it be it can't see the net to sync and then quits?
[14:38] <inetpro> I set the following value in timesyncd.conf on a KDE laptop with "Set date and time automatically" unticked on the GUI
[14:38] <inetpro> NTP=0.ntp.is.co.za 1.ntp2.is.co.za
[14:39] <inetpro> yet when I restart the systemd service I still don't see any attempt of the machine trying to contact anyone of those on port 123
[14:42] <inetpro> or any other port for that matter
[14:43] <inetpro> but when I change that same setting on a server on our network to our NTP server it works perfectly
[14:46]  * nlsthzn has no idea
[14:46]  * nlsthzn goes and eats :p
[14:51] <inetpro> enjoy the meal!
[16:37] <nlsthzn> meal done, baby bear in the bed (and fighting the sleeps :p)
[16:37] <nlsthzn> thx inetpro :)
[16:51] <pavlushka> ahoy ZA!
[16:52] <pavlushka> o/
[17:04] <nlsthzn> a wild pavlushka appears...
[17:43] <pavlushka> nlsthzn: halum :p
[17:43] <nlsthzn> if you say so
[17:47] <inetpro> nlsthzn: oh I was wrong, again
[17:48] <nlsthzn> at least you know your wrong, that is very useful 
[17:48] <inetpro> I missed the tcpdump traffic to port 123 because it's UDP
[17:48] <inetpro> figured it out now
[17:49] <inetpro> that desktop setting does actually read the value in /etc/systemd/timesyncd.conf
[17:50] <inetpro> changed it to NTP=ntp2.is.co.za and after a restart of the service and then untick and tick the GUI it all starts synchronising with the server of my choosing
[17:51] <inetpro> even if the service reports as "inactive (dead)"
[17:52] <nlsthzn> \o/
[17:54] <inetpro> figured it out after looking at journalctl -f and seeing the logged events when ticking and unticking the GUI option
[17:56] <inetpro> hopefully one day someone will add an option to allow changing the ntp server as well
[17:57] <inetpro> in fact, a nicer option would probably be to have some kind of a logic to make an internal NTP server discoverable automagically
[17:58] <inetpro> I mean allow changing the NTP server in the GUI as well above...
[18:00] <inetpro> pointing everyone to ntp.ubuntu.com by default is not very wise in my eyes
[18:01] <nlsthzn> yup
[18:01]  * nlsthzn will be back
[18:25] <inetpro> nlsthzn: oh and there's no need to change things on the GUI either
[18:25] <inetpro> just run the following on the cli after changing timesyncd.conf
[18:25] <inetpro> $ timedatectl set-ntp false && timedatectl set-ntp true
[18:32] <nlsthzn> sweet
[18:32]  * nlsthzn has been on Ubuntu for two days now, time to hop... bbl