[systemd-devel] systemd kills mdmon if it was started manually by user

[Lennart Poettering]

On Tue, 25.01.11 06:58, Andrey Borzenkov (arvidjaar at mail.ru) wrote:

> > systemd supports instantiated services, for example to deal with the
> > gettys (e.g. "getty at tty5.service"). It should be trivial to use the same
> > for mdmon (e.g. "mdmon at md3.service").
> >
> That's right, but the names are not known in advance and can change
> between reboots. This means such units have to be generated
> dynamically, exist until reboot (ramfs?) and be removed when array is
> destroyed. Not sure it is really manageable.

Hmm? It should be sufficient to just write the service template properly
("mdmon at .service") and then instantiate it when needed with "systemctl
start mdmon at xyz.service" or something equivalent. itMs a matter of
issuing a single dbus call.

> And which instance should generate them? mdadm?

i think it is much nicer to spawn the necessary mdadm service instance
from a udev rule, but you could even run it from mdadm by invoking one
dbus call from it.

Lennart

-- 
Lennart Poettering - Red Hat, Inc.