src/examples/sssd*conf: Enable the ifp service by default

[arrowd]

It is required for sssctl program to work and when ifp is not enabled, it fails with an obscure message

[gemini-code-assist]

Code Review

This pull request updates the SSSD configuration examples in src/examples/sssd-example.conf and src/examples/sssd.conf by adding the ifp service to the list of enabled services. I have no feedback to provide as no issues were identified in these changes.

[alexey-tikhonov]

On Linux systems 'ifp' is d-bus socket activated service.
Doesn't it work the same way on FreeBSD?

[arrowd]

After spending some time debugging the sssctl failure it turned out that I hit the following block https://github.com/SSSD/sssd/blob/master/src/monitor/monitor.c#L242-L245

The ifp service does not end up in the list if it wasn't specified in the config, and after failing to register itself with monitor, it immediately exits.

[alexey-tikhonov]

After spending some time debugging the sssctl failure it turned out that I hit the following block https://github.com/SSSD/sssd/blob/master/src/monitor/monitor.c#L242-L245

The ifp service does not end up in the list if it wasn't specified in the config, and after failing to register itself with monitor, it immediately exits.

But it starts at least?

I guess it exits because

sssd/src/monitor/monitor.c

Line 218 in 32dedfb

#ifdef HAVE_SYSTEMD

not met and socket_activated_service_not_found() isn't executed...

That's a real place that needs fixing...

[arrowd]

Yes, the dbus autoactivation mechanism works.

What would be the correct fix?

[alexey-tikhonov]

It depends.
Maybe 'monitor' should allow/expect that any service can be started via external means, doesn't matter if built with/without SYSTEMD support.
Maybe only for 'ifp'...

Currently 'sssd_ifp' can be started automatically as d-bus service, other responders - via systemd socket activation.
Does FreeBSD have anything like systemd socket activation?

[arrowd]

Does FreeBSD have anything like systemd socket activation?

No, our rc.d system is pretty simple wrt that. For dbus services we resort on dbus autoactivation.

[alexey-tikhonov]

Then maybe an exception for 'ifp' makes more sense.