Turning off sssd does not remove files in /var/lib/sss/mc. This allows to respond on requests like 'id username' with sssd turned off. Is this behavior OK or is it a bug? I think it is not very logical to keep this files present. If someone turns off sssd, he probably wants to turn off all services that sssd provides. Or is there some other reason not to remove these files?
Thanks Michal
On Thu, Aug 16, 2012 at 05:32:08PM +0200, Michal Židek wrote:
Turning off sssd does not remove files in /var/lib/sss/mc. This allows to respond on requests like 'id username' with sssd turned off. Is this behavior OK or is it a bug? I think it is not very logical to keep this files present. If someone turns off sssd, he probably wants to turn off all services that sssd provides. Or is there some other reason not to remove these files?
Thanks Michal
I would consider this a bug as well. Shutting down the SSSD should mean it's not responding, otherwise the caching becomes very unpredictable.
Please file a ticket.
----- Original Message -----
On Thu, Aug 16, 2012 at 05:32:08PM +0200, Michal Židek wrote:
Turning off sssd does not remove files in /var/lib/sss/mc. This allows to respond on requests like 'id username' with sssd turned off. Is this behavior OK or is it a bug? I think it is not very logical to keep this files present. If someone turns off sssd, he probably wants to turn off all services that sssd provides. Or is there some other reason not to remove these files?
Thanks Michal
I would consider this a bug as well. Shutting down the SSSD should mean it's not responding, otherwise the caching becomes very unpredictable.
It is intentional. You do not want to delete the fast cache at every reboot. With the fast cache in place queries are replied fast from it even before SSSD is started.
In what case caches would be unpredictable ? All the common users available are still there, this is not much different from using SSSD in offline mode, or is there something I am mising ?
Simo.
On 08/16/2012 11:18 PM, Simo Sorce wrote:
----- Original Message -----
On Thu, Aug 16, 2012 at 05:32:08PM +0200, Michal Židek wrote:
Turning off sssd does not remove files in /var/lib/sss/mc. This allows to respond on requests like 'id username' with sssd turned off. Is this behavior OK or is it a bug? I think it is not very logical to keep this files present. If someone turns off sssd, he probably wants to turn off all services that sssd provides. Or is there some other reason not to remove these files?
Thanks Michal
I would consider this a bug as well. Shutting down the SSSD should mean it's not responding, otherwise the caching becomes very unpredictable.
It is intentional. You do not want to delete the fast cache at every reboot. With the fast cache in place queries are replied fast from it even before SSSD is started In what case caches would be unpredictable ? All the common users available are still there, this is not much different from using SSSD in offline mode, or is there something I am mising ?
Simo.
I found this behaviour strange (that something works after it was turned off), but what you mentioned is a good reason to keep it as it is. I'll change the ticket status to 'invalid'.
Thanks for explanation. Michal
----- Original Message -----
On 08/16/2012 11:18 PM, Simo Sorce wrote:
----- Original Message -----
On Thu, Aug 16, 2012 at 05:32:08PM +0200, Michal Židek wrote:
Turning off sssd does not remove files in /var/lib/sss/mc. This allows to respond on requests like 'id username' with sssd turned off. Is this behavior OK or is it a bug? I think it is not very logical to keep this files present. If someone turns off sssd, he probably wants to turn off all services that sssd provides. Or is there some other reason not to remove these files?
Thanks Michal
I would consider this a bug as well. Shutting down the SSSD should mean it's not responding, otherwise the caching becomes very unpredictable.
It is intentional. You do not want to delete the fast cache at every reboot. With the fast cache in place queries are replied fast from it even before SSSD is started In what case caches would be unpredictable ? All the common users available are still there, this is not much different from using SSSD in offline mode, or is there something I am mising ?
Simo.
I found this behaviour strange (that something works after it was turned off), but what you mentioned is a good reason to keep it as it is. I'll change the ticket status to 'invalid'.
We have other files in /var/lib/sss that are automatically looked up, for example the KDC address. At least for nsswitch, all you need to do is remove the sss lines from nsswitch.conf if you really want to turn sssd off completely. With the KDC stuff at the momment this is not possible, the mere packages being installed cause libkrb5 to load the sssd plugin.
Simo.
I'd prefer it stayed there. It is good to know who owned a file after they are long gone. Uid to user name mapping is what I want to still be around well into the future.
-----Original Message----- From: sssd-devel-bounces@lists.fedorahosted.org [mailto:sssd-devel- bounces@lists.fedorahosted.org] On Behalf Of Michal Židek Sent: Friday, 17 August 2012 1:32 AM To: Development of the System Security Services Daemon Subject: [SSSD] Files 'group' and 'passwd' in /var/lib/sss/mc/ still present even after sssd quits
Turning off sssd does not remove files in /var/lib/sss/mc. This allows to respond on requests like 'id username' with sssd turned off. Is this behavior OK or is it a bug? I think it is not very logical to keep this files present. If someone turns off sssd, he probably wants to turn off all services that sssd provides. Or is there some other reason not to remove these files?
Thanks Michal _______________________________________________ sssd-devel mailing list sssd-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/sssd-devel
sssd-devel@lists.fedorahosted.org
-
Greg Lehmann -
Jakub Hrozek -
Michal Židek -
Simo Sorce