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. ------------------------------------------------------------ __ * * 新日本気象海洋株式会社 ＼ / * * * 環境情報本部 || * 情報システムグループ || * 西山 英之 --------------i hideyuki@yk.metocean.co.jp ‾ ‾ ‾ ‾‾ ‾ ‾‾ ‾ ‾ ‾‾ ‾‾ ‾‾ ‾ ‾‾‾