From: Carlo Zancanaro <carlo@zancanaro.id.au>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: Improving Shepherd
Date: Tue, 06 Feb 2018 03:41:49 +1100 [thread overview]
Message-ID: <87bmh3gzhu.fsf@zancanaro.id.au> (raw)
In-Reply-To: <20180205170011.73780f13@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 703 bytes --]
Hey Danny,
On Mon, Feb 05 2018, Danny Milosavljevic wrote:
> I assume that means "starts a user's shepherd when they log in".
Either that, or run the services itself. In either case, what you
have sent is very helpful!
> User namespaces just present a different set of names to your
> process
> (via VFS) so it looks like a chroot basically.
> It does nothing for processes except fake their ids and limit
> your
> overview of them.
>
> You probably want process groups (see setsid(2)) or maybe
> containers.
Okay. I've been trying to read about containers/cgroups/namespaces
and I think my mind has just blurred them all into the same thing.
I'll read up about process groups. Thanks!
Carlo
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-02-05 16:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 21:14 Improving Shepherd Carlo Zancanaro
2018-01-29 22:27 ` Jelle Licht
2018-02-05 10:49 ` Carlo Zancanaro
2018-02-05 13:08 ` Ludovic Courtès
2018-02-05 15:56 ` Carlo Zancanaro
2018-02-09 13:26 ` Ludovic Courtès
2018-02-09 19:50 ` Carlo Zancanaro
2018-02-09 21:32 ` Christopher Lemmer Webber
2018-02-14 13:10 ` Ludovic Courtès
2018-02-15 13:55 ` Andy Wingo
2018-02-10 13:34 ` Jelle Licht
2018-02-14 13:25 ` Ludovic Courtès
2018-02-15 17:05 ` Jelle Licht
2018-02-15 19:04 ` Mark H Weaver
2018-02-05 16:00 ` Danny Milosavljevic
2018-02-05 16:41 ` Carlo Zancanaro [this message]
2018-02-09 13:22 ` Ludovic Courtès
2018-02-09 20:51 ` David Pirotte
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=87bmh3gzhu.fsf@zancanaro.id.au \
--to=carlo@zancanaro.id.au \
--cc=dannym@scratchpost.org \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.