Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#26762 - [tor] deamon doesn't work
Attached to Project:
Community Packages
Opened by thefclef777 (thefclef777) - Sunday, 06 November 2011, 00:43 GMT
Last edited by Lukas Fleischer (lfleischer) - Monday, 07 November 2011, 06:48 GMT
Opened by thefclef777 (thefclef777) - Sunday, 06 November 2011, 00:43 GMT
Last edited by Lukas Fleischer (lfleischer) - Monday, 07 November 2011, 06:48 GMT
|
DetailsDescription:
community/tor 0.2.2.34-1 Additional info: when i run "/etc/rc.d/tor start" it just sticks on "busy" which really affects my bootup time... so i added a "&" to the end of /usr/bin/tor -f ${TOR_CONF} ${TOR_ARGS} &>/dev/null so it just goes to "done" idk.. |
This task depends upon
Closed by Lukas Fleischer (lfleischer)
Monday, 07 November 2011, 06:48 GMT
Reason for closing: Not a bug
Monday, 07 November 2011, 06:48 GMT
Reason for closing: Not a bug
Comment by Lukas Fleischer (lfleischer) -
Sunday, 06 November 2011, 23:46 GMT
Works for me. Can you reproduce that behavior when using the default config?
Comment by thefclef777 (thefclef777) -
Monday, 07 November 2011, 03:54 GMT
haha sorry nope went away... must have been a misplaced firewall rule or something but the daemon clearly wasn't it then.... again sorry