On Fri, Mar 03, 2017 at 09:56:55AM +0100, Harald Dunkel wrote: > Hi Jakub, > > On 03/03/17 09:32, Jakub Hrozek wrote: > > On Fri, Mar 03, 2017 at 08:45:10AM +0100, Harald Dunkel wrote: > >> Hi folks, > >> > >> running freeipa client 4.3.2-5 and sssd 1.15.0-3 on > >> Debian Stretch > > ~~~~~~~~~~~~~~ > > This is important I guess. > > > > Since SSSD 1.15, SSSD allows to socket-activate the services, so it is > > no longer required to have them explicitly listed in the services line > > of the sssd section. But: > > - there were some nasty bugs in the first version of the socket > > activation. We will be releasing 1.15.1 today to address those > > issues > > - the sockets must be enabled (systemctl status sssd-nss.socket). I > > understand Debian is doing this but I'm neither Debian user nor > > developer. I would suggest to ask on some Debian-specific forum or > > file a bug report if the resulting configurationd doesn't work. > > > > This is systemd-only? > > Wouldn't it be better to create a working sssd.conf, no matter > what?
It is up to whoever is creating the sssd.conf. As I said, the change is backwards-compatible. If you want the services to be started by sssd, then list them in the services line. If you want to have them started on demand and have a simpler configuration, you rely on the systemd services manager. -- Manage your subscription for the Freeipa-users mailing list: https://www.redhat.com/mailman/listinfo/freeipa-users Go to http://freeipa.org for more info on the project
