how to stop ypbind and NIS at boot?

How do I stop NIS contacting the YP server everytime it boots, takes several
minutes to boot the machine. I don't have any use for NIS anyway.

These must be some boot script left cause I removed NIS from the startup
using 'SysvEdit'.

Conny

Conny wrote:
> How do I stop NIS contacting the YP server everytime it boots, takes several
> minutes to boot the machine. I don't have any use for NIS anyway.
>
> These must be some boot script left cause I removed NIS from the startup
> using 'SysvEdit'.
>
> Conny
>
>
When your init script is called nfs, run the following command as root:
> chkconfig nfs off
This will configure the NFS service not to be started at boot time.
You can check about the result with
> chkconfig -l

--
Christian

"Christian Riechers" <(E-Mail Removed)> skrev i meddelandet
news:(E-Mail Removed)...
> Conny wrote:
> > How do I stop NIS contacting the YP server everytime it boots, takes
several
> > minutes to boot the machine. I don't have any use for NIS anyway.
> >
> > These must be some boot script left cause I removed NIS from the startup
> > using 'SysvEdit'.
> >
> > Conny
> >
> >
> When your init script is called nfs, run the following command as root:
> > chkconfig nfs off
> This will configure the NFS service not to be started at boot time.
> You can check about the result with
> > chkconfig -l
>
> --
> Christian

Thanks for the help, but it turned out my Debian system did not have the
command 'chkconfig' :-/

On 2004-09-19, Conny <(E-Mail Removed)> wrote:

> "Christian Riechers" <(E-Mail Removed)> skrev i meddelandet
> news:(E-Mail Removed)...
>> Conny wrote:
>> > How do I stop NIS contacting the YP server everytime it boots, takes
> several
>> > minutes to boot the machine. I don't have any use for NIS anyway.
>> >
>> > These must be some boot script left cause I removed NIS from the startup
>> > using 'SysvEdit'.

>> When your init script is called nfs, run the following command as root:
>> > chkconfig nfs off
>> This will configure the NFS service not to be started at boot time.
>> You can check about the result with
>> > chkconfig -l

> Thanks for the help, but it turned out my Debian system did not have the
> command 'chkconfig' :-/

I think "chkconfig" is a RedHat-ism. Maybe "update-rc.d" will work for
you?

--

-John ((E-Mail Removed))