Closed GoogleCodeExporter closed 8 years ago
prorable.txt determines where to stoe all data: either in the application
folder (portable) or in the user home directory (fixed installation)
It will still try to start tor.sh (which in turn will try to start tor). You
can also turn this off by removing (or renaming) tor.sh, then it will not try
to start it and wait for the hostname file and instead immediately use the
settings torchat.ini
But there is almost never a reason to do this. The normal and recommended setup
is to start a separate instance of tor exclusively for torchat and leaving your
existing system-wide tor completely alone.
The documentation is a bit outdated, it is 2 years old, i should review and
update it.
Original comment by prof7...@gmail.com
on 26 Jan 2011 at 10:31
there is a nice table in the document that explains it. Its still valid.
From the traceback it seems you don't have tor installed on this system or the
tor binary is not in the path or you made changes to torrc.txt that are not
allowed.
What are you trying to do? TorChat is meant to operate exactly like the .deb
package will set it up. And tor should be installed and on your path (on ubuntu
at least it is). If tor is installed and tor.sh cannot find it then please open
another bug to fix tor.sh
Original comment by prof7...@gmail.com
on 26 Jan 2011 at 10:42
I explained the problem of tor.sh for debian at Issue 96, explaining why the
separate instance of tor doesn't work and resulting in "Client mode (permanent
installation)", according to the table in the documentation.
Original comment by kdg83...@trash-mail.com
on 26 Jan 2011 at 7:29
I will close this bug since the problem is originally caused by issue 96
Original comment by prof7...@gmail.com
on 27 Jan 2011 at 1:12
Except the small mistake try 21 of 20... "(1) [tc_client,2067,startPortableTor]
trying to read hostname file (try 21 of 20)"
Original comment by kdg83...@trash-mail.com
on 30 Jan 2011 at 1:40
this is only a cosmetic problem. Its trying a fixed number of times (to not get
stuck there forever) until it stops trying. The mistake here is only in the
print statement.
Original comment by prof7...@gmail.com
on 30 Jan 2011 at 2:38
Original issue reported on code.google.com by
kdg83...@trash-mail.com
on 26 Jan 2011 at 1:52