On Fri, 23 Mar 2001, Jack Byers wrote:
> On both my rhat 5.2 system and my rhat 6.2 system:
>
> linuxconf appears in /etc/inetd.conf
>
> and also appears as a result of
> /sbin/chkconfig --list
>
> I was under the impression that in general,
> services were controlled
> by either
> inetd
> or
> were 'standalone daemons' controlled by chkconfig.
>
> ie not both inetd and chkconfig
>
> Am I wrong?
>
> What gives with linuxconf being used in both?
>
>
> I would like to turn off linuxconf and this seems easy enough
> just commenting it out in inetd.conf
> and
> turning it off with chkconfig.
>
> but again, do I have to do both?
>
> I will experiment with this of course
> but I would like to know general good practice....
> thanks
> Jack
>
The problem here is that linuxconf can be run in several modes. When it
is run from /etc/rc.d/init.d, it is not being launched as a daemon. It
is being run to check/change systems settings, and then it exits. When
it is launched from inetd. it is being run for remote administration of
the system, and is indeed being run as a daemon. (It exits when the
connection is closed.)
Now, as for the best way to disable linuxconfig, many on the list wil
tell you to run "rpm -e linuxconf". That is the way I preferre to do
it, but you can do it the way you have discribed as well. One thing to
be aware of, unless you go into linuxconf and disable web access, it
will put an entry back into /etc/inet.d the next time you run it.
Mikkel
--
Do not meddle in the affairs of dragons,
for you are crunchy and taste good with ketchup.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
