Mike Chambers wrote:
>
> > 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.
>
---------
OK then I am confused. I have only been using linux for 2 years so I
still have much to learn but I thought that xinetd was a drop in
replacement for inetd and for the ACL's to work, the various services
had to be launched from the wrappers and not launched as a separate
service. Are you saying that xinetd ACL's are in place merely if
'disable=no' is in the appropriate file within /etc/xinetd.d at the time
xinetd is started/restarted?
Craig
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
