Event logging and native support

Ian Springer ian.springer at redhat.com
Thu Jan 26 03:38:02 UTC 2012


It's because the logfile "tailing" code uses SIGAR to check inode id's 
(see LogFileEventPoller class). However, after a quick look at the code, 
it may be possible to rework this code to only use standard JDK classes 
when SIGAR is not available and still be almost as robust.

On 01/25/2012 09:27 PM, Larry O'Leary wrote:
> I have not looked through the code so please forgive me if this is an
> easy one. Currently, it would appear that if native support is disabled
> in the agent, event logging does not occur. Is this expected? Why is
> native support required for parsing event logs?
>
> This appears to be related to
> https://bugzilla.redhat.com/show_bug.cgi?id=773435 however in my use
> case native support is actually being disabled by using the --nonative
> command-line option when starting the agent. As long as this option is
> not used, event logging appears to be working as normal but if I start
> the agent with --nonative, even logging no longer occurs and new events
> do not show up in the Events>>  History page.


-- 
Ian Springer
Principal Software Developer
JBoss Operations Network
Red Hat
ian.springer at redhat.com



More information about the rhq-devel mailing list