As with anything else in linux, the advantage is preference. But xinetd does allow for log handling and very simple security measures similar to those of firewalls. In other words, you can restrict services via xinetd to certain domains or hostnames. You can also choose what kind of error or just access logging you want to do based on the service. It allows a nice modular service management. But as for real power advantages, I see none for xinetd over inetd, I actually still use inetd. As for experience with it and Suse 7.0, I have some, and it worked without a hitch. Oh yeah, one neat thing you can due is have the xinetd.conf file include everything from a directory say /etc/xinetd.d/ and have individual files in there that correspond to each service. I think that RedHat 7 does it this way. Just an interesting way of administering things. michael On Mon, 5 Mar 2001, Ahmed Mohammad wrote:
Hello,
Is there any advantage to using xinetd over inetd? Anyone have any experience with this in 7.0?
thankx