Re: Disabling cman at boot

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 20 Jun 2008, Federico Simoncelli wrote:

> On Fri, Jun 20, 2008 at 10:42 AM, Fabio M. Di Nitto <fdinitto@xxxxxxxxxx> wrote:
> >> Do you think we should file a bug and continue the discussion there?
> >
> > Sure. that's also fine by me.
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=452234
> 
> As I wrote in the bug description... the solution I proposed (adding a
> boot parameter) will also make impossible to start the services
> manually later on (until next reboot). This might be why Jozsef was
> using the check on a file (which can be easily removed). Jozsef can
> you confirm this?

Yes, that was the easiest way to make possible to (re)start services 
without the need to reboot.

> Do you think we can find a way to remove this side effect?

It could be worked around by adding new command options to the 
cman/gfs/... init scripts:

case "$1" in
   start)
	<check boot option>
	# fall through
   force-start)
	# real startup

> Is there a way to detect if the init script was run by the init binary
> or manually from the shell?

I don't know any reliable way to detect it - of course it might be 
possible.

> Should we add an other init command such as "force-start" to override
> the boot parameter check?

I think the cleanest solution would be to add new command options to the 
init scripts. 

Best regards,
Jozsef
--
E-mail : kadlec@xxxxxxxxxxxx, kadlec@xxxxxxxxxxxxxxxxx
PGP key: http://www.kfki.hu/~kadlec/pgp_public_key.txt
Address: KFKI Research Institute for Particle and Nuclear Physics
         H-1525 Budapest 114, POB. 49, Hungary

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux