Re^2: [syslog-ng] ipfw logging

Hideyuki Nishiyama hideyuki@yk.metocean.co.jp
Fri, 02 Jun 2000 08:30:45 +0900


 Thanks Balazs Scheidler.

Balazs> FreeBSD uses a special character device named /dev/klog for kernel logging.
Balazs> It _should_ work with
Balazs> 
Balazs> file s_kern { file("/dev/klog"); };
Balazs> 
Balazs> If it doesn't, then tell me how to generate some kernel messages under
Balazs> FreeBSD. I have it installed, but since I'm not that much experienced in
Balazs> it, I can't test whether kernel messages arrive or not.

 I can contribute a little, but at once, I report corectly 
console messagewhen syslog-ng run on FreeBSD. 

 I tested on FreeBSD 4.0-RELEASE, and on 2.2.8-RELEASE. Then 
I used syslog-ng-1.4.3 and libol-0.2.6.

my syslog-ng.conf:

options { long_hostname(off); sync(0);};
source src { file("/dev/klog"); internnal();};
destination messages { file("/var/log/messages"); };
log { source(src); destination(messages);};


 On FreeBSD 4.0-RELEACE, the same on 2.2.8-RELEACE, console messages is

Error opening file /dev/klog for reading (Device busy)
Error initializing configuration, existing.

 Then syslog-ng has finished.

------------------------------------------------------------
    __   *   *                        $B?7F|K\5$>]3$MN3t<02q<R(J
$B!@(J /   *      *    *                  $B4D6->pJsK\It(J
 ||        *                          $B>pJs%7%9%F%`%0%k!<%W(J
 ||               *                $B!!(J $B@>;3(J $B1QG7(J
--------------i   $B!!!!!!!!!!!!!!!!!!(Jhideyuki@yk.metocean.co.jp
 ~  ~ ~  ~~  ~  ~~  ~          
~  ~~  ~~  ~~ ~ ~~~