different makefiles for the main project and ommysql)
- applied fixes from Michael Biebl:
1.) fix failing compilation of ommysql plugin
(s/ommysql-config.h/config.h/)
2.) fix mysql configure check (although the default is no, we did check for
the mysql devel files)
3.) Create a separate Makefile.am for the doc files. This cleans up the
toplevel Makefile.am considerably and makes it much more readable and
maintainable.
3b) Assign the html doc files to html_DATA. This means, they are installed
to $(hmtdir), which by autoconf standards is
$(prefix)/share/doc/$packagename/.
4.) Reformat the SOURCES line to make it better readable and maintainable.
This was done to work around a problem with malloc/free. Note that we
are still running on two threads - the startup thread just waits for
the new one to finish. For a description of the problem I try to
work-around, please see:
http://rgerhards.blogspot.com/2007/10/could-i-really-reproduce-bug.html
Note that this is an experimental change, which will only stay if it
proves to fix the segfault issue we are dealing with.
rsyslog package. I need to re-think it in the future, but for the time
being the current mode is best. I now simply include one additional
tarball for ommysql inside the main distribution. I look forward to
user feedback on how this should be done best. In the long term, a
separate project should be spawend for ommysql, but I'd like to do that
only after the plugin interface is fully stable (what it is not yet).
call to logerror() that many of the modules do. I have not tried it,
but I think things will become wild when we compile without pthread
support. Threading prevents full recursion, so we have not seen any bad
effects so far. However, the problems that I experienced in ommysl
(that caused me to re-structure startWorker()) are actually rooted in
this issue. I first thought to fix it via a module interace, but I now
came to the conclusion that it is not more effort and much cleaner to
do an internal error buffering class. This is implemented in
errbuf.c/h.
- I just noticed that this is not actually an error buf, but the core of an
input module for all internal messages. As such, I implement it now as
iminternal.c/h. Of course, there is no input module interface yet
designed, but that doesn't matter. Worst-case, I need to re-write the
im, best case I can use the im (at least partly) to define the
interface.
- added a few functions to the linkedlist class
- error messages during startup are now buffered - so we do no longer need
to think about how emergency logging might work. Actually, these are
logged to whatever is instatiated in the log file. This enhances the
chance that we will be able to drop the error message somewhere it is
seen.
