On Fri, Jun 23, 2006 at 10:53:46PM -0400, hendrik@topoi.pooq.com wrote: > On Fri, Jun 23, 2006 at 03:39:37PM -0700, Andrew Sackville-West wrote: > > Has anyone else seen this? > > > > in the last few days tiger has started reporting: > > > > OLD: --WARN-- [lin002i] The process `-' is listening on socket 1661 > > (TCP) on > > +every interface. > > NEW: --WARN-- [lin002i] The process `-' is listening on socket 2309 > > (TCP) on > > +every interface. > > > > but a lsof -i :1661 or :2309 returns nothing. > > > > I get all the usual suspect listening such as rpc-stat.d, and that's > > fine, its these `-' processes that concern me. unfortunately my google > > skills are not sufficient to get any info out of a search string with > > `-' in it... > > > > I get processes like this, too. Two of them, every time. > > Runnuing etch. > okay, it just kicked out another report, well, two hours ago anyway and I get this: OLD: --ERROR-- [init001e] Don't have required command LSOF. OLD: --WARN-- [lin002i] The process `-' is listening on socket 1024 (UDP) on +every interface. OLD: --WARN-- [lin002i] The process `-' is listening on socket 2049 (TCP) on +every interface. OLD: --WARN-- [lin002i] The process `-' is listening on socket 2049 (UDP) on +every interface. OLD: --WARN-- [lin002i] The process `-' is listening on socket 2309 (TCP) on +every interface. OLD: --WARN-- [lin002i] The process `X' is listening on socket 6000 (TCP) on +every interface. of course, they're all OLD reports, but the wierd things is the first line as I definitely have lsof.... so this is interesting, nmap localhost returns ... 2049/tcp open nfs ... but lsof -i returns nothing for that port.... clearly there is something going on here that I don't understand. A
Attachment:
signature.asc
Description: Digital signature