[Xorp-hackers] XRL Timing

[Pavlin Radoslavov]

Victor Faion <vfaion at gmail.com> wrote:

> On Tue, Feb 10, 2009 at 17:45, Pavlin Radoslavov
> <pavlin at icsi.berkeley.edu> wrote:
> > Victor Faion <vfaion at gmail.com> wrote:
> >
> >> Hello,
> >>
> >> In my XORP process I have a few parameters that are set in config.boot
> >> and these send XRLs to set some fields in my process. These seem to be
> >> getting sent when the eventloop's run function is called and I was
> >> wondering if/how it's possible to send these XRLs before this?
> >
> > You can't. Sending an XRL is an event and all events are handled by
> > the eventloop (when its run() function is executed).
> >
> > Regards,
> > Pavlin
> >
> >> Victor
> >>
> >> _______________________________________________
> >> Xorp-hackers mailing list
> >> Xorp-hackers at icir.org
> >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
> >
> 
> 
> Is there a way to set the order in which the XRLs called from
> config.boot are called? I just want to insure some of the state is set
> before performing further functions. So for example I can have the
> callback of the last XRL call these functions, but is there a way to
> guarantee which XRL will return last?

Try to reorder the corresponding blocks in the *.tp template file.
Also, try to use %create, %update, %activate as appropriate (see the
rtrmgr design document for description).

Pavlin