Re: [CentOS] SSSD and cache persistence

> >> If the cache is invalid SSS will, obviously, go back to the source and >> return the information there, however, bizarrely, if the original >> source doesn't have the information (like when a user is deleted) the >> cached information is still returned. That cached information is >> retained f

[CentOS] Centos 7.5..and My GDM Greeter/GDM Don't Work Anymore

So, we've updated to 7.5, and for two machines--A Dell Precision M4800, and a Dell Precision 7510..both running Radeon cards--we no longer get the GDM Greeter login box NOR can we switch to virtual text login terminals. It's been driving me nuts. The systems do allow for SSH logins, so that's h

[CentOS] systemd equivalent of xinetd 'only_from' and 'banner_fail' attributes

I'm attempting to port an existing xinetd service from CentOS 6 to something equivalent with systemd for CentOS 7 The existing xinetd config uses the attributes 'only_from' to limit connections from a limited set of remote hosts and 'banner_fail' to print a suitable error message when access is

Re: [CentOS] SSSD and cache persistence

On Mon, 2018-08-06 at 19:55 -0700, Gordon Messmer wrote: > On 08/06/2018 03:16 AM, Pete Biggs wrote: > > If the cache is invalid SSS will, obviously, go back to the source and > > return the information there, however, bizarrely, if the original > > source doesn't have the information (like when a

Re: [CentOS] SSSD and cache persistence

> If the cache is invalid SSS will, obviously, go back to the source and > return the information there, however, bizarrely, if the original > source doesn't have the information (like when a user is deleted) the > cached information is still returned. That cached information is > retained for ev