[syslog-ng] Is logger an effective test tool on Solaris 10?

Chuck chuck.carson at gmail.com
Wed Jul 21 19:36:51 CEST 2010


I am using the following script to test syslog-ng. (Running this from the
same machine as the syslog-ng server):

#!/bin/bash

d=`date '+%y%m%d_%H%M%S'`
logger -p kern.debug    "__kern.debug__ $d"
sleep 1;


d=`date '+%y%m%d_%H%M%S'`
logger -p kern.crit     "__kern.crit__ $d"
sleep 1;

d=`date '+%y%m%d_%H%M%S'`
logger -p kern.info     "__kern.info__ $d"
sleep 1;

However, here is how the messages are being seen within syslog-ng:
Jul 21 10:30:35 log01 cars: [ID 702911 user.debug] __kern.debug__
100721_103035
Jul 21 10:30:36 log01 cars: [ID 702911 user.crit] __kern.crit__
100721_103036
Jul 21 10:30:37 log01 cars: [ID 702911 user.info] __kern.info__
100721_103037

The facility is being seen as user and not kern...

Anyone have any ideas?
Thx,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20100721/2443d8bc/attachment.htm 


More information about the syslog-ng mailing list