inetd & xinetd

I

itsmike

Registered
Just curious, why does OSX (at least 10.2.4) have inetd running, even though no services are active in inetd.conf. And even more confusing why is inetd still around when OSX uses xinetd for services now?

Was this just something left in during some upgrade in the past?

-i
 
There are still a few services in inetd that xinetd doesn't handle. Admittedly, those services aren't even enabled by default in OS X, but some people may be using them, so inetd is still around.
 
I guess since it's a listener and places almost no demands on the system, they decided to cover their bases and keep it running. I shut inetd off just for aesthetic purposes, but I suppose you could leave it running in any situation and not worry about it.
 
coming from the paranoid unix admin point of view, if it isn't doing anything.. shut it off. And get rid of it. I am assuming a normal system not running such services that xinetd can handle (which would those be anyway?) can do without inetd completely.

-i
 
coming from the paranoid unix admin point of view, if it isn't doing anything.. shut it off. And get rid of it. I am assuming a normal system not running such services that xinetd can handle (which would those be anyway?) can do without inetd completely.

-i
 
Yeah, it's not going to cause any problems, but you might as well kill it (started up in /System/Library/Startup Items/IPServices/IPServices).

I have xinetd running on almost all my *nix machines around here, and I've never encountered limitations. Darkshadow, what are the services you say inetd can cover that xinetd can't? I'm curious, now.
 
You must log in or register to reply here.
Back
Top