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

[Lennart Poettering]

On Sat, 22.01.11 20:55, Andrey Borzenkov (arvidjaar at mail.ru) wrote:

> >> mdmon does not belong to user. User is not even aware that it is
> >> started. And it is likely not the last case. So systemd does need some
> >> framework which can move such processes out of user session. It
> >> probably needs some sd_daemon API to notify systemd that it is system
> >> level task even if it was started as result of user interaction.
> >
> >  Well, it is started by user, so it belongs to user. And
> > systemd has an API to start system-level task as a result of
> > user interaction: it is called "systemctl start mdmon.service".
> >
> 
> mdmon is not a singleton - it is started for every array that needs it
> (not each array needs it). Can you pass extra parameters that identify
> object mdmon should monitor via systemctl?

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").

Lennart

-- 
Lennart Poettering - Red Hat, Inc.