From: Tobias Geerinckx-Rice <me@tobias.gr>
To: 35417-done@debbugs.gnu.org
Subject: bug#35417: Tor Service
Date: Wed, 24 Apr 2019 20:53:50 +0200 [thread overview]
Message-ID: <87wojj1bgh.fsf@nckx> (raw)
In-Reply-To: <9db8b9d241902804f6161274028bcf4ee552a26c.camel@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
Raghav,
Raghav Gururajan wrote:
> Including "tor-service-type" does not invoke and add "tor"
> package into
> the system.
To use the ‘tor’ command, like any other package, you must install
the ‘tor’ package into either the system profile (using
SYSTEM-PACKAGES) or that of your user (using ‘guix package’).
I'd recommend SYSTEM-PACKAGES in this case so the tor commands
will always match the version of Tor used by the service.
This is by design; services can't pollute the environment of
users, including the system profile. That's a good thing.
> Therefore, "tor-service-type" is of little or no use, if it does
> not
> invoke and add "tor" package into the system.
That's just not true. The tor service does its job and works just
fine without the ‘tor’ command. I just checked both of my Tor
nodes (both run Guix :-) and neither of them have ‘tor’ installed
into any profile. Nyx and herd (and emacs torrc) are all I need
to administrate them.
I'm closing this because there's no bug here…
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-04-24 18:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 16:34 Tor Service Raghav Gururajan
2019-04-24 17:02 ` bug#35417: " Julien Lepiller
2019-04-24 17:02 ` Julien Lepiller
2019-04-25 11:56 ` ng0
2019-04-25 11:56 ` ng0
2019-04-24 18:01 ` Raghav Gururajan
2019-04-24 18:53 ` Tobias Geerinckx-Rice [this message]
2019-04-25 3:42 ` bug#35417: closed (Re: Tor Service) Raghav Gururajan
2019-04-25 9:10 ` Raghav Gururajan
2019-04-25 18:31 ` Tobias Geerinckx-Rice
2019-04-25 9:24 ` Raghav Gururajan
2019-04-25 9:59 ` Julien Lepiller
2019-04-25 10:02 ` Raghav Gururajan
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wojj1bgh.fsf@nckx \
--to=me@tobias.gr \
--cc=35417-done@debbugs.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.