On Wed, Apr 02, 2003, Martin Andrews wrote:
Dear Martin,
> Finally working with fsl again. fsl-l2tool helped some, but a logger
> type tool that actually read the fsl config would be great. [...]
>
I put this good idea on the wishlist.
> Still
> struggled with the fsl.postfix configuration. Syntax or other errors in
> the fsl.postfix file caused postfix to dump core. Ug. Finally found that
> this works: [...]
> Skipping the target="remote" would cause a core dump. Shouldn't that be
> the default (only allowed) value? More importantly, moving the
> target="remote" attribute also causes bus errors - any idea why: [...]
>
The two examples you posted were identical (i assume by accident) and
they do not work. Here is a working configuration:
##
## fsl.postfix -- OSSP fsl configuration for Postfix
##
ident (postfix/.+)/.+ q{
prefix(
prefix="%b %d %H:%M:%S %N <%L> $1[%P]: "
)
-> {
debug: syslog(
facility=mail,
ident=postfix,
remotehost="127.0.0.1",
remoteport="514",
target="remote"
)
}
};
As i explained in a previous posting, order of the parameters within the
syslog channel is important. This is a known issue (we) the OSSP l2 team
has to fix eventually. There is no default for the target option, it
must be set either "local" or "remote".
--
[EMAIL PROTECTED]
Development Team, Operations Northern Europe, Cable & Wireless
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]