[evlog-dev] syslog --> evlog patch upstream
Bryan Sutula <[email protected]> Fri, 28 Jan 2005 10:27:19 -0700
| Newsgroups | gmane.linux.kernel.event-logging |
|---|---|
| Message-ID | <1106933239.3538.21.camel@localhost> |
Continuing in new thread...was: Re: [evlog-dev] where is patch for kernel-2.4.21-20 On Thu, 2005-01-13 at 16:07 -0800, Hien Nguyen wrote: > We looked at modifying syslogd and also > glibc in the early day of evlog, and decided to go preload route (since > it is the least instrusive). > > ...if it is accepted by the syslogd folks then your > patch is the way to go. Would you like to submit your patch to the > syslogd folks? I'd like to submit this patch to syslog upstream. However, though functional, it's really not in a good form for them to take right now. The patch is #ifdef'd, so can be enabled at compile time. Since syslog ships everywhere and evlog isn't necessarily installed/available everywhere, syslog would have to leave the #define off by default. Most users still wouldn't be able to use the functionality. So at this point, getting the patch into syslog upstream means that a user would still have to get source and recompile syslog to use the syslog --> evlog mechanism I worked on. Given all of the above, it will be hard to make a good case to the syslog maintainers to include it. I think it needs more work. It seems to me that when syslog reads it's conf file, if it sees "%evlog" as a destination, it could do some shared library magic to see if evlog is available. If so, it can be loaded and used. If not, syslog could generate an error saying that the requested configuration cannot be achieved. I have no experience with this sort of "shared library magic". If anyone here knows how to do this, that'd be great. I'd love to improve this patch to the point where it has a chance to be accepted by the syslog folks. I could work with someone, someone could just modify this, or perhaps someone could point me to an example of this being done elsewhere (it'd have to be open source for me to look at it). Anyway, I apologize for the delay in answering. I would like to submit this upstream, but think it needs some more work. Anyone want to help? -- Bryan Sutula <[email protected]> ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl