summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* yet another update of the systemd files we need to carry...Rainer Gerhards2013-03-221-21/+42
|
* build-sys: Fix "update-systemd" targetMichael Biebl2013-03-221-2/+2
| | | | The urls have changed.
* Fix linking for recent sd-daemon.c updateMartin Pitt2013-03-221-0/+2
| | | | | | | | | The recent update of sd-daemon.c introduced the usage of mq_getattr(), which is shipped in -lrt (but clock_gettime isn't any more in glibc 2.17). Also check for mq_getattr() in the rt library to fix linking with glibc 2.17. http://bugzilla.adiscon.com/show_bug.cgi?id=428
* update systemd files to match current systemd sourceRainer Gerhards2013-03-212-37/+136
|
* bugfix: get rid of potential endless loop in doGetGID()Tomas Heinrich2013-03-201-13/+15
|
* bugfix: divide action queue discard mark by 10 - was out of rangeTomas Heinrich2013-03-121-2/+2
|
* doc: mention last patch in ChangeLogRainer Gerhards2013-01-141-0/+2
|
* bugfix: decrement string lengthTomas Heinrich2013-01-141-1/+3
|
* tcpflood: properly terminate when sending small filesRainer Gerhards2013-01-141-0/+2
|
* bugfix[kind of]: omudpspoof discarded messages >1472 bytes (MTU size)Rainer Gerhards2012-12-172-1/+10
| | | | | it now truncates these message, but ensures they are sent. Note that 7.2.5+ will switch to fragmented UDP messages instead (up to 64K)
* bugfix: invalid DST handling under SolarisScott Severtson2012-12-132-1/+3
|
* typo correctionRainer Gerhards2012-11-221-5/+5
|
* bugfix: imklog mistakenly took kernel timestamp subseconds as nanosecondsRainer Gerhards2012-11-222-12/+27
| | | | | | ... actually, they are microseconds. So the fractional part of the timestamp was not properly formatted. Thanks to Marius Tomaschwesky for the bug report and the patch idea.
* imklog: added $klogParseKernelTimestamp optionMarius Tomaschewski2012-11-214-1/+16
| | | | | | | | When enabled, kernel message [timestamp] is converted for message time. Default is to use receive time as in 5.8.x and before, because the clock used to create the timestamp is not supposed to be as accurate as the monotonic clock (depends on hardware and kernel) resulting in differences between kernel and system messages which occurred at same time.
* imklog: added $klogKeepKernelTimestamp optionMarius Tomaschewski2012-11-214-2/+13
| | | | | When enabled, the kernel [timestamp] remains at begin of each message, even it is used for the message time too.
* add "EAGAIN" patch to ChangeLogRainer Gerhards2012-11-131-0/+4
|
* imuxsock: do not log EAGAIN in nonblocking recvfromMarius Tomaschewski2012-11-131-1/+1
|
* doc: v3 compatibility doc lists invalid config directiveRainer Gerhards2012-10-221-1/+1
| | | | closes: http://bugzilla.adiscon.com/show_bug.cgi?id=365
* fix epoll-enabled code to use correct data member for pointersRainer Gerhards2012-10-192-4/+4
|
* preparing for 5.10.1v5.10.1Rainer Gerhards2012-10-173-4/+4
|
* imklog: use memmove instead of memcpy (solaris)Marius Tomaschewski2012-10-171-1/+1
|
* imklog: use memmove to remove kernel timestampMarius Tomaschewski2012-10-171-1/+1
|
* imklog: skip leading spaces in kernel timestampMarius Tomaschewski2012-10-171-1/+3
|
* bugfix: imuxsock truncated head of received messageRainer Gerhards2012-10-162-8/+6
| | | | | | | | | | | | | 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).
* fix problem with cutting first 16 characters from message with bAnnotate on ↵Milan Bartos2012-10-101-1/+5
| | | | modified: plugins/imuxsock/imuxsock.c
* remove cust1 dummy plugin from build systemRainer Gerhards2012-10-044-27/+1
| | | | | | | 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.
* minor: disable debug support in complex1.sh testRainer Gerhards2012-10-021-2/+2
|
* cleanupRainer Gerhards2012-10-021-1/+1
|
* bugfix: fixed wrong bufferlength for snprintf in tcpflood.cAndre Lorbach2012-09-283-3/+5
| | | | | The problem occured when using the -f (dynafiles) option, and caused some tests to fail.
* enable DNS resolution in imrelpApollon Oikonomopoulos2012-09-262-0/+9
|
* Debug logging slightly improvedRainer Gerhards2012-09-141-1/+1
|
* bugfix: invalid property name in property-filter could cause abortRainer Gerhards2012-09-132-56/+67
| | | | | | ...if action chaining (& operator) was used http://bugzilla.adiscon.com/show_bug.cgi?id=355 Thanks to pilou@gmx.com for the bug report
* remove unused variables (if SCM_CREDENTIALS is not available)Cristian Ionescu-Idbohrn2012-09-122-1/+9
|
* imuxsock: remove incorrect socket option callCristian Ionescu-Idbohrn2012-09-121-4/+0
| | | | | | | | | | | | | | | | 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.)
* fix compile problem on FreeBSDBrad Davis2012-09-111-3/+1
|
* Merge branch 'v5-stable' of git+ssh://git.adiscon.com/git/rsyslog into v5-stableRainer Gerhards2012-08-253-30/+48
|\ | | | | | | | | Conflicts: template.c
| * change template.[ch] to ASL 2.0, removing a GPLv3-only patchRainer Gerhards2012-08-253-30/+48
| | | | | | | | | | see template.c file header for details Note that this functionality was almost never used in practice
* | preparing for 5.10.0 releasev5.10.0Rainer Gerhards2012-08-224-4/+11
| |
* | Merge branch 'v5-stable' into v5-betaRainer Gerhards2012-08-221-2/+6
|\| | | | | | | | | | | | | Conflicts: ChangeLog configure.ac doc/manual.html
| * preparing for 5.8.13 releasev5.8.13Rainer Gerhards2012-08-223-3/+3
| |
| * nit: forward-compatible default ruleset name as used in next versionRainer Gerhards2012-08-221-1/+1
| |
* | small bugfix: stream timeout API use was incorrectRainer Gerhards2012-08-221-2/+2
| | | | | | | | Thanks to Andre Lorbach for mentioning this.
* | Merge branch 'v5-stable' into v5-betaRainer Gerhards2012-08-226-18/+119
|\| | | | | | | | | Conflicts: runtime/ruleset.c
| * bugfix: multiple main queues with same queue file name were not detectedRainer Gerhards2012-08-223-3/+48
| | | | | | | | | | | | This lead to queue file corruption. While the root cause is a config error, it is a bug that this important and hard to find config error was not detected by rsyslog.
| * nitfix: remove quirck in new debug message codeRainer Gerhards2012-08-011-4/+2
| |
| * more elaborate debug logging for object deserializerRainer Gerhards2012-08-011-0/+39
| |
| * undo last queue patch - caused a regressionRainer Gerhards2012-08-012-5/+1
| | | | | | | | some more elaborate patch is needed and will be provided
| * bugfix: potential abort if output plugin logged message during shutdownRainer Gerhards2012-08-012-7/+28
| | | | | | | | | | | | | | note that none of the rsyslog-provided plugins does this Thanks to bodik and Rohit Prasad for alerting us on this bug and analyzing it. fixes: http://bugzilla.adiscon.com/show_bug.cgi?id=347
| * bugfix: DA queue fixed handling of bad queue files.Andre Lorbach2012-07-312-1/+5
| |
| * bugfix: strm class could abort under some circumstancesRainer Gerhards2012-07-241-6/+4
| | | | | | | | | | ... it could pass a NULL pointer to unlink. Depending on OS implementation, this could (or could not...) lead to a segfault.
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-05 09:34:31 +0000