|
|
2010-02-08
, 19:21
|
|
Posts: 515 |
Thanked: 266 times |
Joined on Nov 2009
@ Oelsted, Denmark
|
#2
|

|
|
2010-02-08
, 20:01
|
|
|
Posts: 963 |
Thanked: 626 times |
Joined on Sep 2009
@ Connecticut, USA
|
#3
|
|
|
2010-02-09
, 05:39
|
|
Posts: 13 |
Thanked: 3 times |
Joined on Feb 2010
@ Peking,China
|
#4
|
You could also try netstat -an | grep 39500 to se if any (local) processes are connected to that port...
|
|
2010-02-09
, 17:19
|
|
Posts: 328 |
Thanked: 101 times |
Joined on Dec 2009
|
#5
|
|
|
2010-02-09
, 18:45
|
|
|
Posts: 103 |
Thanked: 20 times |
Joined on Jan 2008
|
#6
|
|
|
2010-02-10
, 02:06
|
|
Posts: 452 |
Thanked: 522 times |
Joined on Nov 2007
|
#7
|
|
|
2010-02-16
, 09:58
|
|
Posts: 452 |
Thanked: 522 times |
Joined on Nov 2007
|
#8
|
when I'm running netstat,I found keepassx is listening tcp connections from public network(not 127.0.0.1)
why?
#lsof -p 3988
keepassx 3988 user 18r IPv4 67057 TCP *:39500 (LISTEN)
keepassx 3988 user 20r IPv4 67063 UDP *:1900
keepassx 3988 user 21w IPv4 67070 UDP *:39400
Last edited by snnn; 2010-02-08 at 07:34.