On 9/23/2010 9:34 AM, Auke Kok wrote:
That immediately raises questions:
- is your daemon well-written, such that, once it forks into the
background, it's actually up and running and ofono can be immediately
started?
The following scriptlet (for instance) does NOT work:
# dbus-daemon --system --fork ; hald --daemon=yes
and is a pain to solve once you figure out that you're just starting
too fast :) (btw, normal distributions will likely never see this
issue since they have several scripts executing in between these 2
thus masking the issue).
- also, what's the exact nature of the problem that your daemon needs
to be started before ofonod? Could you implement this in a pluggable
way such that this dependency is not needed? That would for instance
make your daemon restartable (I assume it's not right now) and much
more robust.
also... the ofono plugin should be correctly written and deal with this
daemon coming and going all the time (to make software upgrade of it
possible etc anyway)..
... and to not have a critical dependency in the boot flow as well.
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
