Bug#427499: Merge a few bugs and provide LSB header

Petter Reinholdtsen pere at hungry.com
Thu Feb 21 15:40:49 UTC 2008


[Andre Felipe Machado]
> I read [0] and tried to move the cluster daemons to the end of
> init.d queue as far as possible, in a defined order inside the
> group.  As the Should-Start does not guarantee this, removed then at
> the new proposed headers below.

Why do you want to start the cluster daemon after unrelated services
like xdm and munin-node?  I believe it is better to not depend on
'$all', and instead list the services it need to start after and stop
before.

> Given that $all is composed of "base" services, should not the order
> be first honor the $all then the other strong dependencies in the
> header?

It is not obvious, given the semantic of $all.  And it is not how it
is implemented in the only implementation I know about, insserv.

> Well, I do not have experience with insserv yet, so the objective is 
> to move the cluster daemons group to the very end of boot sequence in a 
> enforced defined order.
> ($all) > $network > $remote_fs > ssh > ccs > cman > fence > clvmd
> There are system services like $named and $time and $syslog that should
> start before any cluster daemon, if available.
> Their absence could lead to troubles in a production site, but they
> are not "essential" for a cluster start.

Then it is better to list $named, $time and $syslog in required-* or
should-*

> I guess that the new proposed headers below will accomplish the
> objective and still LSB 3.1 compliant (did not carefully check
> against 3.2 [1] but seem ok at first sight).

Look good, but I would drop the $all dependency.  Also, there is no
need to order the start and stop dependencies in opposite order.
Instead of

> # Required-Start:    $network $remote_fs fence
> # Required-Stop:     fence $remote_fs $network

I would use

  # Required-Start:    $remote_fs $network fence
  # Required-Stop:     $remote_fs $network fence

It make it easier to see that the two lists are identical.

The other look ok, except the ccs one.  I propose this one:

  ### BEGIN INIT INFO
  # Provides:          ccs
  # Required-Start:    $remote_fs $network ssh
  # Required-Stop:     $remote_fs $network ssh
  # Should-Start:      $named $time $syslog
  # Should-Stop:       $named $time $syslog
  # Default-Start:     2 3 4 5
  # Default-Stop:      0 1 6
  # Short-Description: Cluster aware LVM daemon.
  # Description:       Cluster configuration system to manage the 
  #                    cluster.conf file across the
  #                    Red Hat Cluster.
  ### END INIT INFO

Happy hacking,
-- 
Petter Reinholdtsen





More information about the pkg-lvm-maintainers mailing list