From: Julian Flake <julian@flake.de>
To: help-guix@gnu.org
Subject: Home (shepherd) services: multiple instances
Date: Sun, 10 Nov 2024 01:08:09 +0100 [thread overview]
Message-ID: <875xowj6hi.fsf@flake.de> (raw)
Hi Guixers,
I have a question about home-*-service-types that create a user's
shepherd service.
If I have such services in my home-environment and login, logout
and
login again, I have multiple instances of the processes running,
the
shepherd should manage. Shouldn't the shepherd services (and the
corresponding processes) automatically be stopped (killed), if I
log
out from all ttys? This does not seem to be the case.
I observed this with home-mcron-service-type,
home-syncthing-service-type, home-dbus-service-type and
home-pipewire-service-type. So basically all my user's shepherd
services are affected.
Do I misunderstand something or is this the intended behavior?
Cheers,
nutcase
next reply other threads:[~2024-11-10 0:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-10 0:08 Julian Flake [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-09 23:50 Home (shepherd) services: multiple instances Julian Flake
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875xowj6hi.fsf@flake.de \
--to=julian@flake.de \
--cc=help-guix@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).