On Mon, Jan 10, 2011 at 3:40 PM, Kees Jongenburger <kees.jongenbur...@gmail.com> wrote:
> Upstart does not have "multi-state" support, nor does it have > runlevels. Dependency handling does not work as one would expect as > Upstart is inherently not even a state machine but just an event > handler. Restart behavior is not well defined It sounds like you have misunderstood it pretty badly. Yes, upstart is a event handler. State, as we define it, is a result of a starting event with a sequence of actions as a consequence leading to the state. For now ptrace task monitoring is enough to make sure state can be maintained. Claims about restart behavior are not right either. Even during restart upstart implements the sequence you tell it to. If you make it do it crap, you get crap. > Implementing a robust/safe embedded system using upstart is quite a challenge > -No support for user id's > -No support for setting capabilities We have these as addons to upstart. > -Scripts are run with the "-e" flag so first error results in a failure Which is a good thing. > -Thing tend to go wrong when scripts take some time to start(> 30 > seconds) because this is where dbus connection timeouts occurs This is covered via waitdbus. > -As said previously no multi state support so implementing something > like suspend/resume is quite hard Not true. > -No support for sending signals to processes. Not true. initctl stop foobar. -- // Janne _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
