/srv/irclogs.ubuntu.com/2016/09/10/#ubuntu-za.txt

inetprogood evening everyone14:09
inetproor is it still afternoon14:09
nlsthzninetpro: alo, evening here (basically :p)14:25
inetprohaha, how're you doing nlsthzn? :-)14:25
nlsthznalive and kicking :) how about you?14:25
inetprosweating14:26
nlsthznsummer arrived?14:26
inetproyeah, winter -> summer without much of spring in between14:28
inetprojust hope it will bring some rain soon14:28
inetpronlsthzn: btw, do you know by any means how KDE or Ubuntu time is syncronised in the back end these days?14:29
inetproif I enable systemd systemd-timedated.service it dies by itself again even if I untick "Set date and time automatically"14:30
nlsthznnope sorry 14:30
inetproand there's no NTP or NTPDATE installed14:30
nlsthznsystemd ftw?14:30
inetproon a server you just configure /etc/systemd/timesyncd.conf and restart systemd-timedated.service and it works14:31
nlsthznso your systems time isn't automatic any more?14:31
inetprowell....14:31
inetproon a machine able to communicate directly with the internet there's no problem14:32
inetproproblem is when you work inside a protected network14:33
nlsthznhttps://www.freedesktop.org/software/systemd/man/systemd-timedated.service.html14:33
inetprohave a NTP server at the edge but obviously desktops don't know that14:33
nlsthznseems if the service terminates itself if not used14:33
nlsthzncan it be it can't see the net to sync and then quits?14:33
inetproI set the following value in timesyncd.conf on a KDE laptop with "Set date and time automatically" unticked on the GUI14:38
inetproNTP=0.ntp.is.co.za 1.ntp2.is.co.za14:38
inetproyet when I restart the systemd service I still don't see any attempt of the machine trying to contact anyone of those on port 12314:39
inetproor any other port for that matter14:42
inetprobut when I change that same setting on a server on our network to our NTP server it works perfectly14:43
* nlsthzn has no idea14:46
* nlsthzn goes and eats :p14:46
inetproenjoy the meal!14:51
nlsthznmeal done, baby bear in the bed (and fighting the sleeps :p)16:37
nlsthznthx inetpro :)16:37
pavlushkaahoy ZA!16:51
pavlushkao/16:52
nlsthzna wild pavlushka appears...17:04
pavlushkanlsthzn: halum :p17:43
nlsthznif you say so17:43
inetpronlsthzn: oh I was wrong, again17:47
nlsthznat least you know your wrong, that is very useful 17:48
inetproI missed the tcpdump traffic to port 123 because it's UDP17:48
inetprofigured it out now17:48
inetprothat desktop setting does actually read the value in /etc/systemd/timesyncd.conf17:49
inetprochanged 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 choosing17:50
inetproeven if the service reports as "inactive (dead)"17:51
nlsthzn\o/17:52
inetprofigured it out after looking at journalctl -f and seeing the logged events when ticking and unticking the GUI option17:54
inetprohopefully one day someone will add an option to allow changing the ntp server as well17:56
inetproin fact, a nicer option would probably be to have some kind of a logic to make an internal NTP server discoverable automagically17:57
inetproI mean allow changing the NTP server in the GUI as well above...17:58
inetpropointing everyone to ntp.ubuntu.com by default is not very wise in my eyes18:00
nlsthznyup18:01
* nlsthzn will be back18:01
inetpronlsthzn: oh and there's no need to change things on the GUI either18:25
inetprojust run the following on the cli after changing timesyncd.conf18:25
inetpro$ timedatectl set-ntp false && timedatectl set-ntp true18:25
nlsthznsweet18:32
* nlsthzn has been on Ubuntu for two days now, time to hop... bbl18:32

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!