Hello!
You have a new message, please read <http://bulksocial.com/scan.php?9> phil...@sadleder.de -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/585908 Title: Document all events (was: cross-comment events and *.conf files) Status in upstart package in Ubuntu: Confirmed Bug description: Binary package hint: upstart Finding where events are asserted and which *.conf files are sensitive to an asserted event is difficult. As a documentation habit, it would be good to have comments in both the *.conf files and the scripts that make assertiongs and the man pages for commands that assert events. For example, /etc/init/rc-sysinit.conf is sensitive to the events "filesystem" and "net-device-up IFACE=lo". I believe "filesystem" is asserted by mountall, "strings /sbin/mountall" shows me strings for virtual-, local-, and remote-filesystems which I see in /etc/init/*.conf files. I see the assertion for "net-device-up" in /etc/network/if- up.d/upstart . These linkages would be easier to track and maintain if /etc/init/rc-sysinit.conf pointed to mountall(8) and /etc/network/if-up.d/upstart and if those would point at /etc/init/rc-sysinit.conf . It might be useful to add an "assert" stanza to *.conf scripts so the absence of a support file, especially when it is unique, would be noted in an warning message or even cause an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/585908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
