Michael Grubb wrote:
I understand that this mechanism works as documented, meaning that it
iterates of each server in the list. I guess I was hoping for a little
more intelligence, in that it would only go onto other items if the
first one failed.
I wondered if this is what you were rea
Ed Brown wrote:
> But even in context main, it doesn't work in my tests just now to
> define a list variable for 'server' in an imported file, for a copy
> action in the importing file.
I think this is the standard "imports happen after everything else"
problem. More here:
http://praksys.blogspo
You make a good point about update.conf being self contained.
By moving the definition of cf_policy_hosts into update.conf that
seems to work now.
I understand that this mechanism works as documented, meaning that it
iterates of each server in the list. I guess I was hoping for a
little
Michael Grubb wrote:
Here are the relevant entries in update.conf:
import:
main.cf
#... snip ...
copy:
$(cf_master_inputs)
dest=$(cf_workdir)/inputs
server=$(cf_policy_hosts)
The relevant entry in main.cf:
control:
cf_policy_hosts = ( polserv1.domain:pol
Doh. I forgot to mention that, sorry all.
2.1.20
On Apr 6, 2006, at 6:21 PM, Ed Brown wrote:
I don't know when list iteration was extended to the server field,
but I can tell you it doesn't work in 2.1.11 and does work in
2.1.18. What version are you using?
-Ed
Michael Grubb wrote:
In
I don't know when list iteration was extended to the server field, but I
can tell you it doesn't work in 2.1.11 and does work in 2.1.18. What
version are you using?
-Ed
Michael Grubb wrote:
In the documentation for list iteration it says this:
__
In the documentation for list iteration it says this:
"Iterative expansion is currently restricted to:
* In the directory field of the admit/deny server access rules,
* In the `from' field of a copy action,
* In the server field of the copy action,
* In the directory field of the
