Package: socat
Version: 1.7.1.3-1
Severity: normal
Socat terminates early when used as a forwarding daemon through a tor
daemon. With a tor instance listening on port 9050, this is the socat
command:
socat -T9999999 -s\
TCP4-LISTEN:12345,ignoreeof\
SOCKS4A:127.0.0.1:nntp.aioe.org:563,socksport=9050,ignoreeof
The syntax above prevents termination due to a timeout ("-T9999999"),
an EOF ("ignoreeof"), or a non-fatal error ("-s"). So the *only*
reason it should terminate is if there is a fatal error or the
connection is idle for over 115 days. However, it terminates the same
day it's launched, and does so with an error code of 0.
A news client is able to browse some newsgroups, read messages, and
respond, but then for no apparent reason the connection dies
eventually.
-- System Information:
Debian Release: 6.0.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages socat depends on:
ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib
ii libreadline5 5.2-7 GNU readline and history libraries
ii libssl0.9.8 0.9.8o-4squeeze13 SSL shared libraries
ii libwrap0 7.6.q-19 Wietse Venema's TCP wrappers libra
socat recommends no packages.
socat suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
