| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
also adds speed, because you do no longer need to run the whole file
system in sync mode. New testbench and new config directives:
- $MainMsgQueueSyncQueueFiles
- $ActionQueueSyncQueueFiles
|
|
|
|
|
|
|
|
| |
- added $GenerateConfigGraph configuration command which can be used
to generate nice-looking (and very informative) rsyslog configuration
graphs.
- added $ActionName configuration directive (currently only used for
graph generation, but may find other uses)
|
|
|
|
|
| |
This is more efficient for some outputs. They new can receive fields not only
as a single string but rather in an array where each string is seperated.
|
|\
| |
| |
| |
| | |
Conflicts:
ChangeLog
|
| |
| |
| |
| |
| |
| |
| | |
- fixed a bug that caused action retries not to work correctly
situation was only cleared by a restart
- bugfix: closed dynafile was potentially never written until another
dynafile name was generated - potential loss of messages
|
|/
|
|
|
|
|
|
|
| |
Unfortunatley, I do not have the full list of contributors
available. The patch set was compiled by Ben Taylor, and I made
some further changes to adopt it to the news rsyslog branch. Others
provided much of the base work, but I can not find the names of the
original authors. If you happen to be one of them, please let me
know so that I can give proper credits.
|
|
|
|
|
|
| |
so that the "last message repeated n times" messages, if generated, may
have an alternate format that contains the message that is being repeated.
Note that this is on an action-by-action basis.
|
|
|
|
| |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was suggested by David Lang, to help identify the message that was
repeated. A problem is that I do not have the expanded template at
hand when the "last ... times" message is generated. Spending much time
on this functionality is also probably not a good thing, as the whole
functionality will be overhauled (and once this is done we will not at
all have the output template at hand). So the approach is to use a single
field - here msg - and inlcude it as a notation of what was repeated. This
is far from being perfect, but eventually good enough. I will now wait
for feedback before going any further.
|
|
|
|
|
| |
...which enables to configure HUP to be either a full restart
or "just" a leightweight way to close open files
|
| |
|
|
|
|
|
|
|
| |
This enhances performance and, as some have pointed out, is
probably also more consistent with what users expect how
the various output-timestamp related function should work. This
commit needs some more testing.
|
| |
|
|
|
|
|
|
| |
... for the purpose of conducting a few external tests. This is a
first approach at removing the time() call in the output, but it shows
there are some subleties we need to address.
|
|
|
|
|
|
|
| |
... but did not manage to avoid doing at least one call. So
this change introduced performance benefit only in a few
non-common situations. Anyhow, it hopefully levels ground
for better things to come.
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
runtime/rsyslog.h
tools/syslogd.c
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
runtime/datetime.h
runtime/rsyslog.h
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
default discard severity was incorrectly set to 4, which lead
to discard-on-queue-full to be enabled by default. That could cause
message loss where non was expected. The default has now been changed
to the correct value of 8, which disables the functionality. This
problem applied both to the main message queue and the action queues.
Thanks to Raoul Bhatia for pointing out this problem.
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
action.c
configure.ac
doc/manual.html
|
| |\|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
(until the previous time was reached again). There are still some
side-effects when time is rolled back (A time rollback is really a bad
thing to do, ideally the OS should issue pseudo time (like NetWare did)
when the user tries to roll back time).
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
This also lead to the addition of two new config directives:
$ActionExecOnlyEveryNthTime and $ActionExecOnlyEveryNthTimeTimeout
This feature is useful, for example, for alerting: it permits you to
send an alert only after at least n occurences of a specific message
have been seen by rsyslogd. This protectes against false positives
due to waiting for additional confirmation.
|
| |
| |
| |
| |
| | |
Also added redirector to web description of error codes
closes bug http://bugzilla.adiscon.com/show_bug.cgi?id=20
|
| | |
|
| | |
|
|/
|
|
|
| |
reduced dependencies, moved non-runtime files to its own directory except
for some whom's status is unclear
|
| |
|
|
|
|
| |
with queues - so things can be configured to be done at off-peak hours
|
|
|
|
| |
prevent unintentional message loss
|
|
|
|
| |
source and its capablity to be delayed without bad side effects)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
own class and converted to new object calling conventions
(interface-based)
- converted gss-misc into a loadable library module
|
|
|
|
|
|
|
|
|
|
|
| |
- moved module loader from conf.c to module.c, where it belongs
- made the necessary plumbing to auto-load library modules
- upgraded debug system to include iRet in function exit message
- changed module interface so that instances need only to be supported by
output plugins (if we actually need them for input plugins, we can
always add it again...)
- milestone: first implementation of library modules (but do not get
unloaded on exit/hup so far)
|
|
|
|
| |
interface structure
|
| |
|
|
|
|
| |
had a single thread and non-direct action queues were used
|
|
|
|
| |
http://bugzilla.adiscon.com/show_bug.cgi?id=4
|
|
|
|
|
| |
- some cleanup
- doc improvements
|
| |
|
|
|
|
|
| |
- some initial effort for malloc/free debugging support
- bugfix: using dynafile actions caused rsyslogd abort
|
|
|
|
|
|
| |
direct queue mode. Now fixed. Tracker was
http://sourceforge.net/tracker/index.php?func=detail&aid=1886931&group_
id=123448&atid=696552
|
| |
|
|
|
|
|
| |
was trapped again ;) -- now fixed, sizes > 2GB supported on 32bit
platforms
|
|
|
|
|
|
|
| |
- fixed wrong action suspend/resume handling
- we have some issue with the mutx in dbgoprint, but that is acceptable for
the time being, I just removed the deadlock codition (debug system
only)
|
|
|
|
|
|
|
| |
$<obj>WorkerTimoutThreadShutdown for consistency reasons
- changed default for action queue size to 1000 elements (more reasonable
here)
- fixed bug in sample rsyslog.conf
|
|
|
|
|
| |
- addded $MainMsgQueueMaxDiskSpace config directive
- addded $ActionQueueMaxDiskSpace config directive
|
|
|
|
|
|
| |
- addded $ActionQueueDequeueSlowdown config directive
- addded $MainMsgQueueDequeueSlowdown config directive
- bugfix: MsgDup() did not work with new base object data structure
|