From: ng0 <contact.ng0@cryptolab.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Services: gnunet. (require help)
Date: Sat, 21 Jan 2017 12:04:02 +0000 [thread overview]
Message-ID: <871svwhb65.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <8760l9dfr4.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> contact.ng0@cryptolab.net skribis:
>
>> I've been changing this service back and forth and back again, now
>> running on one computer, and leaving aside all confusion you will see
>> in there, gnunet needs at least a .config/gnunet file, the rest should
>> be automatically created. unless it isn't, which was the case
>> here. And all shepherd gives me on the computer where I run the branch
>> is: starting service gnunet. couldn't start service gnunet.
>
> You can use
>
> (make-forkexec-constructor … #:log-file "/var/log/gnunet.log")
>
> to log stdout/stderr from GNUnet.
>
> HTH!
>
> Ludo’.
Thanks, that might help a bit.
Compared to OpenRC and systemd, shepherd guixsd-specific services
sometimes have an high learning curve.
--
♥Ⓐ ng0 -- https://www.inventati.org/patternsinthechaos/
next prev parent reply other threads:[~2017-01-21 12:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 16:50 Services: gnunet. (require help) contact.ng0
2017-01-18 16:50 ` [PATCH] gnu: services: Add gnunet-service contact.ng0
2017-01-20 13:26 ` Services: gnunet. (require help) Ludovic Courtès
2017-01-21 12:04 ` ng0 [this message]
2017-01-21 22:50 ` Chris Marusich
2017-01-23 11:53 ` ng0
2017-01-23 12:08 ` Ricardo Wurmus
2017-02-24 21:48 ` ng0
2017-02-24 21:53 ` ng0
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=871svwhb65.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
--to=contact.ng0@cryptolab.net \
--cc=guix-devel@gnu.org \
--cc=ludo@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).