On 21.3.2019 16.23, Timo Aaltonen wrote: > On 21.3.2019 16.02, Jan Luca Naumann wrote: >> Another way could be to check in the postinst files if there is already >> an existing sssd.conf file and, if yes, do not enable the systemd units. >> >> This should prevent breaking existing installations but would allow to >> use the services after adjusting sssd.conf and new users would use the >> sockets directly. Admins of existing installations could be informed >> about this change via the NEWS file. >> >> Would that be a useful solution? > > No I think that would be very confusing :) > > I've pushed a new upstream plus added socket activation back (though the > changelog doesn't mention it) here: > > https://aaltoset.kapsi.fi/sssd > > if you can test that it'd be great
I tested it myself and works fine, this is now pushed to experimental so it should be easier to test. I'm hoping this would be fine for buster too. -- t
