On Monday 22 December 2003 05:01, Dean Pullen wrote:
>Ok back at work...
>
>There seems to be no xinetd or inetd messages during startup (I
> performed a dmesg > dmesg.txt and searched for xinetd/inetd).
>
>Is it worth trying to install xinetd from the supplied SuSE rpms?
>
>Note: The guy who first configured these machines has put various
> networking scripts in /etc/init.d/ is this similar to inetd etc?
>
>
>Dean.

I would say to do that only if inetd isn't being used on that system.

And I've no idea how hard it would be to convert an inetd using 
installation into an xinetd using installation short of putting the 
newer versions cd in the drive and rebooting.  Most installers will 
let you update a system, usually without losing any data.  But I've 
not had 100% success doing that, more like 90% I think.

To answer the last question, no, there is a dividing line there as the 
startup scripts for this and that get put into /etc/init.d, and are 
linked to various names starting with S99 or K43 in the various rcx.d 
dirs, where x is a number.  What those do is setup the sequenceing of 
the machines personality, so the S99local is the last thing started, 
and K01local would be the first thing shut down when you do a reboot, 
or an init to a different runlevel than you are running at the 
moment.

Xinetd.d's stuff isn't related to that.  The basic diff between inetd 
and xinetd is that xinetd starts things on demand, whereas inetd 
started them and left them sleeping, using a bit more memory, and far 
less security.

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.