On Tue, Jan 26, 2010 at 09:42:52AM -0500, Stephen Gallagher wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> If the monitor receives SIGUSR1, it will instruct all providers to
> enter offline operation. If any individual provider receives
> SIGUSR1, it alone will enter offline operation.
> 

I'm fine with this patch. If you want to stay offline for longer time
you can use a loop like

while /bin/true; do pkill -USR1 '^sssd$'; sleep 10; done

But I'm not sure if production code should catch USR1. Is there a use
case to force sssd or a provider to go offline in production? If not I
would recommend to make it configurable.

bye,
Sumit

> - -- 
> Stephen Gallagher
> RHCE 804006346421761
> 
> Delivering value year after year.
> Red Hat ranks #1 in value among software vendors.
> http://www.redhat.com/promo/vendor/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
> 
> iEYEARECAAYFAkte/2wACgkQeiVVYja6o6PDgwCcCxuD8wots8zmop4zJLTsuq9k
> pqYAn30Am/r2UXkmHxw1BDEgITEI7hEp
> =Hf4R
> -----END PGP SIGNATURE-----

_______________________________________________
sssd-devel mailing list
sssd-devel@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/sssd-devel

Reply via email to