Hi again,

This is what I did- Let Firestarter start under my runlevel 2 to start
on boot, but changed the code in /etc/if-up.d/Sxfirestarter to only
start if there is a runlevel available. Thus, it doesn't start here on
boot up, but it still starts when bringing the network up on a running
system. It also starts up again after system hibernation. On my laptop I
now get a red "Fail" at times during startup, but it may be the wireless
which is not ready yet? The lock file is then still there though, and
the gui shows when running "sudo firestarter status". On a virtual
machine, this solution seems to work without any sign of failure (to
me).

The changes:

/etc/network/if-down.d/S50firestarter:
<code>
#! /bin/sh

if [ -f /var/lock/firestarter ]
then
        /etc/init.d/firestarter stop
fi

exit 0

</code>

/etc/network/if-up.d/S50firestarter:
<code>
#! /bin/sh

if [ -f /var/lock/firestarter ]
then
        /etc/init.d/firestarter restart
else
# do not start here when system is booting - start at /etc/rc.x
        check_runlevel=`runlevel`
        if [ "$check_runlevel" != "N" ] && [ "$check_runlevel" != "unknown" ]
        then
                /etc/init.d/firestarter start
                echo "$check_runlevel"
        fi
fi

exit 0

</code>

/etc/rc2.d/S50firestarter:
<code>
#! /bin/sh

/etc/init.d/firestarter start

exit 0

</code>

-- 
[gutsy] /etc/network/if-up.d/50firestarter exited with return code 2
https://bugs.launchpad.net/bugs/132039
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to