Hey Group; No one answered this question so I figured out the problem. It is proof SuSE never tried it before shipping SuSE 9.2. Maybe they are just becoming Splash at boot only folks. There are 3 file involved. All are in /etc/init.d 1. SuSEfirewall2_init 2. SuSEfirewall2_setup 3. SuSEfirewall2_final All come with ______________________________________________ SUSEFWALL="/sbin/SuSEfirewall2" test -x $SUSEFWALL || exit 5 test -r /etc/sysconfig/SuSEfirewall2 || exit 6 . /etc/rc.status rc_reset case "$1" in start) echo -n "Starting Firewall Initialization " echo -n '(phase 3 of 3) ' $SUSEFWALL status rc_status -v _________________________________________________ Of course the "phase" number differs in each file. Problem is seen at boot time (Try "F2" at bootup and see what you find - some very interesting thing showup during boot). SuSE didn't verify that "/sbin/SuSEfirewall2" doesn't mind starting multiple times. Problem is it does mind. It will even tell you it does - hence the error at boot time. To fix the problem simply comment out "$SUSEFWALL start" by replacingq it with "# $SUSEFWALL start" in two files. 2. SuSEfirewall2_setup 3. SuSEfirewall2_final Take a look at "/sbin/SuSEfirewall2 --help" -- 73 de Donn Washburn __" http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB / / __ __ __ __ __ __ __ 307 Savoy St. / /__ / / / \/ / / /_/ / \ \/ / Sugar Land, TX 77478 /_____/ /_/ /_/\__/ /_____/ /_/\_\ LL# 1.281.242.3256 Dump Microsoft Software - Stop virus email Email: n5xwb@hal-pc.org " http://counter.li.org " #279316