[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Arm Release 1.4.0
Perfect! I'll try to provide a fix for you to test later today or tomorrow.
> I intent to try Arm in the future. Are you aware of anyone working on a port?
Nope. Jesse just finished an ebuild for Gentoo:
https://bugs.gentoo.org/show_bug.cgi?id=341731
and I'm working with Peter on a deb. But thus far no one has
volunteered to do a bsd port.
On Fri, Dec 3, 2010 at 11:34 AM, Fabian Keil
<freebsd-listen@xxxxxxxxxxxxx> wrote:
> Damian Johnson <atagar1@xxxxxxxxx> wrote:
>
>> The lsof command issued by arm [1] is:
>> lsof -nPi | grep "<process>\s*<pid>.*(ESTABLISHED)"
>>
>> I'd be happy to work with you to provide a fix, if you'd like. Once
>> upon a time I tried to use VMs to troubleshoot FreeBSD and Gentoo
>> issues (thus far they're the only platforms to give arm any trouble).
>> However, either VirtualBox, those OSes, or the combination of the two
>> made this a colossal pain in the ass. Trying to wrangle even the most
>> basic functionality out of those systems chewed up dozens of hours so
>> that's definitely *not* a road I'm going down again.
>>
>> What I'll need from you is the following:
>> - A command that, when executed as the tor user, produces connection
>> results filtered to tor's connections.
>> - Example output.
>
> tor-jail# uname -or
> FreeBSD 9.0-CURRENT
> tor-jail# su -m _tor -c /bin/csh
> tor-jail# id
> uid=256(_tor) gid=256(_tor) groups=256(_tor)
> tor-jail# procstat -f `pgrep tor` | egrep 'TCP|UDP|PID'
> PID COMM FD T V FLAGS REF OFFSET PRO NAME
> 3561 tor 4 s - rw---n-- 2 0 TCP 10.0.0.2:9050 10.0.0.1:22370
> 3561 tor 5 s - rw---n-- 2 0 TCP 10.0.0.2:9050 0.0.0.0:0
> 3561 tor 6 s - rw---n-- 2 0 TCP 10.0.0.2:9040 0.0.0.0:0
> 3561 tor 7 s - rw---n-- 2 0 UDP 10.0.0.2:53 0.0.0.0:0
> 3561 tor 8 s - rw---n-- 2 0 TCP 10.0.0.2:9051 0.0.0.0:0
> 3561 tor 14 s - rw---n-- 2 0 TCP 10.0.0.2:9050 10.0.0.1:44381
> 3561 tor 15 s - rw---n-- 2 0 TCP 10.0.0.2:33734 [scrubbed]:443
> 3561 tor 16 s - rw---n-- 2 0 TCP 10.0.0.2:47704 [scrubbed]:9001
> 3561 tor 17 s - rw---n-- 2 0 TCP 10.0.0.2:9050 10.0.0.1:46343
> 3561 tor 18 s - rw---n-- 2 0 TCP 10.0.0.2:9050 10.0.0.1:64196
> 3561 tor 19 s - rw---n-- 2 0 TCP 10.0.0.2:18856 [scrubbed]:443
> 3561 tor 20 s - rw---n-- 2 0 TCP 10.0.0.2:9050 10.0.0.1:20385
> 3561 tor 22 s - rw---n-- 2 0 TCP 10.0.0.2:9050 10.0.0.1:27541
> 3561 tor 23 s - rw---n-- 2 0 TCP 10.0.0.2:9050 10.0.0.1:21877
> (Public IP addresses scrubbed)
>
>> - Be available to test a potential fix.
>>
>> If you're up for that then I'm glad to have the help! Lets take
>> further discussion of this off the list. I don't think this is
>> generally of interest to the rest of the tor community. -Damian
>
> It's at least interesting to a part of the rest of the tor community.
> I intent to try Arm in the future. Are you aware of anyone working on a port?
>
> Fabian
>
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxxx with
unsubscribe or-talk in the body. http://archives.seul.org/or/talk/