#2501 F34 System-Wide Change: Remove nscd in favour of sssd and systemd-resolved
Opened 15 days ago by bcotton. Modified 2 days ago

This proposal intends to replace the nscd cache for named services with systemd-resolved for the hosts database and the sssd daemon for everything else.


I don't feel like I can make an informed decision for or against this Change, since I don't understand the problem well enough and the discussion on the devil list had mixed opinions as well. ±0

I think we should wait for the discussion to proceed further on fedora-devel.
Essentially:
- nscd is in a separate subpackage and not enabled by default
- dropping nscd reduces the maintainance burden and immediately allows a bunch of thorny bugs to be closed
- dropping nscd does not cause any change for users who haven't opted in
- because it's a separate package, dropping nscd is not relevant for minimization efforts as the term is generally understood
- there are clearly some users of nscd, and they would need to adjust. At least some of those users will be served sufficiently by systemd-resolved.
- There might be some nscd users for whom systemd-resolved is not a good fit. I hope the discussion on fedora-devel will help clarify this.

Metadata Update from @zbyszek:
- Issue tagged with: meeting

10 days ago

I am still trying to catch up with the discussion on devel. I don't have an idea of the number of nscd users because it's not something I often hear people talk about. So I would guess there either are not a lot of nscd users -or- they are all quiet because it works fine.

Regardless, understanding the nscd use cases and making sure there's a transition plan for them would be in order.

I did see a concern regarding musl's use of nscd. I'm not sure how much that matters for Fedora, though we do offer the musl library+toolchain.

We discussed this in today's fesco meeting (
https://meetbot.fedoraproject.org/fedora-meeting-2/2020-11-18/fesco.2020-11-18-15.00.log.html):
@submachine Do you know what glibc upstream wrt. to nscd are, i.e. might it be dropped there too?
Also, would it be possible to slow the removal down a bit: in F34 deprecate the package and mark it as Provides: deprecated() and announce the intent to remove, and then only remove it in F35?

@zbyszek There is currently no discussion upstream regarding possibly dropping nscd.

In Fedora, yes, deprecating in F34 and announcing the intent to remove is possible and okay with us.

@submachine Could you please update the change proposal to include that?

(Also, procedural -1 from me to prevent automatic approval.)

Metadata Update from @churchyard:
- Issue untagged with: meeting

2 days ago

Login to comment on this ticket.

Metadata