On Sat, 4 Aug 2001, Mike Chambers wrote:

> ----- Original Message -----
> From: "Craig White" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Saturday, August 04, 2001 7:37 AM
> Subject: RE: inetd.conf how to install this?
>
>
> > > > Check for and edit /etc/xinetd.d/ipop3 etc and change the line
> > > >
> > > > disable = yes
> > > > to
> > > > disable = no
> > >
> > > Can also use below, which works for all services in xinetd..
> > >
> > > chkconfig service-name on/off
> > > service xinetd restart
> > >
> > ----
> > Not the same thing - if you start the service as a standalone, you don't
> get
> > the safeguards of ACL's of xinetd. Security is the purpose of xinetd.
> >
> > Services such as pop are probably better off started and managed by
> xinetd.
>
> I think you misunderstand what is going on.  The chkconfig command just
> turns the service IN xinetd (can even use it for the stand-alone ones too)
> on or off, chkconfig ipop3 on/off, nothing more, nothing less (just an
> easier way to make it disable=yes/no instead of editing the files manually).
> Then you are restarting xinetd so those changes take affect.
>
> Mike
I see an awful lot of advice to restart xinetd after doing a "chkconfig
<service> on|off".  My experience is that the service is available or not
right away.  My conclusion is that chkconfig sends the appropriate signal
to xinetd, probably SIGHUP.



          Bill in Denver




_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list

Reply via email to