On Thu, Mar 13, 2003, mandrews wrote: > I am trying to make fsl forward messages to syslog and having no luck. > I am working with the postfix package. I editied fsl.postfix [...] > Re Martin, i like to know if you finally succeeded with the feedback you received so far. The fsl itself is a tiny library which gets it's power from the unterlying "l2" logging library and "cfg" configuration parser library. The most trouble i've seen with current releases of fsl (as they come with OpenPKG) is admins fighting with syntactical problems.
I've seen one problem in your reports where you used shell style "hash" comments inside a l2spec which is not allowed. Also note that "fsl concatenates all fsl.* files and needs semicolon as separator" which means that a faulty fsl config file might break others (see http://cvs.openpkg.org/chngview?cn=5365 as an example how we were caught by our own pitfall). The grammar of a OSSP l2 channel tree specification is documented in fsl(3) along with a bunch of examples. I also want to point out that the OSSP l2 library comes with a nifty command line "l2tool" which allows a user to quickly try a l2spec. This is half the way towards fsl. Unfortunately the "l2tool" is not installed along OpenPKG fsl so you either have to hack the fsl.spec (item for my personal TODO list) or install the OpenPKG l2 package just to get the tool (shouldn't be hard work). Quick and dirty example: $ echo "foo" | /cw/bin/l2tool \ 'debug: prefix ( prefix="[%b %d %H:%M:%S] <%L> [%P]" ) -> fd(fd=1)' [Mar 10 23:55:25] <info> [47105]foo Please contact me if you need further assistance. -- [EMAIL PROTECTED] Development Team, Operations Northern Europe, Cable & Wireless ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
