Am 09.10.2015 um 15:56 schrieb Yuri D'Elia: > On 09/10/15 15:23, Martin Pitt wrote: >> i. e. it only gets enabled once on a fresh install, or when you >> upgrade from jessie. But not e. g. from 226-1 to 227-1. Which version >> did you upgrade from? > > I'm following unstable on a KVM instance where I explicitly do not want > time sync, so I'm unsure on which version this got re-enabled. > > I noticed this issue some months ago, where I disabled the service on > two occasions, then tried using timedatectl, and noticed today that the > service got re-enabled again just before reporting the issue.
You are saying that the service was disabled before the 227-1 update and re-enabled after the 227-1 update? How do you know it was disabled before the update? > I'm sure the service was disabled correctly on all occasions, but it got > re-enabled by was I assumed to be package upgrades. > > Was the systemctl check always into place, or was it added just > recently? (just so I can avoid scavenging through log files). Yes, for systemd-timesyncd it was always there. We started enabled timesyncd by default in 219-1 and the code to not re-enable services on upgrades was added way before in 214-1 Please double check if it's really the systemd upgrade which re-enables the service. If you do the steps I posted, is the service re-enabled for you? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature