[Pkg-exim4-users] question about update-exim4.conf manpage

Ross Boylan ross at biostat.ucsf.edu
Tue Jun 27 20:48:22 UTC 2006


On Mon, 2006-06-26 at 14:26 +0200, Marc Haber wrote:
> On Tue, May 23, 2006 at 05:51:37PM +0200, Marc Haber wrote:
> > On Mon, May 22, 2006 at 09:47:56AM -0700, Ross Boylan wrote:
> > > update-exim4.conf checks the validity of the freshly generated
> > > configuration file if and only if invoked without the -o option.  If the
> > > new file is invalid, update-exim4.conf exits with an error and leaves
> > > the old /var/lib/exim4/config.autogenerated untouched.
> 
> I have committed the following new wording:
> 
>        If the new configuration will be written to
>        /var/lib/exim4/config.autogenerated, update-exim4.conf will
>        check the validity of the freshly generated configuration.  If
>        the new file is detected as invalid, update-exim4.conf leaves
>        the old /var/lib/exim4/config.autogenerated untouched and exits
>        with an error.
> 
>        However, there are still possible invalidities that can only be
>        detected at run time. This most notably applies to errors in
>        expressions that are expanded at run time.
> 
>        If the new configuration will be written to some other file,
>        this file's contents will always be overwritten regardless of
>        the validity of the freshly generated configuration.
> 
> 
> > > It might be nice to check the validity of the output file in all cases
> > > (which was the behavior I assumed), but that's a somewhat separate
> > > issue.
> 
> I disagree on that point. The current behavior is just fine in my
> opinion.
It might be good to make this behavior a bit more explicit.  Here's a
possible rewording of the last paragraph:
       If the new configuration will be written to some other file,
       no validity checking occurs  and that file will always be
       overwritten.
Ross




More information about the Pkg-exim4-users mailing list