I just skimmed through the deprecated, and there's a *lot*. But one hit me
in the face: if you make a change to /etc/nsswitch.conf, you need to
REBOOT THE SERVER?
Ok, did this come from Redmond?*
Oh, and I note virt-manager replaced by cockpit. Can someone pass along a
little note: Sybase has had, for a bunch of years, a required program...
called cockpit. I think they've got the name by priority....
* I thought that "your cursor has moved; please reboot Windows to have
this change take effect was a joke... until, about 5-6 years ago, I found
in trying to set up samba at home on Win 8 that if I changed the workgroup
name... it required Windows to be rebooted. So... really? nsswitch.conf,
and reboot?
Now I think I'll install C 7 to dual boot on my lady's workstation,
rather
than 8.
mark "or my manager this I should go to ubuntu, which
I dislike...."
mark
On 2019-09-25 10:10, mark wrote:> I just skimmed through the deprecated, and there's a *lot*. But one hit > me > in the face: if you make a change to /etc/nsswitch.conf, you need to > REBOOT THE SERVER?This is true, but the documentation states that it is possible to fix without a reboot: "If a system reboot is not possible, restart the service that joins your system to Active Directory, which is the System Security Services Daemon (SSSD) or winbind." I wonder if the same holds true for LDAP. R's, James
On 9/25/19 7:10 AM, mark wrote:> I just skimmed through the deprecated, and there's a*lot*. But one hit me > in the face: if you make a change to /etc/nsswitch.conf, you need to > REBOOT THE SERVER?Note, that appears in the "known issues" section, and not deprecations.? And if you look at BZ 132608, you'll see that this was reported as an issue in 2004.? I would imagine that it has always been this way, and simply appears in the documentation now. CentOS 7, for example, includes "files sss" in nsswitch.conf by default, so that if you enable integration with a directory server it's not necessary to restart all of the running services. The BZ entry for that issue seems to indicate that while changes to nsswitch.conf do still require restarting any daemons that need it (or a reboot), the change that caused that to impact a user has been reverted, and the issue has been resolved.