So it seems that just for starting the service without accepting a msg it is a bit misuse, in the fact that you send a nonsense message just to get the device started. Does this have any performance penalty ? For example, if msg loss can occur while the service is not started, it can take longer the fist time to send the msg and process it and this might manifest in the user's ui taking longer to response on the first time. Or is this wrong thinking ?
-Sivan On Sat, Sep 4, 2010 at 7:56 PM, Attila Csipa <[email protected]> wrote: > > > On Fri, Sep 3, 2010 at 10:35 PM, Sivan Greenberg <[email protected]> > wrote: >> >> On Fri, Sep 3, 2010 at 10:22 PM, Auke Kok <[email protected]> >> wrote: >> > On 09/03/10 09:42, Epshteyn, Eugene wrote: >> >> >> >> Are there instructions for MeeGo similar to what exists for Debian >> >> (http://www.debian.org/doc/manuals/securing-debian-howto/ch9.en.html) >> >> about setting up daemons? I have some software that needs to run as >> >> a daemon, and I would like to learn what's the right way to do that >> >> on MeeGo (e.g., creating separate user/group, adding to init.d, >> >> what's a good place for the daemon to dump log files, etc.) >> > >> > MeeGo currently assumes no new system-wide daemons will be added, we >> > prefer >> > that services are started on-demand where possible, and/or run from the >> > user's session instead of running system-wide. D-bus activation is a >> > popular >> > and well-proven method for doing this. >> >> What's the proper canonical way to use dbus in such way to trigger >> local service startup ? > > See http://freedesktop.org/wiki/IntroductionToDBus under Activation. Though > some think using DBus for such things isn't a great idea, see > http://upstart.ubuntu.com/faq.html#replace-dbus for some background. > > > > _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
