| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
action.c
configure.ac
doc/imuxsock.html
plugins/imklog/imklog.c
plugins/imptcp/imptcp.c
plugins/imtcp/imtcp.c
plugins/imudp/imudp.c
plugins/imuxsock/imuxsock.c
runtime/glbl.c
runtime/glbl.h
runtime/net.c
runtime/ruleset.c
tcpsrv.h
tools/syslogd.c
|
| | |
| |
| |
| | |
... for imtcp, directive is $InputTCPServerSupportOctetCountedFraming
|
| | |
| |
| |
| |
| | |
at the socket layer.
reference: http://kb.monitorware.com/post20791.html
|
| |/
|
|
|
| |
... to select if tcp received messages shall be flagged as
light delayable or not.
|
| |
|
|
| |
via new directive "$InputTCPServerDisableLFDelimiter on"
|
| |
|
|
|
| |
This offers considerable additional flexibility AND superior performance
(in cases where multiple inputs now can avoid lock contention)
|
| |
|
|
|
| |
also bumped version number and corrected ChangeLog, where I merged
some post 5.3.1 changes into the 5.3.1 section.
|
| | |
|
| |
|
|
| |
permits to specify how many TCP servers shall be possible (default is 20).
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Well, actually this and a lot of related things. I improved the
testbench so that the new capabilities are automatically tested and
also did some general cleanup. The current multiple tcp listener
solution will probably receive some further cleanup, too, but looks
quite OK so far. I also reviewed the way tcpsrv et all work, in
preparation of using this code for imdiag. I need to document the
findings, especially as the code is rather complicated "thanks" to
the combination of plain tcp and gssapi transport modes.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- added $InputTCPServerAddtlFrameDelimiter config directive, which
enabeles to specify an additional, non-standard message delimiter
for processing plain tcp syslog. This is primarily a fix for the invalid
framing used in Juniper's NetScreen products. Credit to forum user
Arv for suggesting this solution.
- added $InputTCPServerInputName property, which enables a name to be
specified that will be available during message processing in the
inputname property. This is considered useful for logic that treats
messages differently depending on which input received them.
|
| |
|
|
| |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| |\
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Update the documentation to use the new, preferred $ModLoad syntax:
- no more MySQL
- name of the in/output plugin without the trailing .so
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | |
|
| |/ |
|
| |
|
