On Fri, 25 Aug 2000, Fernando Rowies wrote:
> Hello!
>
> I have installed bind in RH 6.1 and don't start as a daemon
> after system boot up.
>
> I use this command:
>
> rpm -i bind-8.2.1-7.i386.rpm
>
> when I install it.
> Appears to be that the installation is correct, because of
> the startup scripts installed in the process:
> /etc/rc.d/init.d/named
> /etc/rc.d/rc0.d/K45named
> /etc/rc.d/rc1.d/K45named
> /etc/rc.d/rc2.d/K45named
> /etc/rc.d/rc3.d/K45named
> /etc/rc.d/rc4.d/K45named
> /etc/rc.d/rc5.d/K45named
> /etc/rc.d/rc6.d/K45named
>
> What happen?
>
> TIA
>
> --
> Fernando Rowies
> SFA Informatica 54-11-4433-2398
> Nuestro sitio en la red: www.sfanet.com.ar
>
>
There are a couple more steps in installing named besides installing the
RPM. You have the first step done. Now you have to configure it.
After you have it configured, you can then set it to start on boot.
You can use chkconfig or ntsysv to turn it on after you have it
configured. Most network daemons are not configured to start after
installion from the RPM any more - it is more secure this way.
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
