summaryrefslogtreecommitdiffstats
path: root/tools/syslogd.c
Commit message (Collapse)AuthorAgeFilesLines
* output memory allocator in version displayRainer Gerhards2013-11-261-0/+5
|
* fix: ruleset queues were activated too earlyRainer Gerhards2013-11-141-2/+7
| | | | | | | | | This does not cause issues in v7, but here we have the problem that the total number of actions, which now is required for wti sizing, is not available at that early stage. So we needed to delay queue startup until everything is processed (just as it should have been already!). Note the previously we could have a segfault on first message when ruleset queues were used.
* refactor bShutdownImmediate handlingRainer Gerhards2013-11-051-3/+2
|
* refactor: move pbShutdownImmediate to wti_tRainer Gerhards2013-11-051-4/+4
|
* cleanup: multiple rulesets inside a single batch are now OKRainer Gerhards2013-11-041-9/+0
| | | | | They don't require special handling any longer, so do no longer care about them.
* milestone: calling sequence changed so that wti is passed to many functionsRainer Gerhards2013-10-261-2/+2
|
* make rsyslog version output include the number of bits used for RainerScriptRainer Gerhards2013-10-261-0/+5
|
* reload lookup tables on HUPRainer Gerhards2013-07-161-0/+1
|
* Merge branch 'v7-stable'Rainer Gerhards2013-06-151-0/+2
|\
| * systemd: use service type notifyCristian Rodríguez2013-06-141-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | There is a time window, between rsyslog reporting syntax errors and the daemon returning with failure, this may cause systemctl restart rsyslog to not report any error inmediately but later in the logs which is confusing to users. The appropiate steps to correct this annoyance is to notify systemd with a simple sd_notify(0, "READY=1"); just before entering the main loop. Tested in openSUSE 12.3/13.1 x86_64
* | Merge branch 'nextmaster'Rainer Gerhards2013-06-061-4/+12
|\ \ | |/ |/| | | | | Conflicts: ChangeLog
| * enable shuffling of crypto parameters down through queue definitionRainer Gerhards2013-05-101-4/+4
| |
| * Add configurable local client IPAxel Rau2013-05-061-1/+9
| |
* | Drop unneeded macro definitionTomas Heinrich2013-05-201-1/+0
|/ | | | | | The macro itself was a malformed version of "_GNU_SOURCE" and thus had no effect. It is not needed as this macro is already defined via AC_GNU_SOURCE.
* bugfix: off-by-one error in handling local FQDN name (regression)Rainer Gerhards2013-04-241-1/+1
| | | | | | | A remporary buffer was allocated one byte too small. Did only affect startup, not actual operations. Came up during routine tests, and can have no effect once the engine runs. Bug was introduced in 7.3.11.
* cleanupRainer Gerhards2013-04-241-1/+0
|
* Merge branch 'master-crypto'Rainer Gerhards2013-04-171-0/+7
|\ | | | | | | | | Conflicts: ChangeLog
| * bugfix: $PreserveFQDN is not properly workingLouis Bouchard2013-04-171-0/+7
| | | | | | | | closes: http://bugzilla.adiscon.com/show_bug.cgi?id=426
* | Merge branch 'c7' into tmpRainer Gerhards2013-04-091-0/+1
|\ \ | |/ |/| | | | | | | | | Conflicts: ChangeLog configure.ac runtime/queue.c
| * make imrelp properly terminate on system shutdownRainer Gerhards2013-04-091-0/+1
| | | | | | | | it didn't do so if it was inside a retry loop
| * bugfix: stdout/stderr were not closed on forkingRainer Gerhards2013-03-211-1/+1
| | | | | | | | | | | | | | | | | | but were closed when running in the forground - this was just reversed of what it should be. This is a regression of a recent change. Conflicts: ChangeLog
* | bugfix: stdout/stderr were not closed on forkingRainer Gerhards2013-03-201-1/+1
| | | | | | | | | | but were closed when running in the forground - this was just reversed of what it should be. This is a regression of a recent change.
* | fix merge problemv7.3.8Rainer Gerhards2013-03-181-4/+4
| |
* | Merge branch 'v7-stable'Rainer Gerhards2013-03-181-15/+22
|\| | | | | | | | | | | Conflicts: runtime/debug.h tools/syslogd.c
| * debug system improvement & bug fix for init system status (see below)Rainer Gerhards2013-03-151-20/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | - rsyslogd startup information is now properly conveyed back to init when privileges are beging dropped Actually, we have moved termination of the parent in front of the priv drop. So it shall work now in all cases. See code comments in commit for more details. - If forking, the parent now waits for a maximum of 60 seconds for termination by the child - improved debugging support in forked (auto-backgrounding) mode The rsyslog debug log file is now continued to be written across the fork.
* | imuxsock: add capability to ignore messages from ourselfesRainer Gerhards2013-02-261-6/+5
| | | | | | | | | | This helps prevent message routing loops, and is vital to have if omjournal is used together with traditional syslog.
* | optimze: reduce memory operations during dns resolution/hostname settingRainer Gerhards2013-01-221-6/+6
| | | | | | | | | | | | | | | | | | | | previously, hostname and ip strings were shuffled to the msg object, which created a property out of them. Now the cache holds the property, and it is resused (almost) everywhere, what saves a lot of memory operations. The only exception is imtcp session setup, where different handling of the hostname is done, which we need to sort out (but that's another story).
* | optimize: have dns cache pre-create rsyslog prop_t'sRainer Gerhards2013-01-241-4/+3
| |
* | optimize: reduce nbr of strcpy() in FROMHOST processingRainer Gerhards2013-01-181-3/+4
| |
* | optimize memory layout for much better cache hitsRainer Gerhards2013-01-151-3/+3
| | | | | | | | | | | | | | | | Moave element status out of batch_obj_t because we get a *much* better cache hit ratio this way. Note that this is really a HUGE saving, even if it doesn't look so (both profiler data as well as practical tests indicate that!).
* | minor cleanupRainer Gerhards2012-12-141-1/+0
| |
* | Merge branch 'v7-stable-newmsglock' into master-newmsglockRainer Gerhards2012-12-061-67/+67
|\| | | | | | | | | | | | | Conflicts: runtime/msg.c runtime/queue.c tools/syslogd.c
| * Merge branch 'v6-stable-newmsglock' into v7-stable-newmsglockRainer Gerhards2012-12-061-10/+0
| |\ | | | | | | | | | | | | Conflicts: tools/syslogd.c
| | * bugfix: some message properties could be garbled due to race conditionRainer Gerhards2012-12-061-10/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This happened only on very high volume systems, if the same message was being processed by two different actions. This was a regression caused by the new config processor, which did no longer properly enable msg locking in multithreaded cases. The bugfix is actually a refactoring of the msg locking code - we no longer do unlocked operations, as the use case for it has mostly gone away. It is potentially possible only at very low-end systems, and there the small additional overhead of doing the locking does not really hurt. Instead, the removal of that capability can actually slightly improve performance in common cases, as the code path is smaller and requires slightly less memory writes. That probably outperforms the extra locking overhead (which in the low-end case always happens in user space, without need for kernel support as we can always directly aquire the lock - there is no contention at all).
| * | fix missing functionality: ruleset(){} could not specify ruleset queueRainer Gerhards2012-11-301-52/+57
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The "queue.xxx" parameter set was not supported, and legacy ruleset config statements did not work (by intention). The fix introduces the "queue.xxx" parameter set. It has some regression potential, but only for the new functionality. Note that using that interface it is possible to specify duplicate queue file names, which will cause trouble. This will be solved in v7.3, because there is a too-large regression potential for the v7.2 stable branch.
| * | silence compiler warningsRainer Gerhards2012-11-301-6/+11
| | | | | | | | | | | | | | | the changes do not affect actual code execution, just keep the compile log clean.
* | | Merge branch 'v7-stable'Rainer Gerhards2012-11-221-0/+2
|\| |
| * | Merge branch 'v6-stable' into tmpRainer Gerhards2012-11-221-0/+2
| |\|
| | * bugfix: hostname set in rsyslog.conf was not picked up until HUPoxpa2012-11-221-0/+2
| | | | | | | | | | | | which could also mean "never" or "not for a very long time".
| | * Merge branch 'v6-stable' into v6-betaRainer Gerhards2012-10-171-14/+5
| | |\
* | | | Merge branch 'v7-stable'Rainer Gerhards2012-11-091-0/+5
|\| | |
| * | | enabled to build without libuuid, at loss of uuid functionalityRainer Gerhards2012-11-091-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | this enables smoother builds on older systems that do not support libuuid. Loss of functionality should usually not matter too much as uuid support has only recently been added and is very seldom used.
* | | | queue: change generic msg ptr (pUsr) to be of msg_t typeRainer Gerhards2012-11-031-3/+3
| | | |
* | | | Merge branch 'master-ratelimit'Rainer Gerhards2012-10-301-119/+48
|\ \ \ \ | |/ / / |/| | |
| * | | rate-limit rsyslog internal messagesRainer Gerhards2012-10-231-2/+7
| | | | | | | | | | | | | | | | | | | | a special ratelimiter is used; it's linux-type ratelimit settings are currently hardcoded
| * | | Merge branch 'master' into master-ratelimitRainer Gerhards2012-10-231-1/+1
| |\ \ \ | | | | | | | | | | | | | | | | | | | | Conflicts: ChangeLog
| * | | | remove "last message repeated n times" from rsyslog output partRainer Gerhards2012-10-231-75/+3
| | | | |
| * | | | ratelimit: add default ratelimiterRainer Gerhards2012-10-191-4/+14
| | | | |
| * | | | cleanupRainer Gerhards2012-10-191-38/+0
| | | | |
| * | | | Merge branch 'master' into master-ratelimitRainer Gerhards2012-10-191-14/+5
| |\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: ChangeLog configure.ac doc/manual.html
generated by cgit v1.2.3 (git 2.25.1) at 2025-04-24 21:34:46 +0000