Re: [SLE] reloading SuSEfirewall2 config 'live'

20 Jan 2006

      -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The Friday 2006-01-20 at 18:03 -0500, Patrick Shanahan wrote:
...
* Carlos E. R.  [01-20-06 17:59]:
...
I think "SuSEfirewall2" with no parameters does a reload - no, my mistake, 
it does a "start". I'm unsure of the diference between both programs :-?
wahoo:~ # ls -la `locate SuSEfirewall2|grep bin`
-rwxr-----    1 root     root        79612 Oct 27  2003 /sbin/SuSEfirewall2*
lrwxrwxrwx    1 root     root           31 Dec  7  2003 /sbin/rcSuSEfirewall2 -> /etc/init.d/SuSEfirewall2_setup*
I see yours is bigger! They must have streamlined them:

- -rwxr-xr-x  1 root root 51042 Apr  4  2005 /sbin/SuSEfirewall2*
lrwxrwxrwx  1 root root 31 Oct  7 03:15 /sbin/rcSuSEfirewall2 -> /etc/init.d/SuSEfirewall2_setup*
- -rwxr-xr-x  1 root root 1696 Mar 19  2005 /etc/init.d/SuSEfirewall2_setup*

Yes, both of them are scripts, and with different syntax. Ah... I see the 
difference, SuSEfirewall2_setup calls "/sbin/SuSEfirewall2":

SUSEFWALL="/sbin/SuSEfirewall2"

    start)
        echo -n "Starting Firewall Initialization "
        echo -n '(phase 2 of 2) '
        rm -f "$BOOTLOCKFILE"
        $SUSEFWALL -q start
        rc_status -v
        ;;

    restart|force-reload)
        $0 start
        rc_status -v
        ;;

So, a reload does the same as a start; and start calls 
"/sbin/SuSEfirewall2 -q start".

Conclusion: to reload the firewall, the shortest command is 
"SuSEfirewall2" alone :-)

- -- 
Cheers,
       Carlos Robinson

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Made with pgp4pine 1.76

iD8DBQFD0XYCtTMYHG2NR9URAu/iAKCMc+YZb8yzkZqveK9as/5ZPuSbIgCbBqGX
4Natx/EJRfPn7Qo8EugqRyI=
=BWh8
-----END PGP SIGNATURE-----