From: Arne Babenhauserheide <arne_bab@web.de>
To: guile-user@gnu.org
Cc: guix-devel@gnu.org
Subject: Re: GNU Shepherd 0.6.1 released
Date: Sun, 12 May 2019 01:35:28 +0200 [thread overview]
Message-ID: <874l60zhrz.fsf@web.de> (raw)
In-Reply-To: <87imugx4u8.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 575 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> We are pleased to announce the GNU Shepherd version 0.6.1, a bug-fix
> release.
Congrats!
> interface. The GNU Shepherd may also be used by unprivileged users to
> manage per-user daemons (e.g., tor, privoxy, mcron, etc.)
Is there a tutorial about using shepherd for per-user daemons? I don’t
really know how to start with it, but I would very much like to
move services from "just start this in ~/.bashrc" to shepherd.
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1076 bytes --]
next prev parent reply other threads:[~2019-05-11 23:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-11 17:45 GNU Shepherd 0.6.1 released Ludovic Courtès
2019-05-11 23:35 ` Arne Babenhauserheide [this message]
2019-05-13 7:59 ` Ludovic Courtès
2019-05-13 8:04 ` Nala Ginrut
2019-05-13 20:19 ` Arne Babenhauserheide
2019-05-14 6:12 ` Nala Ginrut
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874l60zhrz.fsf@web.de \
--to=arne_bab@web.de \
--cc=guile-user@gnu.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).