Victor Faion <[email protected]> wrote:
> OK, I understood it correctly then. If a process relies on another
> process for all of its configuration and has no state itself, could
> you have an empty template file? Maybe something like this:
>
> protocols {
> empty-protocol {
> %help: short "No configurable options";
> }
> }
Yes, but in practice the "empty" template file is slightly more
complex, because it needs to include info how the rtrmgr will start
"empty-protocol", etc (assuming the startup/shutdown is managed by
the rtrmgr).
See etc/templates/rib.tp for such "almost empty" template file (you
need ignore the "policy {} section there).
Pavlin
> Victor
>
>
> On Tue, Jan 27, 2009 at 20:31, Pavlin Radoslavov
> <[email protected]> wrote:
> >> Thank you, this has made it work. I think I misunderstood the point of
> >> the template files, I thought all the functions in the protocol had to
> >> be described in the template, but it's just the ones that are used for
> >> configuration when you start rtrmgr (I think).
> >
> > The template files are the glue between user config and the
> > particular XRLs used to change the config. state in the protocol.
> > Hence only the XRLs used to (re)configure the protocol need to be
> > exposed in the *.tp file.
> >
> > Regards,
> > Pavlin
> >
>
> _______________________________________________
> Xorp-hackers mailing list
> [email protected]
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
_______________________________________________
Xorp-hackers mailing list
[email protected]
http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
