Call primary.d and secondary.d scripts according to their dependencies

Bug #692790 reported by Derek_ on 2010-12-20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenVista/GT.M Integration

Bug Description

Until recently, the typical method by which Linux systems handle dependencies between init scripts has been to assign a priority number to each and then call them in that order. Newer systems for starting and stopping Linux services, such as Upstart, allow for the service init scripts to each be called asynchronously as soon as their specified dependencies are satisfied.

My initial design for openvista-init was to provide a dependency-based method, but since there are only a few services expected initially to be called in primary.d and secondary.d, and those few have minimal interdependency, the version of openvista-init for the first release of OpenVista replication is, for simplicity, written to just call each of the scripts asynchronously without regard to any dependencies. Since some future services may need to take interdependency of the services into account, we should provide support for this. The script added in this commit and then removed in the next contains code that might be adapted for this.

revision-id: <email address hidden>

Derek_ (derek-name) on 2011-07-29
tags: added: openvista-init
Changed in openvista-gtm-integration:
milestone: 0.9.1 → 0.9.2
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers