Bug 1662470

Summary:	Resurrection of auto-reloading /etc/nsswitch request
Product:	Red Hat Enterprise Linux 7	Reporter:	Trevor Vaughan <tvaughan>
Component:	glibc	Assignee:	glibc team <glibc-bugzilla>
Status:	CLOSED DUPLICATE	QA Contact:	qe-baseos-tools-bugs
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	7.6	CC:	ashankar, codonell, dj, fweimer, mnewsome, pfrankli, vchepkov
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-09 16:01:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Trevor Vaughan 2018-12-28 18:25:04 UTC

Description of problem:

I would like to ask that https://bugzilla.redhat.com/show_bug.cgi?id=132608 be evaluated once more to solve long standing issues with multiple applications that are currently worked around either by restarting processes or various amounts of internal code wrangling.

The original fears from 2004 should be able to be avoided by using inotify where available and simply not having this feature (legacy mode) where not available.

Version-Release number of selected component (if applicable):

All since 2004

How reproducible:

Have a service that uses material from nsswitch and subsequently update the /etc/nsswitch.conf configuration and attempt to evaluate updated information.

Actual results:

Old information is returned

Expected results:

New information is returned

Comment 2 Vadym Chepkov 2019-01-02 13:37:52 UTC

Previously suggested workaround using NSCD doesn't work nowadays, since SSSD is not compatible with it.

Comment 3 Carlos O'Donell 2019-01-09 16:01:10 UTC

Red Hat Enterprise Linux 7 is going to enter Maintenance Support Phase 1 during 2019, and this change means that our customers are looking forward to a stable release without the kinds of changes that this auto-reloading might imply. The lead time to make this change is going to be quite long, we will have to enable this upstream, test it thoroughly for a time with various workloads (enabled by default), and then after enough experience decide if it's ready to backport to a stable RHEL release. All of this work rules out this change for RHEL 7, but we will continue this work as part of the RHEL 8 request in bug 132608. Therefore I'm closing this RFE in favour of bug 132608. Lastly, we understand that this kind of feature is important and will continue investigating how to best implement it upstream.

*** This bug has been marked as a duplicate of bug 132608 ***