(Dave Wolfe writes:)
> [ Chan Wilson writes: ]
> > > And what happens to any comments I might insert? Eaten by the
> > > "de-commenter", no doubt. The easiest thing to do is to supply a
> > Well, unless you put them in the "comments" variable, yea. I don't
> > think it's ever been intended for the config file to be a general
> > free-form file thing.
> That's news. But the point is, many times I'll insert a comment with a
> variable to note why it's set the way it is, that it should be changed
> after a particular event, etc. This acts as a reminder to list owners
> (including me) so that they don't forget and make silly mistakes in the
> configuration files. Putting the note in the comment variable is usually
> too far removed to do any good.
How about something somewhere in the middle where you do the equivalent
of 'make config' to take the possibly-commented version and write out
a de-commented one for performance purposes?
I'm maybe a little concerned about the suggestions to do anything with dbm or
other like things due to portability unless we can safely assume that the
sendmail (or equivalent) has one of a small set of such dbm variants
----------- Vince Skahan ------ firstname.lastname@example.org -----------
Disks have a steady state and that state is full....
- Ken Thompson