Red Hat Bugzilla – Bug 702864
tsocks(8) man page: replace TSOCKS_CONFFILE with TSOCKS_CONF_FILE
Last modified: 2011-05-24 23:05:32 EDT
Description of problem:
Quoting from the man page for tsocks(8):
This environment variable overrides the default location of the
tsocks configuration file.
Though, I can not use it.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create $HOME/.tsocks.conf
2. export TSOCKS_CONFFILE=$HOME/.tsocks.conf
3. tsocks koji build --scratch dist-6E-epel SRPMS/satchmo-0.9.1-1.20110418hg3126f1733ad4.fc14.src.rpm
22:11:37 libtsocks(20667): Could not open socks configuration file (/etc/tsocks.conf), assuming all networks local
$HOME/.tsocks.conf should be used
[ciupicri@hermes rpmbuild]$ cat $TSOCKS_CONFFILE
server = localhost
port = 9080
The man page says that the environment variable won't be used if tsocks is compiled with --disable-envconf, but according to the RPM SPEC this doesn't seem the case.
Brief look at the source code tells this is a typo in the manual. Try $TSOCKS_CONF_FILE instead.
Yes that did the trick. Thank you!
tsocks-1.8-0.8.beta5.fc15 has been submitted as an update for Fedora 15.
tsocks-1.8-0.8.beta5.fc14 has been submitted as an update for Fedora 14.
tsocks-1.8-0.8.beta5.fc13 has been submitted as an update for Fedora 13.
* should fix your issue,
* was pushed to the Fedora 14 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing tsocks-1.8-0.8.beta5.fc14'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
tsocks-1.8-0.8.beta5.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
tsocks-1.8-0.8.beta5.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
tsocks-1.8-0.8.beta5.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.