| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
On many platforms, this has no effect at all. At some, it may cause
a segfault. The problem occurs only during config phase, no segfault
happens when rsyslog has fully started.
|
|\ |
|
| |\
| | |
| | |
| | |
| | | |
Conflicts:
runtime/nsdpoll_ptcp.c
|
| | | |
|
|\| | |
|
| | | |
|
|\| | |
|
| |\|
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | |
|
| | | |
|
| | | |
|
|\| | |
|
| |\|
| | |
| | |
| | |
| | | |
Conflicts:
plugins/imuxsock/imuxsock.c
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This happened only under some circumstances. Thanks to Marius
Tomaschwesky, Florian Piekert and Milan Bartos for their help in
solving this issue.
Note that Milan sent a patch, which solved the problem under some
conditions (can be found somewhat earlier in git history). However,
it did not handle the original root cause, and so did not fix the
problem always. The main reason was that the date parser modifies
the provided lenghts. That part of the API was not properly
used by the caller (who decremented the length once more).
|
| | |
| | |
| | |
| | | |
modified: plugins/imuxsock/imuxsock.c
|
|\| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
CEE originally specified the cookie with SP, whereas other lumberjack
tools used it without space. In order to keep interop with lumberjack,
we now use the cookie without space as well. I hope this can be changed
in CEE as well when it is released at a later time.
Thanks to Miloslav Trmač for pointing this out and a similiar v7 patch.
|
|\| | |
|
| |\| |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Thanks to Michael Biebl for identifying this as the culprit for
several build-related issues. The plugin is a placeholder, and was
not used for quite some while. It is definitely not worth the effort
to keep it along. If needed, can be quickly created.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
This could lead to startup with invalid parameters.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\| | |
|
| |\|
| | |
| | |
| | |
| | | |
Conflicts:
plugins/imrelp/imrelp.c
|
| | | |
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
This does not have any practical problems associated with it, EXCECPT
that it caused almost all valgrind testbench tests to fail.
|
|\| |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
|
| |\|
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
SCM_CREDENTIALS is not a socket option; its value is usually
0x2 which on most archs corresponds to socket option
SO_REUSEADDR, but on mips-arch there is no socket option
with value 0x2 and SO_REUSEADDR = 0x4, so the call will fail
with ENOPROTOOPT 'Protocol not available'; skip it.
There does not seem any other special setsockopt call is
needed anyway, besides the above.
In addition Jonny Törnbom commented:
SCM_CREDENTIALS is a control message type, not a socket option, so using
setsockopt(...SCM_CREDENTIALS...) is potentially dangerous and wrong and
should be deleted from the code. (SCM_CREDENTIALS is used in conjuction
with SO_PASSCRED which is the socket option to use.)
|
| |\| |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
It does nothing, at is just confusing.
Signed-off-by: Miloslav Trmač <mitr@redhat.com>
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
now the complete code (JSON passing & ommongodb) could be tested
and passed the module tests made during development
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Uses a json-c library (http://oss.metaparadigm.com/json-c/).
With this, a template
> $template MongoTemplate,"{%hostname:::jsonf:sys%, %$!all-json:2:$:%"
and action
> & action(type="ommongodb" db="ceelog" collection="local" template="MongoTemplate")
will store a record created by
> logger -d -u p/dev/log -p mail.info -t mymailer '@cee: {"false": false, "null": null, "true": true, "object": {"a":"a", "b":"b"}, "array": [1, 2, 3], "number1": 3, "number2": 3.14, "string": "String"}'
as
> { "_id" : ObjectId("5037bbfc97dd811374ce5a00"), "sys" : "kulicka", "false" : "false", "null" : "-", "true" : "true", "object.a" : "a", "object.b" : "b", "array.*" : "3", "number1" : "3", "number2" : "3.140000", "string" : "String" }
which is not great, but fair enough given the current design of
libee (the information loss manifests by the time of template processing,
ommongodb can't fix it).
Signed-off-by: Miloslav Trmač <mitr@redhat.com>
|