| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Conflicts:
tools/omfwd.c
|
|\ \ \ \ \ \
| | |_|_|_|/
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Conflicts:
ChangeLog
Makefile.am
configure.ac
doc/manual.html
plugins/imptcp/imptcp.c
plugins/imudp/imudp.c
plugins/imuxsock/imuxsock.c
runtime/parser.c
template.c
tools/omfwd.c
tools/syslogd.c
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The new default turns off rate limiting. This was chosen as people
experienced problems with rate-limiting activated by default. Now it
needs an explicit opt-in by setting this parameter.
Thanks to Chris Gaffney for suggesting to make it opt-in; thanks to
many unnamed others who already had complained at the time Chris made
the suggestion ;-)
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
probably caused by a recent merge, was not present in 5.9.4
|
|\| | | | | |
|
| |\ \ \ \ \
| | | |_|_|/
| | |/| | |
| | | | | |
| | | | | | |
Conflicts:
plugins/imuxsock/imuxsock.c
|
| | | |_|/
| | |/| |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
a proper date.
The truncation occured because we removed that part of the messages
that was expected to be the date.
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=295
|
|\| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
plugins/imuxsock/imuxsock.c
runtime/modules.c
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
which contains some properties obtained from the system and as such
sure to not be faked. This is inspired by the similiar idea introduced
in systemd.
|
|\| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
runtime/conf.c
tools/omfile.c
tools/omusrmsg.c
|
| |\| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
plugins/imuxsock/imuxsock.c
|
| | | |/
| | |/|
| | | |
| | | |
| | | | |
if so configured (the *default*). Lead to no longer sub-second timestamps.
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=281
|
| | | | |
|
|\| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
plugins/imfile/imfile.c
plugins/imklog/imklog.c
plugins/imptcp/imptcp.c
plugins/imtcp/imtcp.c
plugins/imuxsock/imuxsock.c
plugins/mmsnmptrapd/mmsnmptrapd.c
tools/omfile.c
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This permits to read the time a message was submitted to the system
log socket. Most importantly, this is provided in microsecond resolution.
So we are able to obtain high precision timestampis even for messages
that were - as is usual - not formatted with them. This also simplifies
things in regard to local time calculation in chroot environments.
Many thanks to Lennart Poettering for suggesting this feature,
providing some guidance on implementing it and coordinating getting the
necessary support into the Linux kernel.
|
| | |
| | |
| | |
| | | |
now also properly works with privilege drop
|
| | |
| | |
| | |
| | | |
as far as we know that new interface right now ;)
|
| | | |
|
|\| |
| |/
|/|
| |
| | |
Conflicts:
tools/syslogd.c
|
| |
| |
| |
| |
| |
| |
| | |
reason was that a global config variable was invalidly accessed where a
listener variable should have been used.
Also performance-improved the case when rate limiting is turned off (this
is a very unintrusive change, thus done directly to the stable version).
|
|\|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
plugins/omlibdbi/omlibdbi.c
tests/Makefile.am
tests/diag.sh
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The capability has been added for module to specify that they do not
like being unloaded.
related bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=222
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| |/ |
|
| |
| |
| |
| |
| | |
The previous fix left variable lenMsg in an inconsistent state when
sanitization actually happend. This could lead to message truncation.
|
| |
| |
| |
| |
| | |
This also causes problems when NUL characters are present inside
the message (as is the case with spamd).
|
| |
| |
| |
| | |
thanks to Michael Biebl for alterting me
|
| |
| |
| |
| |
| |
| |
| | |
This was a regression from the imuxsock partial rewrite. Happened
because the message is no longer run through the standard parsers.
Now imuxsock does this sanitization itself.
bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=224
|
|\|
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | |
|
| |
| |
| |
| |
| |
| | |
Support for multiple unix sockets and activation in forking mode
Signed-off-by: Marius Tomaschewski <mt@suse.de>
|
|\|
| |
| |
| |
| | |
Conflicts:
ChangeLog
|
| |
| |
| |
| |
| |
| | |
by doing math a little bit more optimal in hash table code. Also reduced
memory requirement for imuxsock hash tables (expected number of connections
was set too high -- table can be extended dynamically).
|
|\| |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Note: we do rate-limiting by the pid and we obtain the pid via SCM_CREDENTIALS
socket options. So this patch effectively disables the (new) ratelimiting
capability. In a later patch, I'll see that I can provide a global ratelimiting
capability, which could always be used (an alternative may be using the tag, will
check this out as well).
|
|\|
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
plugins/imuxsock/imuxsock.c
runtime/rsyslog.h
|
| |\ |
|
| | |
| | |
| | |
| | |
| | | |
finally this looks almost production ready for files where no
directory path needs to be created
|
| | |
| | |
| | |
| | | |
I left a testing setting in, resulting in /dev/log never being deleted...
|
| |/
| |
| |
| |
| |
| |
| |
| | |
related bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=200
Note that this may not be the ultimate fix. I could not definitely
identify the root cause of the problem and so I did some changes
that I *think* (but could not verify) that resolved the issue.
|
| |
| |
| |
| | |
also improved test tool
|
| | |
|
| |
| |
| |
| |
| | |
rate limiting now applies only to messages with a given severity or above. By
default, emergency messages are NOT rate-limited.
|
| | |
|
| |
| |
| |
| | |
found at http://www.cl.cam.ac.uk/~cwc22/hashtable/
|
| |
| |
| |
| | |
works, but at a global level, need to go down to pid or cgroup
|
| | |
|