Re: questions on debugger_command
- On 12/23/2012 12:35 PM, Robert Moskowitz wrote:
>Don't submit it to the CentOS list. CentOS is a direct copy, as much as
> On 12/23/2012 12:12 PM, Wietse Venema wrote:
>> Robert Moskowitz:
>>> postconf debugger_command
>>> postconf: warning: debugger_command: unknown parameter
>>> This is postfix 2.6.6 on Centos 6
>>> Fixed in Postfix 2.9.
>>> Robert Moskowitz:
>>> ARGH!!! :)
>>> I will submit this to the Centos list and see what they do with it.
>>> Thanks Wietse.
>>> BTW, is this only a problem with reporting debugger_command or is
>>> debugger_command broken until 2.9?
>> This is a limitation of old postconf implementations, and it is
>> unlikely that it will be patched (it may be sufficient to add an
>> entry to postconf/install_table.h and postconf/install_vars.h).
>> The Postfix 2.9 implementation is a complete rewrite that reports
>> debugger_command and more importantly, warns about unused parameters
>> in main.cf or master.cf (typically typos).
>> Postfix 2.10 brings incremental improvements: postconf reports the
>> expansion of $name in parameter values, reports parameters that
>> can't be set in main.cf (process_name, process_id), warns about
>> attempts to set such read-only parameters, and warns about an unknown
>> $name in parameter values (typically typos).
>> All this will help with Postfix troubleshooting and support. Folks
>> that run four-year old code will have something to look forward to.
> Right now I am trying to stay with what Centos 6.3 is shipping with.
> Perhaps that is risky, but this is a low usage server with a few
> domains and a couple handful of users.
> My current server is built on F12 with a custom built postfix to add
> the quota patch. I just checked and that is running 2.6.5; thus I
> have instructions on how to build postfix from source. This is part of
> why I want 'stock' rpms and a stable OS base. Right now I need to
> rebuild on a new OS platform, either F18 which will ship shortly or
> Centos 6.3.
> I really appreciate all you have done here.
possible of Redhat. You would need to report this to Redhat and get them
to do the updates before it would make it out to CentOS. You may however
find a repo with a newer version available.
877-777-1407 ext 502
Comprehensive Online Solutions