From: Tangonov <tn@eml.cc>
To: GUIX Help <help-guix@gnu.org>
Subject: Re: Guix home user-level shepherd services
Date: Wed, 15 Jun 2022 18:09:17 -0700 [thread overview]
Message-ID: <87tu8lpg2l.fsf@eml.cc> (raw)
In-Reply-To: <87v8t1qz9w.fsf@eml.cc>
[-- Attachment #1.1: Type: text/plain, Size: 3392 bytes --]
Ok, it seems as though I had some bash configuration issues. My
"$(inline commands)" made things unhappy for some reason.
I resolved them, and shepherd started working...except that herd
was totally bound up and not responsive. I had to kill it to
reconfigure.
I assumed this is because the services were holding stuff up...so
I tried a forked config:
#+BEGIN_SRC scheme
(service home-shepherd-service-type
(home-shepherd-configuration
(services (list
(shepherd-service
(provision '(syncthing))
(start #~(make-forkexec-constructor
"syncthing" #:user #:t))
(stop #~(make-kill-destructor))
(documentation
"Synchronize folders to other
device"))
(shepherd-service
(provision '(pantalaimon))
(start #~(make-forkexec-constructor
"pantalaimon" #:user #:t))
(stop #~(make-kill-destructor))
(documentation
"Crypto back-end server for
ement.el"))))))
#+END_SRC
The forked service does not seem to work :/
#+BEGIN_QUOTE
λ herd start pantalaimon
herd: exception caught while executing 'start' on service
'pantalaimon':
Throw to key `match-error' with args `("match" "no matching
pattern" "pantalaimon")'.
#+END_QUOTE
Tangonov <tn@eml.cc> writes:
> Oh! I almost forgot, the error messages from guix home
> container. It's worth mentioning that these are user packages.
> They're not installed on the root level.
>
> Starting services… Comparing
> /gnu/store/non-existing-generation/profile/share/fonts and
> /gnu/store/c04qxlqgawnbb0k08acwdd6sk2kjc1i2-home/profile/share/fonts…
> done (same) Evaluating on-change
> gexps.
>
> On-change gexps evaluation finished.
>
> sh: line 1: syncthing: command not found Service syncthing
> could not be started. sh: line 1: pantalaimon: command
> not found Service pantalaimon could not be started.
>
> Tangonov <tn@eml.cc> writes:
>
> Hello Guix!
>
> I don't seem to be able to start Shepherd services from my guix
> home config. The services fail to start, despite being
> startable from the command line from both reconfigure &
> container.
>
> Here's what my services look like:
>
> (home-environment (packages (specifications->packages (append
> %base-packages %emacs %multimedia %browsers
> %chat-clients %devel))) (services (list ; … bash services
> (service home-shepherd-service-type
> (home-shepherd-configuration (services (list (shepherd-service
> (provision '(syncthing)) (start
> #~(make-system-constructor "syncthing")) (stop
> #~(make-kill-destructor)) (documentation "Synchronize folders
> to
> other device")) (shepherd-service (provision '(pantalaimon))
> (start #~(make-system-constructor "pantalaimon"))
> (stop #~(make-kill-destructor)) (documentation "Crypto back-end
> server for ement.el")))))))))
>
> Thanks again for the help & software
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]
next prev parent reply other threads:[~2022-06-16 1:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 23:18 Guix home user-level shepherd services Tangonov
2022-06-15 23:28 ` Tangonov
2022-06-16 1:09 ` Tangonov [this message]
2022-06-16 16:19 ` Fredrik Salomonsson
2022-06-16 18:36 ` Tangonov
2022-06-16 21:45 ` Fredrik Salomonsson
2022-06-19 12:23 ` Efraim Flashner
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=87tu8lpg2l.fsf@eml.cc \
--to=tn@eml.cc \
--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).