Re: How do I find out who's using port # xxxxx

1998-05-26 Thread Mark W. Eichin
You can *also* do this with lsof: % sudo lsof -i tcp:25 COMMAND PID USER FD TYPE DEVICE SIZE/OFF INODE NAME sendmail 239 root4u inet 0x005bc810 0t0 TCP *:smtp (LISTEN) % using -i tcp:smtp works as well, "lsof -i :domain" is an example of finding either... -- To UNSUBSCRIB

Re: How do I find out who's using port # xxxxx

1998-05-23 Thread Adriano Nagelschmidt Rodrigues
Martin Bialasinski writes: [snip] > Try lsof |grep smtp You can also try: # fuser -v 25/tcp Nice, isn't it? -- Adriano -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: How do I find out who's using port # xxxxx

1998-05-23 Thread Martin Bialasinski
> "LZ" == Luiz Otavio L Zorzella <[EMAIL PROTECTED]> writes: LZ> looking at the package, I ended with "lsof -U". Now I can't quite LZ> decifrate the results. For example, let's take the most famous: LZ> sendmail on port 25. LZ> nr# lsof -U LZ> COMMANDPID USER FD TYPE DEVICE

Re: How do I find out who's using port # xxxxx

1998-05-22 Thread Luiz Otavio L. Zorzella
Martin Bialasinski writes: > > > "LOLZ" == Luiz Otavio L Zorzella <[EMAIL PROTECTED]> writes: > > LOLZ> complaining another process was using that port. > > LOLZ> I tryed to find out who was using it, but could not. Is there a way to > LOLZ> find it? (Just a note: I changed the numbe

Re: How do I find out who's using port # xxxxx

1998-05-22 Thread Martin Bialasinski
> "LOLZ" == Luiz Otavio L Zorzella <[EMAIL PROTECTED]> writes: LOLZ> complaining another process was using that port. LOLZ> I tryed to find out who was using it, but could not. Is there a way to LOLZ> find it? (Just a note: I changed the number, and it works, but I'd LOLZ> like to be able t

How do I find out who's using port # xxxxx

1998-05-22 Thread Luiz Otavio L. Zorzella
Hi, I wrote a small program that listened to a sokcet port. I wanted it to never conflict with anything, so I made it listen to a port above 6. Everything worked ok, but then, one day, it stopped working, complaining another process was using that port. I tryed to find out who was using it