Re: [PLUG] xinetd v. inetd (was: starting a program at boot)

[Noah silva <nsilva@atari-source.com>]

well it also means that when installing a service, you could just copy one
file, instead of trying to EDIT a config file, which is a better idea to
me.

but...

inetd works fine, and them switching it like that and having it disabled
by default catches people off guard.

 -- noah silva 

On Fri, 14 Jun 2002, gabriel rosenkoetter wrote:

> On Fri, Jun 14, 2002 at 11:04:58AM -0400, epike@isinet.com wrote:
> > Offtopic, whatever happened to /etc/inetd.conf which redhat
> > replaced with the /etc/xinetd.d/ directory, what does the other
> > distros use?  Which one is more correct?
> 
> Everyone else in the world still uses inetd. xinetd is, imho, just a
> bad idea. The theory is that having a bunch of files, one for each
> service, makes things easier to manage. It's not totally
> off-the-wall thinking; it means that multiple sysadmins editing
> inetd settings at the same time won't run into each other. But how
> often does inetd *really* need to be edited?
> 
> -- 
> gabriel rosenkoetter
> gr@eclipsed.net
> 


______________________________________________________________________
Philadelphia Linux Users Group       -      http://www.phillylinux.org
Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce
General Discussion  -  http://lists.phillylinux.org/mail/listinfo/plug