On Sat, Jun 4, 2016 at 7:53 AM, Sam Varshavchik <mr...@courier-mta.com> wrote: > Chris Murphy writes: > >> On Fri, Jun 3, 2016 at 9:37 PM, Chris Murphy <li...@colorremedies.com> >> wrote: >> >> > 4. >> > [chris@f24m ~]$ sudo btrfs scrub status / >> > [sudo] password for chris: >> > scrub status for dbf2e938-1f28-4e93-aa6c-1e193004931b >> > scrub started at Fri Jun 3 20:38:15 2016, interrupted after >> > 00:00:05, not running >> > total bytes scrubbed: 2.52GiB with 0 errors >> >> >> The other problem is the journal doesn't contain any hint why there >> was an interruption. >> >> What this incentivizes me to do is just stay logged in, in cases where >> I probably should log out. > > > I would think this would incentivize you to put KillUserProcesses back to > "no".
I don't necessarily have such detailed administrative control of every Fedora box I might connect to, especially a fresh-built one on which I've had no oppertunity to hand-craft and add new configuration management settings. -- devel mailing list devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
