[luau] cron vs. anacron, xinetd useful?

[Tom_Gordon/RISE/HIDOE at notes.k12.hi.us]

No errors should be generated directly by having xinetd off.  Xinetd 
provides internet services and they will simply not be available with it 
off.  But if most errors go to syslog or the like in /var/log.

Using Xinetd on a Desktop system I can still see a reason to run it.  If 
you use the CUPS printing system and want it to be backwards-compatible 
with legacy lpd applications then you will want Xinetd on.

Xinetd reduces the amount of services that has to be run and frees up 
memory on the system by only running the services it provides in memory.

Personally, I love Xinetd.  I even used to have my apache run off it.  A 
great benefit is that you never have to restart the server after 
configuration changes.  Of course there are some negatives to that but the 
whole point of using Linux is figuring out why you would want or not want 
to do things a certain way by experiencing it yourself.

Happy hacking,

Tom





David Burns <burnst001 at hawaii.rr.com>
Sent by: luau-admin at videl.ics.hawaii.edu
11/01/03 01:48 PM
Please respond to luau

 
        To:     luau <luau at videl.ics.hawaii.edu>
        cc: 
        Subject:        Re: [luau] cron vs. anacron, xinetd useful?


I mean, if I turn off xinetd, and later I install
something that won't work without it, how would I know
(besides RTFM)? (Naturally I always RTFM, but I still
make mistakes.) Presumably it won't work, but will it
bomb in some identifiable characteristic fashion, or
will I just have to scratchmy head and RTFM some more
until I have an epiphany?
TB

----- Original Message -----
From: Tom_Gordon/RISE/HIDOE at notes.k12.hi.us
Date: Friday, October 31, 2003 3:07 pm
Subject: [despammed] Re: [luau] cron vs. anacron,
xinetd useful?

> If a tree falls in the woods and noone is around to
hear it, does 
> it fall? 
> You'd probably know when a service you use is no
longer 
> available.  If 
> you don't know you need it then you don't need it. 
Check what 
> depends on 
> xinetd.d.
> 
> You can see a list of ENABLED depended services by
running this:
> 
> grep -li disable.*=.*no /etc/xinetd.d/*
> 
> This looks for all xinetd.d configs that are
enabled.  You can 
> also check 
> out the directory to see which services are disabled
that depend 
> on it 
> too.
> 
> Using redhat-config-services will keep you save in
that it knows 
> how these 
> dependencies work (usually) and will warn you.
> 
> Tom
> 
> 
> If I turn off xinetd, and later it turns out I need
> it, how would I know?
_______________________________________________
LUAU mailing list
LUAU at videl.ics.hawaii.edu
http://videl.ics.hawaii.edu/mailman/listinfo/luau