The desktop machine is giving me more grief, however. I've closed all ports except 22 and 839. I have no idea what service runs on port 839(TCP, BTW), and neither does nmap or netstat. Does anyone know what this is, or where I can find out what service runs on port 839?

EDIT: What output do you get when you type the command above?

Derek fucked around with this message on 09-24-2005 at 05:08 PM.

It seems that whatever the service is, it's listening on localhost only. Portscanning from another machine doesn't mark it as open; 22 is the only open port. I think I can consider the issue resolved.

Again, my default assumption is that you have mountd running (most common thing it might be) and it's bound to lo only.

quote:

---

Karnaj stumbled drunkenly to the keyboard and typed:
I piped netstat to grep and figured out that it was famd. So, no biggie. If I somehow removed it from my laptop with no harm done, I'll double check this one and remove it.

---

Yea, more NFS stuff as RIG is saying. Unless you know you want it, getting rid of it probably won't destroy anything.

quote:

---

Alidane put down Tada! magazine long enough to type:
Yea, more NFS stuff as RIG is saying. Unless you know you want it, getting rid of it probably won't destroy anything.

---

Apparently, Gnome also depends on FAM for some reason. I see why it never raised it stink on my laptop; I did a base install, then installed the X server and KDE as disparate components. Gnome never got installed, so it never bitched at me for removing it. I have a larger hard drive on my desktop, however, so I just checked the Desktop Environment when I installed the OS. Oh well, I'll just break the symlinks and remove the startup script.

Problem solved, thanks for the input, everyone.