Such a defensive strategy to not misfire is certainly well thought out and appreciated.
However, like Adam pointed out, a log entry indicating why exactly the service couldn't be started would be a good policy change according to me. Or even a simple echo like "START variable not set/incomplete intialisation" would be very helpful for the user. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/815665 Title: corosync does not start with init scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/815665/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
