Ok setting the env var works for me. Just another minor thing:
Since when running configure, I specified target=mips64-montavista-linux When installing, the install script copies all the binaries with prefix "mips64-montavista-linux", like mips64-montavista-linux-xorp_rtrmgr However, when starting mips64-montavista-linux-xorp_rtrmgr, it will start "xorp_fea". On Thu, Sep 4, 2008 at 12:16 PM, Pavlin Radoslavov <[EMAIL PROTECTED] > wrote: > RTP Techie <[EMAIL PROTECTED]> wrote: > > > I will try to set the env var let you folks know if it works for me > > > > So, since I'm new to the code base, is there any more of these env var > get > > documented somewhere? > > XORP_PROMPT_OPERATIONAL and XORP_PROMPT_CONFIGURATION to overwrite the > default xorpsh prompt in operational and configuration mode > respectively (see Section 1.7.1 in the User Manual). > > Other (undocumented) interesting variables are: > XORP_FINDER_SERVER_ADDRESS > XORP_FINDER_SERVER_PORT > XORP_FINDER_CLIENT_ADDRESS > XRLTRACE > > The first three are useful if you want to run XORP as a distributed > router (i.e., different components on different machines). > XRLTRACE is useful if you want to debug the XRL IPC exchange. > > Pavlin >
_______________________________________________ Xorp-hackers mailing list [email protected] http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
