If user starts array manually (mdadm -A -s as example) from within
user session and array needs mdmon, mdmon becomes part of user session
control group:
├ user
│ └ root
│ └ 1
│ ├ 1916 login -- root
│ ├ 1930 -bash
│ ├ 1964 gpg-agent --keep-display --daemon --write-env-file /root/.gnup
On Saturday, December 04, 2010 09:41:26 am Andrey Borzenkov wrote:
> If user starts array manually (mdadm -A -s as example) from within
> user session and array needs mdmon, mdmon becomes part of user session
> control group:
>
> ├ user
> │ └ root
> │ └ 1
> │ ├ 1916 login -- root
> │ ├ 1
On Sat, Dec 4, 2010 at 12:12 PM, Christian Parpart wrote:
> On Saturday, December 04, 2010 09:41:26 am Andrey Borzenkov wrote:
>> If user starts array manually (mdadm -A -s as example) from within
>> user session and array needs mdmon, mdmon becomes part of user session
>> control group:
>>
>> ├ u
On Sat, Dec 04, 2010 at 03:08:05PM +0300, Andrey Borzenkov wrote:
> > (/etc/pam.d/system-auth), which automatically creates cgroups by login
> > session, which in turn gets killed when the user has "completely logged
> > out".
> > That is why your mdadm gets terminated, too.
>
> Sure.
>
> > You
