| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
... when working with disk queues.
|
|
|
|
|
|
| |
(depending on configuration). This was a small change, but with big
results. There is more potential to explore, but the effects were so
dramatic that I think it makes sense to include this fix.
|
|
|
|
| |
Happend e.g. with imuxsock.
|
|
|
|
| |
...which permits to set a new console log level while rsyslog is active
|
|
|
|
|
| |
This could lead to timestamps written in the wrong format, but not to
an abort.
|
|\ |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | |
|
| | | |
|
|\| |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
actually destructed.
This most likely had no effect to existing code, but it may also have
caused trouble in remote cases. Similarly, the fix may also cause trouble...
Due to this trouble scenario, the fix deserves its own commit.
|
|\| |
| | |
| | |
| | |
| | | |
Conflicts:
tools/syslogd.c
|
| |\ \
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
stderr/stdout were not closed to be able to emit error messages,
but this caused ssh sessions to hang. Now we close them after the
initial initialization. See forum thread:
http://kb.monitorware.com/controlling-terminal-issues-t9875.html
|
| | | |
| | | |
| | | |
| | | |
| | | | |
the deferred activation of input modules broke part of the testbench -
but this was a testbench issue, not one of the patch
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- bugfix: subtle (and usually irrelevant) issue in timout processing
timeout could be one second too early if nanoseconds wrapped
- set a more sensible timeout for shutdow, now 1.5 seconds to complete
processing (this also removes those cases where the shutdown message
was not written because the termination happened before it)
|
| | | |
| | | |
| | | |
| | | |
| | | | |
... as far as I think this mostly is to keep the thread debuggers
happy
|
|\| | | |
|
| |\| | |
|
| | |\| |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Detected under threading debugger, seems not to have any impact on
actual deployments.
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
Conflicts:
ChangeLog
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
... hopefully removes false positives (but may cause some trouble
with hostname parsing). For details, see this bug tracker:
http://bugzilla.adiscon.com/show_bug.cgi?id=126
This patch is not optimal for v4 - another one will follow. The spirit
of this commit is to enable easier backporting if someone is interested
in doing so.
|
| | | |
| | | |
| | | |
| | | | |
tests for the various timestamp formats have been added
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
tools/omfile.c
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Conflicts:
ChangeLog
runtime/msg.h
tcps_sess.c
tcpsrv.c
tools/syslogd.c
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
plus some cleanup...
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
now contain a copy of the config line that (most likely) caused the error
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The former maximum of 10,000 really made no sense, even 1,000 is very high,
but we like to keep the user in control ;)).
Also, some general cleanup was done.
|
|\ \ \ \ \ \
| | |_|_|/ /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | | | | |
|
| | | | | | |
|
| |_|_|/ /
|/| | | | |
|
|\| | | |
| |_|/ /
|/| | | |
|
| |\ \ \
| | | |/
| | |/| |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- bugfix: invalid error message issued if $inlcudeConfig was on an empty
set of files (e.g. *.conf, where none such files existed)
thanks to Michael Biebl for reporting this bug
- bugfix: when run in foreground (but not in debug mode), a
debug message ("DoDie called") was emitted at shutdown. Removed.
thanks to Michael Biebl for reporting this bug
- bugfix: some garbagge was emitted to stderr on shutdown. This
garbage consisted of file names, which were written during
startup (key point: not a pointer error)
thanks to Michael Biebl for reporting this bug
- bugfix: startup and shutdown message were emitted to stdout
thanks to Michael Biebl for reporting this bug
|
| | | |
| | | |
| | | |
| | | | |
stderr and stdo are now kept open across fork()
|
| |_|/
|/| |
| | |
| | |
| | | |
... as well as some cleanup (some commented-out code is left to
support UxTradMsg again is someone really complains ;)).
|
| | | |
|
| | |
| | |
| | |
| | | |
(in addition to rather specific syslog tcp server)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
sending n messages
New config directive $ActionSendUDPRebindInterval
added for the purpose. By default, rebinding is disabled. This is
considered useful for load balancers.
|
|\| | |
|
| |\| |
|
| | |
| | |
| | |
| | | |
(testcase was only present in v4, so I did not spot the issue immediately)
|
| |\|
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
|
| | |
| | |
| | |
| | | |
... as well as some other minor issues.
|
|\| |
| | |
| | |
| | |
| | | |
Conflicts:
tests/Makefile.am
|