Robert Moskowitz:
>
> On 01/10/2013 04:01 PM, Wietse Venema wrote:
> > With the option to edit master.cf will come new opportunities
> > to destroy a configuration.
> >
> > Below is a first design for a "backup before edit" option. If no
> > command is configured, then no backup will be made. If
On 01/10/2013 04:01 PM, Wietse Venema wrote:
With the option to edit master.cf will come new opportunities
to destroy a configuration.
Below is a first design for a "backup before edit" option. If no
command is configured, then no backup will be made. If the backup
command fails, then the pos
On 1/10/2013 3:01 PM, Wietse Venema wrote:
> With the option to edit master.cf will come new opportunities
> to destroy a configuration.
>
> Below is a first design for a "backup before edit" option. If no
> command is configured, then no backup will be made. If the backup
> command fails, then
On Thu, Jan 10, 2013 at 07:23:36PM -0500, Wietse Venema wrote:
> The "backup before edit" feature does not work with revision control
> systems that error out when the current version is already checked
> in. For example, git and hg returns status 1 when a file has not
> changed since it was check
Viktor Dukhovni:
> > postconf_backup_command (default: empty)
> >
> > Optional external command that the postconf(1) command executes
> > before it attempts to modify the main.cf or master.cf file. The
> > macro "$file" is replaced by the absolute pathname of the file.
> >
> > Not
On Thu, Jan 10, 2013 at 04:01:13PM -0500, Wietse Venema wrote:
> With the option to edit master.cf will come new opportunities
> to destroy a configuration.
>
> Below is a first design for a "backup before edit" option. If no
> command is configured, then no backup will be made. If the backup
With the option to edit master.cf will come new opportunities
to destroy a configuration.
Below is a first design for a "backup before edit" option. If no
command is configured, then no backup will be made. If the backup
command fails, then the postconf command will not edit the file.
