Hello,
On Thu, Nov 24, 2005 at 06:55:04AM +0800, Bill Hacker wrote:
> >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?
It was a flat file, but as Phil mentioned this behaviour is common to
all kind of lookups.
--
Gruss / Best regards | LF.net GmbH | fon +49 711 90074-411
Matthias Waffenschmidt | Ruppmannstr. 27 | fax +49 711 90074-33
mw@??? | D-70565 Stuttgart | http://www.lf.net
