Elaborate on the need to re-login on Debian-based systems to use tor following usermod

Starting bitcoind with `-onlynet=onion` immediately after adding bitcoind user to debian-tor group will yield the following notice on debug.log:

"tor: Authentication cookie /run/tor/control.authcookie could not be opened (check permissions)"

Elaborate on the need to re-login to ensure debian-tor group has been applied to bitcoind user after:

	sudo usermod -a -G debian-tor username

Verification can be done via `groups` command in shell.
This commit is contained in:
clashicly 2019-09-12 00:55:05 -04:00 committed by clashic
parent 2324aa1dc4
commit 706340150f

View file

@ -114,7 +114,10 @@ preconfigured and the creation of a hidden service is automatic. If permission p
are seen with `-debug=tor` they can be resolved by adding both the user running Tor and are seen with `-debug=tor` they can be resolved by adding both the user running Tor and
the user running bitcoind to the same group and setting permissions appropriately. On the user running bitcoind to the same group and setting permissions appropriately. On
Debian-based systems the user running bitcoind can be added to the debian-tor group, Debian-based systems the user running bitcoind can be added to the debian-tor group,
which has the appropriate permissions. which has the appropriate permissions. Before starting bitcoind you will need to re-login
to allow debian-tor group to be applied. Otherwise you will see the following notice: "tor:
Authentication cookie /run/tor/control.authcookie could not be opened (check permissions)"
on debug.log.
An alternative authentication method is the use An alternative authentication method is the use
of the `-torpassword=password` option. The `password` is the clear text form that of the `-torpassword=password` option. The `password` is the clear text form that