On 09/21/10 17:08, PJ Bostley wrote:
On 9/21/2010 3:28 PM, Auke Kok wrote:
Do you have a concrete issue where something "becomes a problem if
there is a need to add new a daemon that has to be started *before* a
daemon started by rc.sysinit." ?
Yes.
Plugins for things running in sysinit will have dependencies on 3rd
party software that must start before stuff in sysinit.
Specifically we have an ofono plugin that needs to talk to a
communication link multiplexing daemon that is specific to a piece of
3rd party hardware. With ofono launching out of rc.sysinit there is
nowhere to start the multiplexing daemon other than hacking on rc.sysinit.
As said before, this smells like bad design. You should write an ofono
plugin to properly initialize the 3rd party hardware instead. This way,
you don't need to start up anything manually, get rid of the
dependencies, and the ofono plugin can actually restart/monitor the
service, making your part of the stack much more reliable.
What if your hardware isn't available to the system before ofonod
starts? With delayed device initialization, this may very well be the
case. What if your daemon needs to be restarted?
Auke
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
