From: Chris Murphy <lists@colorremedies.com>
To: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
Cc: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: systemd KillUserProcesses=yes and btrfs scrub
Date: Mon, 1 Aug 2016 11:47:15 -0600 [thread overview]
Message-ID: <CAJCQCtTXNAC1aNpwmhMYYct2GVFO9syFom34XYwM9rGSB5xCJA@mail.gmail.com> (raw)
In-Reply-To: <66ae3161-b57e-e531-36d5-afc726912563@gmail.com>
On Mon, Aug 1, 2016 at 11:19 AM, Austin S. Hemmelgarn
<ahferroin7@gmail.com> wrote:
> On 2016-08-01 13:15, Chris Murphy wrote:
>> I've been using balance with &, and when I logout, the btrfs command
>> continues to flip between status D and R, just like before logout and
>> it appears to complete. I still get status messages of the balance
>> after logout, in kernel messages.
>>
> Interesting, maybe balance is explicitly white-listed? Either that, or it
> just ignores whatever signal systemd uses to kill stuff in this context (I
> initially thought SIGTERM, but SIGHUP would make more sense in this
> context), which wouldn't surprise me either.
I'm not aware of any program specific white listing method with
KillUserProcesses=yes. However, there is KillExcludeUsers which by
default is KillExcludeUsers=root. Everything I run as sudo appears in
top and ps as use root. So are these processes exempt? And if so, why
is btrfs scrub becoming a zombie process? I don't know if it's
appropriate, but I asked about it (no response yet), whether all
things sudo should just be moved out of the user session. In my own
head I don't associate sudo commands with my user or my user session,
and at least top and ps agree with the former, so why not have sudo'd
processes put in a different scope from the outset?
--
Chris Murphy
next prev parent reply other threads:[~2016-08-01 17:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-30 20:02 systemd KillUserProcesses=yes and btrfs scrub Chris Murphy
2016-07-31 0:29 ` Chris Murphy
2016-08-01 12:44 ` Austin S. Hemmelgarn
2016-08-01 15:46 ` Chris Murphy
2016-08-01 15:52 ` Chris Murphy
2016-08-01 16:08 ` Austin S. Hemmelgarn
2016-08-01 16:19 ` Chris Murphy
2016-08-01 16:22 ` Chris Murphy
2016-08-01 16:58 ` Austin S. Hemmelgarn
2016-08-01 17:15 ` Chris Murphy
2016-08-01 17:19 ` Austin S. Hemmelgarn
2016-08-01 17:47 ` Chris Murphy [this message]
2016-08-01 18:00 ` Chris Murphy
2016-08-01 18:43 ` Chris Murphy
2016-07-31 10:56 ` Gabriel C
2016-07-31 16:58 ` Chris Murphy
2016-08-01 3:33 ` Duncan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJCQCtTXNAC1aNpwmhMYYct2GVFO9syFom34XYwM9rGSB5xCJA@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).