summaryrefslogtreecommitdiffstats
path: root/linkedlist.h
Commit message (Collapse)AuthorAgeFilesLines
* changed license to GPLv3 (for what is to become rsyslog v3)Rainer Gerhards2007-12-141-7/+8
|
* - added an identifier to command handler table - need to identify whichRainer Gerhards2007-11-211-0/+1
| | | | | | | | | | command handler entries need to be removed when module is unloaded - added support so that linkedlist key can be used for owner handle - enhanced llExecFunc to support deletion of list elements (on behalf of user function being called, slight interface change) - enhanced linkedlist class so that list elements can now be deleted based on the key value they have - created entry point so that CfSysLine handlers are removed on modExit()
* cleaned up compiler warningsRainer Gerhards2007-09-111-1/+1
|
* - I found out that we finally have problems with the (somewhat recursive)Rainer Gerhards2007-08-031-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* enhanced linkedList class, new method to get count, new method to execute aRainer Gerhards2007-08-021-0/+7
| | | | user-supplied function on all members
* shuffeled code in cfline() to prepare for a better system of processing theRainer Gerhards2007-08-011-1/+1
| | | | selector_t linked list
* - got the basic code in place to create an in-memory list of cfsyslineRainer Gerhards2007-07-311-1/+2
| | | | handlers (omfile.c used as testing case) -- not yet in active code
* - added interface to register a cfsysline command handler (basicRainer Gerhards2007-07-311-0/+1
| | | | functionality)
* prepared cfsysline.c for integration into output modulesRainer Gerhards2007-07-311-2/+3
|
* added some more functions to linkedList classRainer Gerhards2007-07-311-3/+5
|
* added a generic linked list object (files linkedlist.h/c)Rainer Gerhards2007-07-311-0/+57