> > If anyone wants a project, you could work on adapting the walklist
function
> > to support missing numbers and send me the code...
>
> Right now I don't see who to avoid the problem unless you impose some
> sort of maximum variable count. The walk_list condition is designed to
> stop via
>
> while
> eval ITEM="\$$BASENAME$x"
> [ "$ITEM" != "" ]
> do
>
> I grepped walk_list in /etc and found 10 instances in both ipfilter.conf
> and network.conf. Suppose you set a max list variable size to 20. I
> might loose a few pico seconds off my life but how long will that take
> lrp to boot for each call to walk_list configured with a max list
> variable this big? Wouldn't 20 more than cover all the lists that LRP
> uses?
I really dislike the idea of a limit on the number of potential items, but I
also really dislike the fact that a missing number causes walk_list to stop.
Both behaviors seems un-expected, and therefore increasing confusion.
I was intending something like:
for VAR in `set | sed -n "/^$BASENAME/{s/=.*//;p;}" | sort`
The older versions of LRP/LEAF didn't have a working sort command, so there
was no way to put the variables in the proper order before. Dachstein
includes the functional busybox sort command.
Charles Steinkuehler
http://lrp.steinkuehler.net
http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
