[lug] ingreslock is listening?

[Justin-lists]

Thanks for the help. All these methods were just what I was looking for. Most specifically the netstat and lsof commands :) I also found out that it was my portsentry that was listening on the ingreslock port like I had thought. Thanks again, this is definitely handy stuff to know.

Justin

--
glow at jackmoves.com


---------- Original Message -----------
From: rm at fabula.de
To: lug at lug.boulder.co.us
Sent: Wed, 26 Jun 2002 18:05:38 +0200
Subject: Re: [lug] ingreslock is listening?

> On Wed, Jun 26, 2002 at 11:51:36AM -0400, Hugh Brown wrote:
> > On Wed, 2002-06-26 at 11:46, Paul Walmsley wrote:
> > > On 26 Jun 2002, Hugh Brown wrote:
> > > 
> > > > netstat -ap|grep ingres
> > > 
> > > hmmm, that's a neat trick with netstat ...
> > > 
> > > fuser should also work in this circumstance (as root):
> > > 
> > > fuser ingreslock/tcp
> > > fuser ingreslock/udp
> > > 
> > 
> > also as root,
> > 
> > lsof -i :portnumber
> 
> And to add to the party:
> 
>  lsof -i @nnn.nnn.nnn.nnn:portnumber
> 
> where  nnn.nnn.nnn.nnn is the address of your interface (this
> _is_ important if you have different processes listen on the
> same port but different IP adresses).
>    
> Ralf 
> 
> > > 
> > > - Paul
> > > 
> > > _______________________________________________
> > > Web Page:  http://lug.boulder.co.us
> > > Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> > > Join us on IRC: lug.boulder.co.us port=6667 channel=#colug
> > 
> > 
> > _______________________________________________
> > Web Page:  http://lug.boulder.co.us
> > Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> > Join us on IRC: lug.boulder.co.us port=6667 channel=#colug
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: lug.boulder.co.us port=6667 channel=#colug
------- End of Original Message -------