summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'v7-stable'Rainer Gerhards2013-11-163-4/+8
|\ | | | | | | | | Conflicts: plugins/imuxsock/imuxsock.c
| * bugfix: imuxsock: UseSysTimeStamp config parameter did not work correctlyRainer Gerhards2013-11-152-3/+6
| | | | | | | | | | Thanks to Tomas Heinrich for alerting us and provinding a solution suggestion.
| * doc typo fixRainer Gerhards2013-11-151-1/+1
| |
| * doc: fix glitch in v6+ parameter descriptionRainer Gerhards2013-11-151-1/+2
| |
* | Merge branch 'v7-devel'Rainer Gerhards2013-11-152-1/+11
|\ \
| * | Merge branch 'v7-stable' into v7-develRainer Gerhards2013-11-152-1/+11
| |\| | | | | | | | | | | | | Conflicts: ChangeLog
| | * doc: add Tomas' patch to ChangeLogRainer Gerhards2013-11-151-0/+3
| | |
| | * imuxsock: pass along missing legacy config variablesTomas Heinrich2013-11-151-1/+5
| | | | | | | | | | | | | | | | | | | | | Not doing so caused that the system log socket was unaffected by these directives. bCreatePath is still not passed but currently, there's no placeholder for it.
* | | prepare for 8.1.0 releasev8.1.0Rainer Gerhards2013-11-151-1/+1
| | |
* | | fix: ruleset queues were activated too earlyRainer Gerhards2013-11-145-4/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | This does not cause issues in v7, but here we have the problem that the total number of actions, which now is required for wti sizing, is not available at that early stage. So we needed to delay queue startup until everything is processed (just as it should have been already!). Note the previously we could have a segfault on first message when ruleset queues were used.
* | | testbench: add new test vor v6+ formatRainer Gerhards2013-11-143-0/+68
| | |
* | | regression fix: misadressing if worker thread was restartedRainer Gerhards2013-11-141-0/+1
| | |
* | | regression fix: failure if more than one template was to processRainer Gerhards2013-11-132-1/+8
| | |
* | | doc: note that v8 output module interface is not yet stableRainer Gerhards2013-11-131-0/+4
| | |
* | | document yet-untested modulesRainer Gerhards2013-11-131-1/+19
| | |
* | | documented modules not yet supported in v8Rainer Gerhards2013-11-131-0/+18
| | |
* | | doc: remove copy&paste leftoverRainer Gerhards2013-11-131-2/+0
| | |
* | | bump version numberRainer Gerhards2013-11-133-2/+16
| | |
* | | Merge branch 'master-ruleeng' into master-ruleeng-simdRainer Gerhards2013-11-1324-456/+750
|\ \ \
| * | | mmpstrucdata: support for v8 omod interfaceRainer Gerhards2013-11-131-1/+14
| | | |
| * | | mmfields: support v8 omod interfaceRainer Gerhards2013-11-131-1/+14
| | | |
| * | | ommongodb: minimal support for v8 omod interfaceRainer Gerhards2013-11-131-3/+22
| | | | | | | | | | | | | | | | single instance, untested
| * | | ompgsql: very minimal support for v8 omod interfaceRainer Gerhards2013-11-131-7/+28
| | | | | | | | | | | | | | | | | | | | TX DISABLED, single instance, untested - but at least it builds so that users can test...
| * | | omlibdbi: very minimal support for v8 omod interfaceRainer Gerhards2013-11-131-5/+24
| | | | | | | | | | | | | | | | | | | | TX DISABLED, single instance, untested - but at least it builds so that users can test...
| * | | omuxsock: minimal support for v8 omod interfaceRainer Gerhards2013-11-131-7/+22
| | | | | | | | | | | | | | | | single instance only, untested
| * | | omudpspoof: support v8 omod interfaceRainer Gerhards2013-11-131-57/+73
| | | | | | | | | | | | | | | | so far untested
| * | | omrelp: support v8 omod interfaceRainer Gerhards2013-11-131-54/+81
| | | |
| * | | mmsequence: support v8 omod interfaceRainer Gerhards2013-11-131-5/+29
| | | | | | | | | | | | | | | | | | | | Note that this is done so that we have it, but it so far is *untested* (build test, only).
| * | | omfwd: fully support v8 omod interfaceRainer Gerhards2013-11-131-153/+161
| | | | | | | | | | | | | | | | we now also create multiple connections, one for each instance
| * | | omprog: support v8 omod interfaceRainer Gerhards2013-11-121-14/+34
| | | |
| * | | ommail: small cleanupRainer Gerhards2013-11-121-6/+3
| | | |
| * | | ommail: support v8 omod interfaceRainer Gerhards2013-11-121-83/+99
| | | |
| * | | mmjsonparse: support v8 omod interfaceRainer Gerhards2013-11-111-15/+30
| | | |
| * | | mmutf8fix: support v8 omod interfaceRainer Gerhards2013-11-111-3/+18
| | | |
| * | | omsnmp: support omod v8 interfaceRainer Gerhards2013-11-111-33/+48
| | | |
| * | | mmanon: adjust to recent omod interface changesRainer Gerhards2013-11-101-2/+1
| | | |
| * | | mmnormalize: convert to v8 omod interfaceRainer Gerhards2013-11-091-3/+18
| | | |
| * | | Merge branch 'master' into master-ruleengRainer Gerhards2013-11-083-4/+5
| |\| |
| | * | doc: maintain ChangeLogRainer Gerhards2013-11-081-0/+2
| | | |
| | * | bugfix: regression in template processingPavel Levshin2013-11-081-1/+1
| | | |
| | * | Merge branch 'v7-stable'Rainer Gerhards2013-11-080-0/+0
| | |\|
| | | * omhiredis: fix memory leakPavel Levshin2013-11-081-3/+2
| | | |
| | * | omhiredis: fix memory leakPavel Levshin2013-11-081-3/+2
| | | |
| * | | Merge branch 'master' into master-ruleengRainer Gerhards2013-11-075-1/+27
| |\| |
| | * | emit warning message if output module with msg passing mode runs asynchronouslyRainer Gerhards2013-11-075-1/+27
| | | |
* | | | Merge branch 'master-ruleeng' into master-ruleeng-simdRainer Gerhards2013-11-079-27/+43
|\| | |
| * | | Merge branch 'master' into master-ruleengRainer Gerhards2013-11-079-27/+43
| |\| | | | | | | | | | | | | | | | | | | | | | Conflicts: runtime/wti.c runtime/wti.h
| | * | doc: maintain ChangeLogRainer Gerhards2013-11-071-6/+12
| | | |
| | * | bugfix: regular workers are no longer started if DA worker is activePavel Levshin2013-11-071-8/+7
| | | | | | | | | | | | | | | | | | | | form mail: Look, below, if it is time to activate DA worker, we call it explicitly. But in this case we do not advise regular workers. They are likely already running at this point, but it is not guaranteed. What if, for example, the system is set to start additional workers when the queue is going over high watermark? What if HighWatermark is set to 1? Regular workers will not be started, and DA worker may fail. Thus, it is reasonable to advise regular workers even if we are going DA.
| | * | cleanup no longer needed codeRainer Gerhards2013-11-074-8/+1
| | | |