On Mon, 2009-03-30 at 16:42 -0500, David Teigland wrote:
On Thu, Mar 26, 2009 at 02:50:31PM +0100, Fabio M. Di Nitto wrote:
In our current startup sequence, we do start a daemon, we make sure it
starts, but we never check if it's actually working properly.
If there's no groupd_compat
On Tue, Mar 31, 2009 at 07:23:15AM +0200, Fabio M. Di Nitto wrote:
On Mon, 2009-03-30 at 16:42 -0500, David Teigland wrote:
On Thu, Mar 26, 2009 at 02:50:31PM +0100, Fabio M. Di Nitto wrote:
In our current startup sequence, we do start a daemon, we make sure it
starts, but we never check
On Thu, Mar 26, 2009 at 02:50:31PM +0100, Fabio M. Di Nitto wrote:
In our current startup sequence, we do start a daemon, we make sure it
starts, but we never check if it's actually working properly.
If there's no groupd_compat setting in cluster.conf, or if it's set to 2, then
groupd does
On Mon, 2009-03-30 at 16:42 -0500, David Teigland wrote:
On Thu, Mar 26, 2009 at 02:50:31PM +0100, Fabio M. Di Nitto wrote:
In our current startup sequence, we do start a daemon, we make sure it
starts, but we never check if it's actually working properly.
If there's no groupd_compat
Hi everybody,
I spent a bit of time cleaning cman init script to be a lot easier to
read (IMHO), more maintainable and ready to be expanded to fix some
outstanding issues.
major highlights:
- clean up all over
- grouping of functions
- made ready for extensions (specially at startup time)
-
