From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: 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 08:44:34 -0400 [thread overview]
Message-ID: <ac28e105-f228-de18-08c2-e504e304052d@gmail.com> (raw)
In-Reply-To: <CAJCQCtQ8yPQf8O2LA92-Gd95GGXQiDp-ZomKZgP4bNv-MmKHYw@mail.gmail.com>
On 2016-07-30 20:29, Chris Murphy wrote:
> On Sat, Jul 30, 2016 at 2:02 PM, Chris Murphy <lists@colorremedies.com> wrote:
>> Short version: When systemd-logind login.conf KillUserProcesses=yes,
>> and the user does "sudo btrfs scrub start" in e.g. GNOME Terminal, and
>
> Same thing with Xfce, so it's not DE specific. (Unsuprising.)
>
> I inflated the size of the test volume, and it seems pretty clear that
> the scrub is not completing, as the kernel threads stop sooner when
> logging out vs not logging out. So the status reporting an
> interruption appears to be valid for the net operation, not merely the
> user space tool being interrupted.
You have your terminals set to start the shell as a login shell I'm
guessing. That's probably why closing the terminal window is triggering
systemd's process killing. It will of course still trigger when you
close the graphical session though. Personally, this is yet another
reason for me to not like systemd. This setting breaks traditional UNIX
userspace semantics.
Personally, I'm with Duncan on this one though, if resume works
correctly, then it's not a bug, just a bad interaction between an
administrative tool designed for a server and an init system designed
for a desktop.
next prev parent reply other threads:[~2016-08-01 12:46 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 [this message]
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
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=ac28e105-f228-de18-08c2-e504e304052d@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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).