Re: can't get a pid on 3 udp sockets
From: Vic Abell (abe@purdue.edu)
Date: 04/03/03
- Next message: Khayman: "Re: New MS Vulnerability?"
- Previous message: Nico Kadel-Garcia: "Re: chkrootkit error on install"
- In reply to: Ed Hynan -- evh at ehynan dot com: "Re: can't get a pid on 3 udp sockets"
- Next in thread: Ed Hynan -- evh at ehynan dot com: "Re: can't get a pid on 3 udp sockets"
- Reply: Ed Hynan -- evh at ehynan dot com: "Re: can't get a pid on 3 udp sockets"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: abe@purdue.edu (Vic Abell) Date: 3 Apr 2003 05:56:31 -0800
ehynan@cloud9dotnet.false (Ed Hynan -- evh at ehynan dot com) wrote in message news:<v8nac970mjae85@corp.supernews.com>...
> FWIW, the NetBSD nfs clients ports are < 1024 (and
> don't show with lsof).
FWIAW, lsof documentation (e.g., the FAQ) is very clear on this.
If a port is not bound to an open socket file, lsof won't find it.
(After all, lsof stands for LiSt Open Files and there is no open
file.) The lsof FAQ points out that some kernels reserve ports
internally and never bind them to open files.
Vic Abell, lsof author
- Next message: Khayman: "Re: New MS Vulnerability?"
- Previous message: Nico Kadel-Garcia: "Re: chkrootkit error on install"
- In reply to: Ed Hynan -- evh at ehynan dot com: "Re: can't get a pid on 3 udp sockets"
- Next in thread: Ed Hynan -- evh at ehynan dot com: "Re: can't get a pid on 3 udp sockets"
- Reply: Ed Hynan -- evh at ehynan dot com: "Re: can't get a pid on 3 udp sockets"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|