From: Chris Marusich <cmmarusich@gmail.com>
To: Raghav Gururajan <rvgn@disroot.org>
Cc: Danny Milosavljevic <dannym@scratchpost.org>, help-guix@gnu.org
Subject: Re: "System Package" vs "System Service"
Date: Wed, 08 May 2019 00:18:25 -0700 [thread overview]
Message-ID: <87v9yltnwe.fsf@gmail.com> (raw)
In-Reply-To: <671f8198e5e9419e37b646a67ff5c343@disroot.org> (Raghav Gururajan's message of "Tue, 07 May 2019 05:28:46 +0000")
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]
Hi Raghav,
"Raghav Gururajan" <rvgn@disroot.org> writes:
> Hello Chris!
>
> Thank you for your email. I have already tried configuring my browser
> to use localhost's tor port as proxy, but getting error "proxy is
> refusing connection". When I check tor service with "herd status", tor
> wasn't running. When I did "herd start tor", I am getting error
> "service tor failed to start".
Just a reminder: Please bottom-post when replying on this list.
I'm sorry to hear that Tor is giving you such trouble. Maybe there is
some helpful information in one of the files in /var/log? Perhaps dmesg
has some useful output?
As a last resort, another way you might be able to debug the problem is
by attempting to manually launch Tor and watch what happens. For
example, something like this ought to mimic the way it starts:
sudo -u tor /path/to/tor -f /path/to/torrc
You'll need to replace /path/to/tor with the path to the Tor executable,
and you'll need to replace the /path/to/torrc with the path to a file
containing valid Tor configuration. I think if you make a torrc file
that contains the following, it should work (I have not tested this):
User tor
DataDirectory /var/lib/tor
PidFile /var/run/tor/tor.pid
Log notice syslog
For details on the config file syntax, see "man tor".
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-05-08 7:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-28 15:59 "System Package" vs "System Service" Raghav Gururajan
2019-04-28 16:41 ` Danny Milosavljevic
2019-04-29 13:28 ` Raghav Gururajan
2019-05-06 3:24 ` Chris Marusich
2019-05-07 5:28 ` Raghav Gururajan
2019-05-08 7:18 ` Chris Marusich [this message]
2019-05-08 7:43 ` Raghav Gururajan
2019-05-09 6:01 ` Chris Marusich
2019-05-09 14:29 ` 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
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=87v9yltnwe.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=dannym@scratchpost.org \
--cc=help-guix@gnu.org \
--cc=rvgn@disroot.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).