>From the ML discussions upstream might take the initialization improvements, >but not the try-and-fall-back we need. So we will go with the wrapper for now.
There might be a best of both worlds approach to make us safe against time namespaces. We could use the wrapper to set -X (upper case) and carry a patch. But this is already a maintenance burden being the script and with it in place -X won't give us too much on top. So going the fix via wrapper that sets -x (lower case) in the cases we think it is needed. And eating the implications this have (install chrony and service working means not always we sync time). But we provide: - log entries that warn about it - config options to override I'll let you know when some tests are done and this is ready for wider Ubuntu review. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589780 Title: chrony.service doesn't start on LXD container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1589780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
