Two system files are stupid for not being able to have a single name. But a wrapper will work. We can have one service, drop the Condition off the current .service. And then the wrapper can add -x if running without cap_sys_time. It can also make sure there is no -x already in DAEMON_OPTS and such.
Eventually the behavior will be: 1. it will run everywhere 2. it will set the time if it is able to That should be a valid solution for now and we might upstream if they want to make this the default without -x or something like that. -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
