Results 1 to 5 of 5

Thread: Starting named at boot time

  1. #1
    igodit Guest

    Default Starting named at boot time

    After following the instruction on Unix Wiz on 'Starting named at boot time' I notice that after creating the symbolic links:

    # cd /etc/rc.d
    # ln -s ../init.d/named rc2.d/S11named
    # ln -s ../init.d/named rc3.d/S11named

    I rebooted to test it, but I had to manually start the named,, again.

    After checking my files, I noticed that the color on the new files are different from those that were there. The new files are Black/Red while the existing files are Teal(Green).

    I'm using SuSE 9.0 and the BIND was setup from the tar.gx files.

    -- Also how can I know what services started up at boot time?

  2. #2
    Join Date
    Sep 2002
    Posts
    3,270
    Rep Power
    0

    Default Re:Starting named at boot time

    [quote author=igodit link=board=8;threadid=2400;start=0#msg23017 date=1069428824]
    After following the instruction on Unix Wiz on 'Starting named at boot time' I notice that after creating the symbolic links:

    # cd /etc/rc.d
    # ln -s ../init.d/named rc2.d/S11named
    # ln -s ../init.d/named rc3.d/S11named

    I rebooted to test it, but I had to manually start the named,, again.

    After checking my files, I noticed that the color on the new files are different from those that were there. The new files are Black/Red while the existing files are Teal(Green).

    I'm using SuSE 9.0 and the BIND was setup from the tar.gx files.

    -- Also how can I know what services started up at boot time?
    [/quote]

    bind already comes with Suse 9.0 or Mandrake 9.x.
    More importantly Suse9.0 has bind 9. Bind 9 fixes a lot of bugs in the previous versions. Anyhoo, why'd you install from source instead of using the suse rpm for bind9 ?

    That said, you have the EASY way of setting up and running bind. You can use the DNS SERVER tool in yast and yast2 to tweak bind nicely and you can use yast or yast 2 runlevel editor to start named.... at boot.
    the runlevel editor for yast shows you what is started and what is not.

    other wise the SMART WAY
    is to get familiar with this command

    chkconfig

    but first I think you need to run ....
    man chkconfig

    I am not saying anymore on chkconfig.... just a clue...

    gillion

  3. #3
    igodit Guest

    Default Re:Starting named at boot time

    Thanks for the clue Gillion, I use the command

    chkconf to see the list of services and their status:

    I ran the command chkconfig -s named on

    mdadmd off
    microcode off
    named 235
    netstat off
    network on

    Why wouldn't its status be on?

  4. #4
    Join Date
    Sep 2002
    Posts
    3,270
    Rep Power
    0

    Default Re:Starting named at boot time

    Because on means that the service is on for all 5 working run levels.
    you have name 235 this means that named will only start for
    run levels 2, 3 & 5 on boot up.

    Note also that by default some services are NEVER allowed to startup at boot. For instance, runlevels 0,1 and 4.
    ::: FYI :::

    # runlevel 0 is System halt (Do not use this for initdefault!)
    # runlevel 1 is Single user mode
    # runlevel 2 is Local multiuser without remote network (e.g. NFS)
    # runlevel 3 is Full multiuser with network
    # runlevel 4 is Not used
    # runlevel 5 is Full multiuser with network and xdm
    # runlevel 6 is System reboot (Do not use this for initdefault!)







  5. #5
    Join Date
    Aug 2002
    Posts
    3,959
    Rep Power
    25

    Default Re:Starting named at boot time

    If you compile your software, you also have the option of adding the start command to the /etc/rc.local file.

    In your case you can add


    /path/to/named

    at the end of the file.

    The command will then be run everytime the machine starts.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •