Skip to content
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.

[dev.icinga.com #1008] Dependency based boot sqeuence #455

Closed
icinga-migration opened this issue Nov 15, 2010 · 6 comments
Closed

[dev.icinga.com #1008] Dependency based boot sqeuence #455

icinga-migration opened this issue Nov 15, 2010 · 6 comments

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/1008

Created by tgelf on 2010-11-15 15:10:37 +00:00

Assignee: (none)
Status: Closed (closed on 2011-05-05 16:51:22 +00:00)
Target Version: (none)
Last Update: 2011-05-05 16:51:22 +00:00 (in Redmine)


Debian Squeeze will probably switch to dependency based boot per default, even on dist-upgrade. Here a proposal what init scripts could look like:

--- /etc/init.d/icinga.dist
+++ /etc/init.d/icinga
# Provides: icinga
# Required-Start: $local_fs $network
# Required-Stop: $local_fs $network
+ # Should-Start:  ido2db
+ # Should-Stop:   ido2db
# Default-Start:  2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: start and stop Icinga monitoring daemon

--- /etc/init.d/ido2db.dist
+++ /etc/init.d/ido2db
# Provides:          ido2db
# Required-Start:    $local_fs $network
# Required-Stop:     $local_fs $network
+ # Should-Start:      mysql
+ # Should-Stop:       mysql
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Icinga IDO2DB Initscript

Please note that I'm definitively not an expert for dependency-based boot scripts. Therefore someone should try to find out whether something like this really makes sense. For Debian-related information please see http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2010-11-16 09:45:39 +00:00

  • Status changed from New to Feedback
  • Priority changed from Normal to Low
  • icinga

is only true if idoutils are installed. that's not the normal case on a basic core install. so this would haveto remain optional.

  • idoutils

we are not bound to mysql. so this is also rather optional.

preferred solution might be contributed initscripts for different use cases. but in fact, that would be something for package maintainers instead building/using their own initscripts.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2011-03-14 21:45:11 +00:00

  • Assigned to set to Meier
  • Target Version set to 1.4

@chris

pls check if it makes sense to add that to the default initscripts.

@icinga-migration
Copy link
Author

Updated by Meier on 2011-03-21 15:57:15 +00:00

From LSB:

facilities which, if present, should be available during startup of this service. This allows for weak dependencies which do not cause the service to fail if a facility is not available. The service may provide reduced functionality in this situation. Conforming applications should not rely on the existence of this feature.

So in my opinion adding the proposed lines is the right thing to do for icinga. For ido2db I'm not so sure since the database doesn't havt to be mysql.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2011-03-24 21:35:45 +00:00

  • Status changed from Feedback to Assigned
  • Assigned to changed from Meier to mfriedrich

for mysql, that's up to packagers then. from the sources, it's rather hard to tell.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2011-04-28 20:30:51 +00:00

  • Status changed from Assigned to Feedback
  • Assigned to deleted mfriedrich
  • Target Version deleted 1.4

main problem is that not each icinga intance uses ido2db. we are currently using classicui, which does not need any ido2db daemon running. so i'd mainly leave that to packagers.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2011-05-05 16:51:22 +00:00

  • Status changed from Feedback to Closed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant