WARNING: Scotty includes two SUID-root binaries that it uses to connect
to privileged ports on its host machine.  The programs are:

/usr/bin/ntping - lets Scotty ping other machines
/usr/bin/straps - lets Scotty receive SNMP traps from other devices

If SUID-root programs make you uncomfortable, you may remove these
binaries at the expense of these capabilties of Scotty.

If you want to use Scotty from another Tcl interpreter (such as wish),
you need to tell Tcl where to find it.  From the offical README file:

    Scotty and tkined installs as a dynamic loadable module. You have to
    make sure that the Tcl interpreter is able to find the modules on
    your system. There are two ways to achieve this goal:

    1. You can use the Tcl environment variable TCLLIBPATH by setting
       it to the installation directories of the scotty and the tkined
       extension. If you use a sh compatible shell, just type:

        TCLLIBPATH="/usr/local/lib/tnm2.1.7 /usr/local/lib/tkined1.4.7"
        export TCLLIBPATH

       Users of a csh compatible shell have to type:

        setenv TCLLIBPATH "/usr/local/lib/tnm2.1.7 /usr/local/lib/tkined1.4.7"

    2. You can edit the Tcl initialization file init.tcl usually found
       as /usr/local/lib/tcl7.5/init.tcl and append the scotty and tkined
       directories to the Tcl auto_path variable, e.g.

        if [file exists /usr/local/lib/tnm2.1.7] {
            lappend auto_path /usr/local/lib/tnm2.1.7
        }
        if [file exists /usr/local/lib/tkined1.4.7] {
            lappend auto_path /usr/local/lib/tkined1.4.7
        }

    The first solution is useful for testing and playing with the scotty
    extension. If you are going to use scotty regularly and if there
    are multiple users who will be using scotty, the second version
    might be easier to use and administrate.
