Miscellaneous Irix Configuration Issues


Introduction

Things to make your system work better, but I couldn't figure out a better place to put...

chkconfig options

The global configuration of an SGI machine (an IRIS) running any release of IRIX is controlled by the chkconfig state. The current state of your host is determined by running the `chkconfig` command without any arguments. This is the output from an IRIS running Irix-5.2 and using SLIP or PPP as it's only network access (a so-called stand-alone host):
        Flag                 State               
        ====                 =====               

        autoconfig_ipaddress off
        automount            off
        desktop              on
        directoryserver      off
        fontserver           off
        gated                off
        glb                  off
        llb                  off
        lockd                on
        mediad               on
        mrouted              off
        named                off
        netls                on
        network              off
        nfs                  on
        noiconlogin          off
        objectserver         on
        rarpd                off
        rfindd               on
        routed               off
        rtnetd               off
        rwhod                off
        sar                  off
        snmpd                off
        soundscheme          off
        timed                off
        timeslave            off
        verbose              on
        visuallogin          on
        vswap                on
        windowsystem         on
        xdm                  on
        yp                   off
        ypmaster             off
        ypserv               off
Many of the options like yp are not even checked if network is off. Note that the network option has to do only with whether the physical networking interfaces (like ethernet) are configured, not with whether TCP/IP is enabled (it can't be turned off).

The chkconfig options can be changed by running the command (as root):

chkconfig option on|off
The chkconfig options are checked when the scripts in /etc/init.d/ are run, normally at system boot time. Unless you are very familiar with the boot process, it is best to just reboot after changing any of the options, to have them take effect.

Boot-time startup scripts

Sometimes you need to add something that needs to happen at system boot. This could be adding routes, or starting a dynamic dialed PPP at boot time, or setting up proxy ARP on a server. This is accomplished by adding a script to the /etc/init.d/ directory, where the startup (aka RC) scripts are placed. You would also place a symbolic link in the /etc/rc2.d/ directory for your script to be run at the correct sequence during startup. Because they are in seperate files, your custom startup scripts will not be stepped on by an upgrade to the OS.

Sample startup scripts can be found in context for dyanmically dialed Irix PPP, and dynamically dialed SLIP. Here is a sample startup script to setup Proxy ARP on a server at boot time:

#!/bin/sh
#
# starting up local networking stuff
#

IS_ON=/etc/chkconfig
CONF=/etc/config

if $IS_ON verbose ; then
        ECHO=echo
        VERBOSE=-v
else            # For a quiet startup and shutdown
        ECHO=:
        VERBOSE=
fi

case "$1" in
  'start')
      # setup proxy ARP for the dialin hosts
      # if this host has more than one interface,
      # you will need to hard-code the ethernet MAC address
      # instead of letting it be determined at run time.
      # note that 4DDN (among others) may change the MAC address from default!
      # and some AppleTalk packages change the output of `netstat -ian`!
      arp -s client1 `netstat -ian | grep :` pub
      arp -s client2 `netstat -ian | grep :` pub
      arp -s client3 `netstat -ian | grep :` pub
      ;;
  'stop')
      # be nice and delete the ARP entries
      arp -d client1
      arp -d client2
      arp -d client3
      ;;
  *)
        echo "usage: $0 {start|stop}"
        ;;
esac
exit 0
#
Assume the preceding file was named /etc/init.d/network.local, and you want it to start just after networking, then you would use the following commands to create the startup and shutdown links:
ln -s ../init.d/network.local /etc/rc2.d/S31netlocal
ln -s ../init.d/network.local /etc/rc0.d/K39netlocal

Where To Go From Here

Either use the Back key on your browser, or check out the top-level source page for Dialup (Remote) Access.
http://reality.sgi.com/employees/scotth/ Scott Henry <[email protected]>
Last modified: Thu Mar 21 21:48:36 1996