>For debugging aid please have a look at the last paragraph of
>http://marc.theaimsgroup.com/?l=openpkg-dev&m=116608524305991
I had found the instructions in the fsl code, but had hoped
there might be an easier way...
>> On a related question - does the fsl library re-read
>configuration on the fly
>> - or it only on startup?
>>
>The fsl reads all fsl.* files from it's configuration
>directory on every
>openlog() call from the application. A common pitfall is to
>store defective,
>testing and copies of fsl.* files in the directory which
>confuses fsl because
>it reads them all and concatenates them into a huge string.
>This also leads to
>the problem of one defective file - independent of the
>application - affects
>all fsl applications.
Had worked this out too.
Ok - recompiled fsl with debugging enabled and then postfix
with the new fsl library.
By doing this I was able to see messages like the following in the
debugging output:
Mar 01 10:34:59 <debug> postfix/postsuper/mail[25262^25245] processcfg:
argident=ident, argmatch=(postfix/.+)/.+, argl2spec=
prefix(
prefix="%b %d %H:%M:%S %N <%L> postfix/postsuper[%P]: "
)
-> {
debug: file(
path="/secomon/openpkg-2.20061018/var/postfix/log/postfix.log",
perm=0644, monitor=3600
);
debug: syslog(
target='remote',
remotehost='secomondev.dnr.qld.gov.au'.
remoteport=4800,
ident='jay'
);
}
Mar 01 10:34:59 <error> postfix/postsuper/mail[25262^25245] processcfg:
logging failed to create stream from spec invalid use; line 11, column
18: `ote'<>,
'; failed to configure channel with
'target="'remote'"'(3)
Mar 01 10:34:59 <error> postfix/postsuper/mail[25262^25245] openlog:
processcfg() failed with an unrecoverable error (6)
Some additional testing I managed to break it down to:
fsl-l2tool 'syslog(target="remote")'
l2tool:ERROR: failed to parse specification (invalid use; line 1, column
23: `ote"<>)'; failed to configure channel with 'target="remote"')
It would appear to me that the configuration file parser is getting
itself out of sync. The 'target="remote"' has already been read, but it
thinks it is up to the "ote" part of the file.
My guess there is a bug in the config file reader (l2 I think it is
called)?
If anyone has any ideas that would be great, otherwise I will need to
rebuild all with debugging enabled and try that way. At least I make a
much simpler test case then using a whole postfix installation.
Jason
--
Jason Wilson <[EMAIL PROTECTED]>
ICT Security Services
Queensland Department of Natural Resources and Water, Australia
Ph: +61 7 389 63129
************************************************************************
The information in this e-mail together with any attachments is
intended only for the person or entity to which it is addressed
and may contain confidential and/or privileged material.
Any form of review, disclosure, modification, distribution
and/or publication of this e-mail message is prohibited.
If you have received this message in error, you are asked to
inform the sender as quickly as possible and delete this message
and any copies of this message from your computer and/or your
computer system network.
************************************************************************
______________________________________________________________________
OpenPKG http://openpkg.org
User Communication List openpkg-users@openpkg.org
