[systemd-devel] dependencies between instances

Lennart Poettering lennart at poettering.net
Wed Feb 13 11:10:45 PST 2013

On Wed, 13.02.13 11:22, Oleksii Shevchuk (alxchk at gmail.com) wrote:

> > Can you suggest other usecases?
> I can. Situation like local client-server, where server requires root
> creds, cannot into socket/d-bus activation and requires device or
> something about it; client should be running from user and server
> requires.
> Example: pcscd + nfc-eventd
> So, how it supposed to be working:
> 1. Device inserted
> 2. System-wide unit started
> 2.1. Deps of unit started
> 2.2. System instance makes announce about started unit
> 2.3  User instances gets announce
> 3. User instances makes this virtual unit active
> 4. User instances starts user configured deps of unit

I figure the user code should not have to watch system functionality
this way at all. Much rather those daemons should use bus or socket
activation so that they always offer their interfaces when user code
needs it, possibly starting only on demand then.

In fact, pcscd-lite already works like that and uses socket activation afair.


Lennart Poettering - Red Hat, Inc.

More information about the systemd-devel mailing list