Robert Collins wrote:
> I'll create a parser type for that then. IMO the existing acl file
> inclusion method is quite useful - because the contents of the file
> don't need the acl foo bar prefix for each line. This makes script
> generated files easier. So I'd like to keep that method around. If
> someone wants to suggest a more intuitive syntax for triggering it (ie
> acl foo bar source = /path/to/file) or whatever, that's ok by me too,
> and I'll endeavour to implement that.
It is useful indeed, but the current config file syntax sucks and should
be changed to make it more obvious it is a file based acl definition.
Possibly with a syntax somewhere along the lines you proposed above, and
most likely extended to dynamically reload the ACL on changes (maybe as
an option).
-- HenrikReceived on Sat May 12 2001 - 16:34:43 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:14:01 MST