On 8/21/2014 1:43 PM, PGNd wrote:
> Using some inelegant "echo X" debugging, I tracked down the point of the 
> segfault
> 
> Exec of any tc cmd, e.g.,
>       
>     ${TC} qdisc add dev $dev root handle 1: hfsc default $CLASS_DEFAULT
> 
>  causes a SEGFAULT if
> 
>     TC=run_tc
> 
> If I return it to its pre-SW-integration value
> 
>     TC=tc
> 
> it execs fine in /tcstart, with no obvious errors.
> 
> Not sure why, yet.  Reading what I can find re: run_tc usage ...

This is run_tc:

run_tc() {
    if ! $TC $@ ; then
        error_message "ERROR: Command \"$TC $@\" Failed"
        stop_firewall
        exit 2
    fi
}

So setting TC=run_tc causes runaway recursion. TC should point to the tc
executable, as is clearly documented in shorewall.conf(5)

-Tom
-- 
Tom Eastep        \ When I die, I want to go like my Grandfather who
Shoreline,         \ died peacefully in his sleep. Not screaming like
Washington, USA     \ all of the passengers in his car
http://shorewall.net \________________________________________________

Attachment: signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users

Reply via email to