**** BEGIN LOGGING AT Mon Jul 09 03:00:02 2018 Jul 09 13:42:04 Morning! Jul 09 14:17:18 morning Jul 09 18:10:52 elvispre: Hmmz weird Jul 09 18:10:59 You shouldn't need timesyncd Jul 09 18:11:15 Unless there's a dependency somewhere in other service files Jul 09 18:13:58 That would most likely be in connman then Jul 09 19:20:15 Herrie: I would imagine that there is a dependency hidden in there somewhere, yes. Jul 09 19:20:50 The really interesting thing for me was being able to start the timesyncd service at all. Jul 09 19:21:33 It generally fails with a cryptic systemd "NAMESPACE" error, so I was just pleased to get some movement on that. Jul 09 21:02:53 elvispre: Might be 3.4 kernel specific Jul 09 21:02:58 Not sure need to check my mido Jul 09 21:03:10 timesyncd is missing some config so it fails for me at some point too Jul 09 21:03:17 But that's to reach a server I think Jul 09 21:03:21 Not the service itself Jul 09 21:46:12 Herrie: I did notice that the systemd README specifies 3.10 kernel as minimum. Not much to be done but live with that for the moment, I guess. **** ENDING LOGGING AT Tue Jul 10 03:00:01 2018