3 ms·
> They are allowed to use pool, they just have to apply to use them. Which has unclear (non-technical) implications. Which Lennart Poettering doesn't want to t
by Merovius 11y ago
> They are allowed to use pool, they just have to apply to use them.
Which has unclear (non-technical) implications. Which Lennart Poettering doesn't want to tolerate. Which I would consider a valid opinion.
> The linked thread has someone from Google telling systemd that systemd should stop using Google's time servers.
For technical reasons, that Lennart Poettering doesn't agree with (i.e. these defaults won't be used in production and if you use an unconfigured self-build of systemd in production, it's your own fault).
- jamespo 11y agoThis doesn't address why not just leave it unconfigured. Unconfigured is better than a bad default.
- dagw 11y agoThis doesn't address why not just leave it unconfigured. He addressed that in another post. Basically from a testing and development POV he believes it's important to ship with some default that at least works out of the box, even if the default is completely unsuitable for production.
- digi_owl 11y agoI think the worst issue here is that the result will be on the surface correct, unlike some other test settings that will show that the protocol/code works but that the settings needs to be changed to be useful. Something akin to the blinking 0:00, that shows the time circuit is powered up but with no time set.