Re: can't get a pid on 3 udp sockets
From: /dev/null (dev'0x2e'null@BeginThread.com)
From: "/dev/null" <dev'0x2e'null@BeginThread.com> Date: Thu, 03 Apr 2003 05:47:20 GMT
> Actually, no. Maintained RH 6.0 since '99.
You dark-sider ;-).
> Box was kept up to
> date by hand re. security and software I use, and served well.
What security exactly?
> Nonetheless, I never grew too fond of RH.
You could rephrase that "Nonetheless I kept my sanity..."
> I banged my head a bit with Slack-current a couple months ago
> and it didn't even raise a bruise. Felt pretty good, actually.
Yeah, I bought (choke, gag) mandrake about 4-5 years ago and followed the
book that came with it to the T. Never could get it to dual with my NT box
(I was running low on spare hardware so I put it on my work computer). If I
wanted linux I'd have to boot with the floppy. Then there was the whole
swap disk ordeal. It waits until after you do the install to tell you
there's not enough swap (actually it didn't tell me, it just wouldn't work
and I couldn't figure out why - who needs a swap for a dev install on a 512M
Then I found a magical 486. Dirt cheap - free. Who installs on 486
out-of-the-box that has a good "hands on" install? So I've been with slack
What an education... I got bruises. Now I have 5 boxes that just run
terminal (sshd) and one main station that is KDE. Those 5 terminals run
iptables amoung other things, that's why I was asking about your security...
> BTW, rpcinfo now show rquotad on four priviliged ports (2 udp,
> 2 tcp), 2 nfs on udp:2049, and several nlockmgr, mountd, and status
> on ports above 32767. This box has no nfs clients, it just serves
> nfs. The clients are NetBSD, and the kernels are without nfs
> server, so I can't check the ports used by the Linux nfs client
> right now. FWIW, the NetBSD nfs clients ports are < 1024 (and
> don't show with lsof).
Thanks for all your help on this port issue. Turns out it's nfs mounts
(it's the client). I unmounted the 3 mounts one at a time and did
`netstat -nlp | grep -` and watched them disappear one at a time. I guess
that 2048 was because 2049 was in use when nfs started up...