use fuser.
ex
fuser -n udp 757
that will give you the pid.

Greg and Chris, thank you very much.

These ports appeared to be used by inetd.

Regards,
Mikhail

Mikhail Zotov wrote:
> Greg and Chris, thank you very much.
>
> These ports appeared to be used by inetd.

That is suspicious, 755 & 757 are unused according to my copy of the
official list & AFAIK inetd uses no ports itself. Trojan backdoor? rootkit?

--
Merci........Yvan I did not want to repeat other people's mistakes.
So I made new mistakes of my own.
Boy did I invent some good ones!

bq434@freenet.carleton.ca (Yvan Loranger) wrote in message news:<cas0d3$lop$1@freenet9.carleton.ca>...
> Mikhail Zotov wrote:
> > Greg and Chris, thank you very much.
> >
> > These ports appeared to be used by inetd.
>
> That is suspicious, 755 & 757 are unused according to my copy of the
> official list & AFAIK inetd uses no ports itself. Trojan backdoor? rootkit?

Thanks for the reply, Yvan.

A rootkit was the first thing I thought about but chkrootkit
found nothing. Surely, this is not a 100% warranty but...

I still don't know why was inetd listening to these ports but
it doesn't listen anymore after I have upgraded the kernel.
All this took place at a Slackware 9.0 PC. A Slackware 9.1 PC
with the same services opened at inetd.conf doesn't have such
a problem.

Regards,
Mikhail