-----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.
- -- Stephen Gallagher RHCE 804006346421761
Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/
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-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 01/29/2010 07:23 AM, Sumit Bose wrote:
On Tue, Jan 26, 2010 at 09:42:52AM -0500, Stephen Gallagher wrote: 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.
I don't know about "production", but I think it would be useful for anyone developing their own custom backend. They don't need to recompile the SSSD binary just for this.
We could make it a commandline argument if you think that's wiser, but since only root can send it a signal anyway, I think we're probably over-engineering it.
- -- 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 SIGNED MESSAGE----- Hash: SHA1
On 01/29/2010 07:23 AM, Sumit Bose wrote:
On Tue, Jan 26, 2010 at 09:42:52AM -0500, Stephen Gallagher wrote: 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
Pushed to master.
- -- Stephen Gallagher RHCE 804006346421761
Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/
sssd-devel@lists.fedorahosted.org
-
Stephen Gallagher -
Sumit Bose