Autor: Bill Hacker Data: A: exim Assumpte: Re: [exim] caching of file contents in expansion testing mode
Matthias Waffenschmidt wrote:
> Hello,
>
> when debugging an expansion problem via -be I discovered the following
> problem (running version 4.52 on FreeBSD):
>
> If you're using a file lookup like
>
> ${if eq {${lookup{whatever}nwildlsearch{/some/file}}}{test}{yes}{no}}
>
> the file contents are cached and will not be reread if /some/file has
> been changed (-d always says 'cached open').
>
> Is this a feature or a bug? If it is a feature (I don't guess so) it
> should be documented in the docs.
>
Is '/some/file' a flat file, or a .db created from a flat-file?
And if the latter, was the derived db updated after changes to
the flat-file?
Not an 'academic' question - I am testing two similar checks against
'one of each type', same contents, for whitelisting, and the result
returned seems to be more sensitive to I/O variables than choice
of lookup methodolgy.
