Thanks for the further ideas, Ken.

Firestarter certainly does not seem to be starting on bootup. Using ps as root gives no entries for Firestarter after booting, whereas it does once I get Firestarter to start.

The boot script  /etc/init.d/firestarter is:

#!/bin/sh
#
# Init file for the Firestarter firewall
#
# chkconfig: 2345 11 92
#
# description: Starts, stops, and lock the firewall
#
# Script Authors:
#       Tomas Junnonen <[EMAIL PROTECTED]>
#       Paul Drain <[EMAIL PROTECTED]>
#
# config: /etc/firestarter/configuration

FS_CONTROL="/etc/firestarter/firestarter.sh"

[ -x /usr/sbin/firestarter ] || exit 0
[ -x $FS_CONTROL ] || exit 0
[ -s /etc/firestarter/configuration ] || exit 0

RETVAL=0

start() {
        echo -n "Starting the Firestarter firewall: "
        $FS_CONTROL start > /dev/null
        RETVAL=$?
        if [ $RETVAL -eq 0 ]; then
                echo done.
        else
                echo "may have failed."
        fi
        return $RETVAL
}

stop() {
        echo -n "Stopping the Firestarter firewall:"
        $FS_CONTROL stop > /dev/null
        RETVAL=$?
        if [ $RETVAL -eq 0 ]; then
                echo done.
        else
                echo failed.
        fi
        return $RETVAL
}

And the result on bootup is

Starting the Firestarter firewall: may have failed

(Echo message altered to confirm where it is coming from)

Running  /etc/init.d/firestarter start as root

gives the result:

Starting the Firestarter firewall: done.

But in fact it is still not running.

The dektop applet configuration is:
[Desktop Entry]
Type=Application
Encoding=UTF-8
Name=Firestarter
GenericName=
Comment=
Icon=/usr/share/pixmaps/firestarter.xpm
Exec=gksu -g /usr/sbin/firestarter
Terminal=false
Categories=X-Debian-Apps-Net

Running /usr/sbin/firestarter as root does start Firestarter.

So it seems that the binary /usr/sbin/firestarter works but the scripts starting at /etc/firestarter/firestarter.sh do not.

Any more ideas/suggestions?

John Talbut


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to