tony mancill wrote: > What if we did this? > > /etc/rc.config.d/sendmail.default > /etc/rc.config.d/sendmail > (or /etc/rc.config.d/sendmail.override) > . > . > . > > And so on. Always source sendmail.default first, so that we know we have > sane values. If "sendmail" is there, source it too.
That's the same as my idea (toward the bottom of my mail) of setting the variables to defaults at the top of the init script, then sourcing the defaults file to overwrite them. Except it introduces a third file for no benefit I can tell. (I can see a benefit if 2 scripts both needed to look at defaults for the same values, but this is rare, and such scripts could happily source a defaults file from /usr/share/lib/something, without it being specified in policy or cluttering up /etc with immutable files. > This way, users can > take a peek at the .default file to see what should in their file But there's no need since the non-.default file can include all possible entires, commented out or not. -- see shy jo