[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #7813 [arm]: arm doesn't consistently list connections on OpenBSD 5.1
#7813: arm doesn't consistently list connections on OpenBSD 5.1
--------------------------+-------------------------------------------------
Reporter: mischief | Owner: atagar
Type: defect | Status: assigned
Priority: normal | Milestone:
Component: arm | Version:
Keywords: OpenBSD, arm | Parent:
Points: | Actualpoints:
--------------------------+-------------------------------------------------
Comment(by fk):
Replying to [ticket:7813 mischief]:
> going with the theme of calling external programs for information, i
think an appropriate solution is to use the fstat(1) program instead of
lsof(1), which is available in the base distribution of OpenBSD, FreeBSD,
and NetBSD.
I don't think fstat is appropriate for FreeBSD as it doesn't show the
connection details:
{{{
USER CMD PID FD MOUNT INUM MODE SZ|DV R/W
_tor tor 2567 text /usr/jails/tor-jail 4276 -r-xr-xr-x
14677809 r
_tor tor 2567 wd /usr/jails/tor-jail 3715 drwx------
13 r
_tor tor 2567 root /usr/jails/tor-jail 3 drwxr-xr-x
21 r
_tor tor 2567 jail /usr/jails/tor-jail 3 drwxr-xr-x
21 r
_tor tor 2567 0 /usr/jails/tor-jail/dev 25 crw-rw-rw-
null rw
_tor tor 2567 1 /usr/jails/tor-jail/dev 25 crw-rw-rw-
null rw
_tor tor 2567 2 /usr/jails/tor-jail/dev 25 crw-rw-rw-
null rw
_tor tor 2567 3
_tor tor 2567 4* internet stream tcp fffffe0077706000
_tor tor 2567 5* internet stream tcp fffffe007504a000
_tor tor 2567 6* internet dgram udp fffffe0017ad3188
_tor tor 2567 7* internet stream tcp fffffe007505bb70
_tor tor 2567 8* internet stream tcp fffffe007505b7a0
_tor tor 2567 9* local stream fffffe0017b00c30
_tor tor 2567 10 /usr/jails/tor-jail/dev 65 crw-rw----
pf rw
_tor tor 2567 11 /usr/jails/tor-jail 862 -rw-r-----
24076 w
_tor tor 2567 12 /usr/jails/tor-jail 863 -rw-r-----
12951160 w
_tor tor 2567 13 /usr/jails/tor-jail/dev 25 crw-rw-rw-
null w
_tor tor 2567 14 - 3721 -rw------- 0 rw
_tor tor 2567 15* internet stream tcp fffffe0077a94b70
}}}
Apparently it also gets the working directory wrong, and by the way it
looks questionable in the OpenBSD example given above as well.
"Arm hanging" is a problem I reported before in the past and I don't think
it has anything to do with lsof. I've locally patched stem to use procstat
instead of lsof (for other reasons) and it didn't make a difference.
My impression is that only the GUI becomes unresponsive, control port
traffic is still logged. It could be related to redraws, but I haven't
recently looked at it.
It would probably help debugging if arm would catch SIGHUP to "reboot the
GUI" after logging the current state.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7813#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs