[Dev] Tizen 3.0 proposal for fixing OSP/WRT/Core hard-coded UID issue

Jussi Laako jussi.laako at linux.intel.com
Thu Oct 17 10:13:47 GMT 2013

On 17.10.2013 12:31, Patrick Ohly wrote:
> For example, exclusive write access to the sqlite DB in EDS or the Tizen
> contacts service simplifies change notification, because a single
> process knows what changes are made at a semantic level and can send

By the way, easiest way to solve this for UI-less daemon services is to 
daemonize the service (disconnect stdio and call setsid()) and use one 
daemon per userid and then use a single per-user p2p dbus socket for 
communication instead of session bus. This way the service becomes 
per-user and not per-session and all sessions of single user can talk to 
the same daemon.

Or alternatively yuou could even expand this to have three dbus daemons 
and buses, "system", "session" and "user".

Like the system bus, user-bus services couldn't have GUIs, while the 
session-bus services can. This way you can easily make some of the 
existing services work even if they assume exclusive access to some 
files, as long as they don't try to have a GUI at the same time...

More information about the Dev mailing list