From: "jordila@librebits.info" <jordila@librebits.info>
To: help-guix@gnu.org
Subject: herd service "conflicts / will not be respawned" issue ?
Date: Thu, 15 Dec 2022 16:41:00 +0100 [thread overview]
Message-ID: <28b6-639b4000-21-6869e600@227200> (raw)
Hi guixers !
I'm learning the guix (in general) and the herd (in particular) sorcery... xDD .
Okey, i've setup Syncthing as a herd service, in my /etc/configuration.scm file . See below the relevant parts of the file :
;; Indicate which modules to import to access the variables
;; used in this configuration.
(use-modules (gnu) (nongnu packages linux))
(use-service-modules cups desktop networking ssh xorg syncthing)
(operating-system
[ OMMITED .. there is MOREE STUFF HERE... ;-) ]
;; Below is the list of system services. To search for available
;; services, run 'guix system search KEYWORD' in a terminal.
(services
(append (list
;; To configure OpenSSH, pass an 'openssh-configuration'
;; record as a second argument to 'service' below.
(service openssh-service-type)
(service xfce-desktop-service-type)
(set-xorg-configuration
(xorg-configuration (keyboard-layout keyboard-layout)))
(service syncthing-service-type
(syncthing-configuration (user "fenix"))))
Okey, Syncthing is running fine (as i can see it doing his job ! )... What now is confusing to me is the following reporting :
fenix@rigel ~/latj_hugo$ sudo herd status syncthing-fenix
Status of syncthing-fenix:
It is started.
Running value is 376.
It is enabled.
Provides (syncthing-fenix).
Requires (loopback).
Conflicts with ().
Will not be respawned.
fenix@rigel ~/latj_hugo$
What am i missing ?
Thanks, Thanks, Thanks
F
next reply other threads:[~2022-12-15 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 15:41 jordila [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-21 0:01 herd service "conflicts / will not be respawned" issue ? Nathan Dehnel
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=28b6-639b4000-21-6869e600@227200 \
--to=jordila@librebits.info \
--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).