Martin,
here are examples that i have tested to work successfully.
Verify syslog.conf was prepared. The syslog.conf(5) wants to see tabs
not spaces, i marked the output manually to make that clear.
$ grep mail.info /etc/syslog.conf
mail.info\t\t\t/var/log/maillog
Check if syslog is usable using standard tool.
$ logger -p mail.info "from logger"
Check if l2 can use syslog locally.
$ echo "from l2, loc" | fsl-l2tool 'syslog(facility=mail, ident=info,
target="local")'
Check if l2 can use syslog remotly. Make sure syslogd accepts network
connections, see it's -s option for syslogd(8) on FreeBSD, -r option for
syslogd(8) on Linux or -t for syslogd(1M) on Solaris. Also note that the
l2spec requires a certain order of the remotehost, remoteport an target
keywords, see http://cvs.ossp.org/chngview?cn=3313.
$ echo "from l2, net" | fsl-l2tool 'syslog(facility=mail, ident=info,
remotehost="127.0.0.1", remoteport="514", target="remote")'
Now create a fsl config entry. This one is for openssh.
##
## fsl.openssh -- OSSP fsl configuration for openssh
##
ident (ssh(d|-.+)?|scp|sftp(-server)?)/.+ q{
prefix(
prefix="%b %d %H:%M:%S %N <%L> $1[%P]: "
)
-> {
debug: file(
path="/usr/opkg/var/openssh/sshd.log",
append=1, perm=0644
);
debug: syslog(
facility=mail, ident=info,
remotehost="127.0.0.1", remoteport="514", target="remote"
)
}
};
#Note: do not put HASH comments inside a l2spec
--
[EMAIL PROTECTED]
Development Team, Operations Northern Europe, Cable & Wireless
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
