[evlog-dev] Implementation questions
Benoit Guillon <[email protected]> Mon, 19 Apr 2004 16:00:55 +0200
| Newsgroups | gmane.linux.kernel.event-logging |
|---|---|
| Message-ID | <[email protected]> |
--------------E741907051A9818A5169C48E Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: Quoted-Printable Hello, I'm sorry to bother you again, but I have some questions about the evlog implementation (1.0.6-b2) and its scope: * Is it necessary to fork evlogd to manage kernel events? Why not using a thread, since it would make synchronization cleaner (a mutex is then enough)? Besides, on some implementations thread use is lighter than process fork. * For TCP backend, BACKENDS_DIR is set to "EVLOG_PLUGINGS_DIR" string. I think it should be set to the macro EVLOG_PLUGINS_DIR instead. * As far as I can understand, all the backends are called for each event. That is the available backends or their configuration (Disable=3Dyes in the config file) that selects the backends used. Is it possible to filter the backend(s) to use according to the event? For instance, it could be interesting to be able to "route" some kinds of events (e.g. facility=3DLOCAL4) to a centralized evlogd, and to let other events locally on the machines. It is not possible if the TCP backend is used for all the events. * Is it possible to use IBM Director combined to evlog ELA feature, or is IBM Director techno incompatible? Thansks for your answers, Bye, -- Beno=EEt Guillon [email protected] --------------E741907051A9818A5169C48E Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7Bit <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html> Hello, <p>I'm sorry to bother you again, but I have some questions about the evlog implementation (1.0.6-b2) and its scope: <p>* Is it necessary to fork evlogd to manage kernel events? Why not using a thread, since it would make synchronization cleaner (a mutex is then enough)? Besides, on some implementations thread use is lighter than process fork. <br>* For TCP backend, BACKENDS_DIR is set to "EVLOG_PLUGINGS_DIR" string. I think it should be set to the macro EVLOG_PLUGINS_DIR instead. <br>* As far as I can understand, all the backends are called for each event. That is the available backends or their configuration (Disable=yes in the config file) that selects the backends used. Is it possible to filter the backend(s) to use according to the event? For instance, it could be interesting to be able to "route" some kinds of events (e.g. facility=LOCAL4) to a centralized evlogd, and to let other events locally on the machines. It is not possible if the TCP backend is used for all the events. <br>* Is it possible to use IBM Director combined to evlog ELA feature, or is IBM Director techno incompatible? <p>Thansks for your answers, <p>Bye, <pre>-- Benoît Guillon [email protected] </pre> </html> --------------E741907051A9818A5169C48E-- ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click