I notice that this or similar logic is found in most of the BGP test harness
scripts:
if [ $START_PROGRAMS = "yes" ]
then
CXRL="$CALLXRL -r 10"
runit $QUIET $VERBOSE -c "$0 -s -c $*" <<EOF
../../libxipc/xorp_finder
../../fea/xorp_fea_dummy = $CXRL finder://fea/common/0.1/get_target_name
../../rib/xorp_rib = $CXRL finder://rib/common/0.1/get_target_name
../xorp_bgp = $CXRL finder://bgp/common/0.1/get_target_name
./test_peer -s peer1 = $CXRL finder://peer1/common/0.1/get_target_name
./coord = $CXRL finder://coord/common/0.1/get_target_name
EOF
trap '' 0
exit $?
fi
Even after tweaking for correct binary paths, the applications fail to properly
start unless I delete everything after the first token. For instance:
if [ $START_PROGRAMS = "yes" ]
then
CXRL="$CALLXRL -r 10"
runit $QUIET $VERBOSE -c "$0 -s -c $*" <<EOF
../../libxipc/xorp_finder
../../fea/xorp_fea_dummy
../../rib/xorp_rib
../xorp_bgp
./test_peer -s peer1
./coord
EOF
trap '' 0
exit $?
fi
Anyone know what that CXRL logic was supposed to accomplish? Maybe it only
works with xorp_rtrmgr is running?
Thanks,
Ben
--
Ben Greear <[email protected]>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
Xorp-hackers mailing list
[email protected]
http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
