Comment 2 for bug 1966181

Hello Timo,

I'm not actually sure where these /etc/systemd/system/chrony* files come from (in particular the mask). They are not owned by any package, nor does chrony's postinst seem to create it (but maybe through a helper, they are not exactly simple -- some weird interaction with the SysV compat code?).

The chronyd.service link is created by the Alias=chronyd.service in chrony.service, and systemd creates that when enabling the service.

My debian-testing VM has that chrony.service → /dev/null mask link right after a fresh install and boot, no IPA script was running yet. But I just saw that I apparently mixed up my VMs when reporting this here -- my ubuntu-stable VM does not have chrony installed at all (even though freeipa-client recommends it, and I don't use --no-install-recommends). I'll investigate this more thoroughly, chase down what creates that pesky chrony.service masking, and report back here.

Thanks, and sorry for the noise so far!