| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
If no default template is set, a segfault occured on startup.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
This prevents linking with libee, liblognorm and libgcrypt when not
necessary.
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
This solves problems with some build environments.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Accidently, the old-style cache size parameter was used when the
dynafile cache was created in a RainerScript action. If the old-style
size was lower than the one actually set, this lead to misadressing
when the size was overrun, and that could lead to all kinds of
"interesting things", often in segfaults.
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=440
Conflicts:
ChangeLog
|
| |
| |
| |
| | |
either rscryutil or rsgtutil man was installed, but not both
|
| |
| |
| |
| |
| |
| | |
We don't want to hard-code `libgcrypt-config --libs` at various.
Also, make sure LIBGCRYPT_CFLAGS and LIBGCRYPT_LIBS are correctly
substituted.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
|
| | |
| | |
| | |
| | | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=426
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
including their generation via rscrytool
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
also add test parameter to be able to set key
|
| | |
| | |
| | |
| | | |
rough baseline, needs to be extended for actual use.
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
runtime/queue.c
|
| |/
| |
| |
| | |
it didn't do so if it was inside a retry loop
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This is tested as far as possible. However, the actual extend
case can only be tested in about three weeks from now when the
next publication is out. I have done module-testing with a
mockup extend call, so chances are great the final test will
be passed.
|
| |
| |
| |
| |
| |
| |
| | |
... done up until the point where I need to wait for the
timestamps to become extendible. So doing a milestone commit
to make sure the work is inside the archive. Actual writing of the
extended timestamp is missing.
|
| |
| |
| |
| | |
does not contain actual implementation
|
| | |
|
| |
| |
| |
| |
| | |
The way tlvrecords are processed is changed in order to
provide better extensibility for further work.
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | | |
Conflicts:
configure.ac
runtime/rsyslog.h
|
| |\| |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
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:
runtime/debug.h
tools/syslogd.c
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- 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.
|
| |\|
| | |
| | |
| | |
| | |
| | | |
Conflicts:
configure.ac
doc/manual.html
|
| | |
| | |
| | |
| | | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=418
|
| | |
| | |
| | |
| | |
| | | |
This helps prevent message routing loops, and is vital to have
if omjournal is used together with traditional syslog.
|
| | | |
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
We now use a higher-level verification function as suggested
by GuardTime.
|
|/ / / |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
unfortunately, there seems to be a problem with the GuardTime API, so
that I need their support before being able to carry on. Once I
receive it, it should be fairly quick to complete the function. I am
commiting this work as I do not know how long it will take to receive
an answer.
|