Thomas, Thanks again for your assistance.
I am still looking to log to at least one file, whether through fsl writing to wherever it likes, fsl to my mail log, fsl to syslog or just from postfix to syslog. Since the last case (postfix to syslog) might be the most expeditious while other issues are considered and tested, how does one now builf postfix to not use fsl (ie. what exactly needs to be changed in the spec)? > >What do you suggest as the next step? > I'm afraid it's time to go a little bit deeper into fsl debugging. > There're some points to consider: Ok. > 1.) fsl is not linked into the program [snip] > This is not your problem as we know fsl is working with the OpenPKG > postfix package. Great, I think. > 2.) something is wrong with fsl configuration Everything I have is out-of-the-box for postfix (with switches given previously) and fsl. > That's very likely but hard to debug. [snip dangers of debugging build] Would it help if I add "with_fsl_debug yes" to postfix.spec and rebuild? > 3.) the l2 spec is wrong > Also verly likely. Unlikely, I think you mean, right? > Have a look at the tiny but precious "l2tool" that comes with the l2 > library as it allows you to play around with l2specs from the shell > command line. I'd be happy to if it would help, but I've no idea what I'd be trying to test. > 4.) bug in fsl > Unlikely :-) All software is broken*. All hardware will fail. The only variables are when and how you find out. *[I don't mean to start a thread on formal proofs of code. Anyway, you can't run sources.] -Andrew- -- _______________________________________________________________ | -Andrew J. Caines- [EMAIL PROTECTED] | | 703-886-2689 Unix Systems Engineer, WorldCom Web Hosting | ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
