Comment 3 for bug 574554
Revision history for this message
| Scott James Remnant (Canonical) (canonical-scott) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I would recommend not deploying this script as-is.
Using "and" in a "start on" condition links the two events, so neither can complete until the other occurs, and links them to your service so that neither can complete until your service starts.
In your script, this would link the "net-device-up IFACE=lo" event and the "filesystem" event together, and to you your service.
Since these are also used by key services required to boot the system, it's possible that tying them together would be a BAD THING. One could envision a scenario whereby the system wouldn't boot due to the service not starting correctly.
The rc-sysinit script already uses these events, for now it might be better to do "start on started rc-sysinit"