AnsweredAssumed Answered

Did Configure Always Autostart the Warden?

Question asked by mandoskippy on Jan 26, 2014
Latest reply on Jan 27, 2014 by mandoskippy
Something I am noticing in 3.1 is configure.sh will auto start the warden.  This is odd for me, because I don't seem to remember it starting the warden. An example of this is when I wanted to move some services around the cluster,  I used to shut it down (the cluster) then run configure on all nodes after installing or uninstalling various roles with apt-get.  When I did it on 3.1 it saw that warden wasn't running, and started it (out of order, causing some consternation on my CLDB etc.

What is the proper way to add and remove services from nodes now? Thanks!


Outcomes