Simo Sorce wrote:
On Mon, 2012-10-29 at 15:41 -0400, Rob Crittenden wrote:
Simo Sorce wrote:
On Fri, 2012-10-26 at 16:30 -0400, Rob Crittenden wrote:
Simo Sorce wrote:
From: Simo Sorce sso...@redhat.com
We check (possibly different) data from LDAP only at (re)start.
This way we always
From: Simo Sorce sso...@redhat.com
We check (possibly different) data from LDAP only at (re)start.
This way we always shutdown exactly the services we started even if the list
changed in the meanwhile (we avoid leaving a service running even if it was
removed from LDAP as the admin decided it
From: Simo Sorce sso...@redhat.com
We check (possibly different) data from LDAP only at (re)start.
This way we always shutdown exactly the services we started even if the list
changed in the meanwhile (we avoid leaving a service running even if it was
removed from LDAP as the admin decided it
Simo Sorce wrote:
On Fri, 2012-10-26 at 16:30 -0400, Rob Crittenden wrote:
Simo Sorce wrote:
From: Simo Sorce sso...@redhat.com
We check (possibly different) data from LDAP only at (re)start.
This way we always shutdown exactly the services we started even if the list
changed in the meanwhile
On Mon, 2012-10-29 at 15:41 -0400, Rob Crittenden wrote:
Simo Sorce wrote:
On Fri, 2012-10-26 at 16:30 -0400, Rob Crittenden wrote:
Simo Sorce wrote:
From: Simo Sorce sso...@redhat.com
We check (possibly different) data from LDAP only at (re)start.
This way we always shutdown exactly
Simo Sorce wrote:
From: Simo Sorce sso...@redhat.com
We check (possibly different) data from LDAP only at (re)start.
This way we always shutdown exactly the services we started even if the list
changed in the meanwhile (we avoid leaving a service running even if it was
removed from LDAP as the
From: Simo Sorce sso...@redhat.com
We check (possibly different) data from LDAP only at (re)start.
This way we always shutdown exactly the services we started even if the list
changed in the meanwhile (we avoid leaving a service running even if it was
removed from LDAP as the admin decided it