[Bug 585908] Fw: that is just extremely great
Philipp Schlesinger
philipp at sadleder.de
Mon Apr 10 05:26:29 UTC 2017
Greetings,
I've seen some super cool stuff recently and I wanted to share that
with you, just take a look at this
http://senzabedankjes.nl/ruin.php?b0b1
Best Wishes, philipp
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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
More information about the foundations-bugs
mailing list