[syslog-ng]internal logging problem

[Carlos Velasco]

Hi Bazsi,

>internal() messages are generated by syslog-ng itself. If you want kernel
>logs, you need to do it differently.

Yes, no INTERNAL messages are logged until I do a kill -HUP to syslog.ng=
 process, after that then I can see them:

>> kill -HUP 22765
>> 
>> Oct  2 12:01:49 src@atlas syslog-ng[22765]: new configuration=
 initialized

> kill 22765

>> Oct  2 12:02:18 src@atlas syslog-ng[22765]: syslog-ng version 1.5.18
>going down

I can grant you a root account in this machine if you want to pursue this=
 issue.

Regards,
Carlos Velasco

*********** REPLY SEPARATOR  ***********

On 02/10/2002 at 12:26 Balazs Scheidler wrote:

>On Wed, Oct 02, 2002 at 12:04:35PM +0200, Carlos Velasco wrote:
>> It works if I send a HUP signal to daemon AFTER launching:
>> 
>> kill -HUP 22765
>> 
>> Oct  2 12:01:49 src@atlas syslog-ng[22765]: new configuration=
 initialized
>> Oct  2 12:02:18 src@atlas syslog-ng[22765]: syslog-ng version 1.5.18
>going down
>
>internal() messages are generated by syslog-ng itself. If you want kernel
>logs, you need to do it differently.
>
>-- 
>Bazsi
>PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C
>8EB1
>
>_______________________________________________
>syslog-ng maillist  -  syslog-ng@lists.balabit.hu
>https://lists.balabit.hu/mailman/listinfo/syslog-ng
>Frequently asked questions at http://www.campin.net/syslog-ng/faq.html