| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
We noticed this race issue under Solaris (thanks to its different
scheduler, I guess). In some cases, the previous instance of rsyslogd
was not terminated, resulting in a failure on the next test. Now
handled correctly.
|
|
|
|
| |
new tests added, now much better
|
|
|
|
|
|
|
|
| |
The testbench has now a generic driver that can run a whole class
of test suites just by providing a config file and test cases. This
does not cover all testing needs, but a lot.
We have now added one test for the new array-passing output plugin
interface.
|
|
|
|
|
| |
interestingly, they manifested on Debian, only, but potentially
existed on other platforms, too.
|
| |
|
|\
| |
| |
| |
| | |
Conflicts:
tests/Makefile.am
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
I finally removed the tcl script because tcl costs a lot of
time if you do not invest the full learning cycle, plus I have
not everything avaible I need on Solaris. With C, I am quicker and
I also can create a superior solution. So I finally switched. Took
much less time than the initial tcl script...
|
| |
| |
| |
| | |
especially when executed as non-root
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
integrated tcl test script into autotools make check, created
a few test cases based a real-world sample and samples from
RFC3164 and 5424.
|
| |
| |
| |
| |
| | |
more or less complete now, with some minor nits left for later
but is usable.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
worked on ways to provide a better test suite:
- added -T rsyslogd command line option, enables to specify a directory
where to chroot() into on startup. This is NOT a security feature but
introduced to support testing. Thus, -T does not make sure chroot()
is used in a secure way. (may be removed later)
- added omstdout module for testing purposes. Spits out all messages to
stdout - no config option, no other features
- modified $ModLoad statement so that for modules whom's name starts with
a dot, no path is prepended (this enables relative-pathes and should
not break any valid current config)
|
|/ |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
Makefile.am
configure.ac
doc/manual.html
|
| |
| |
| |
| |
| |
| | |
pkg-config uses uppercase for its _CFLAGS and _LIBS variable names.
So we follow suit and convert all _cflags and _libs variables to
uppercase for more consistency.
|
|/ |
|
|
|
|
| |
I left some file in the file system, cause make distcheck to fail...
|
|
|
|
|
|
|
| |
I disabled some make check checks for make distcheck. I need
to add some addtl support for make distcheck environment to
rsyslogd and I don't like to hold 3.21.1 just for that any
longer.
|
| |
|
|
|
|
|
|
| |
- bugfix: no error was reported if the target of a $IncludeConfig
could not be accessed.
- added testbed for common config errors
|
| |
|
| |
|
|
|
|
|
| |
it now works based on test case files, which enable to quickly
generate test cases.
|
|
|
|
|
|
| |
This is needed so that we can create simple testbenches which
will check the result of a test (a generated program) via a
simple strcmp.
|
|
|
|
|
|
|
|
|
| |
I disabled a check below, because I can not find the cause of the
misalignment. The problem is that pToken structure has a different
member alignment inside the runtime library then inside of this
program. I checked compiler options, but could not find the cause.
Should anyone have any insight, I'd really appreciate if you drop me
a line.
|
|
|
|
|
|
| |
..., restructured makefile, added some troubleshooting to test case
(program rscript-parse.c has problem due to different structure alignment,
where I do not yet know the reason)
|
| |
|
|
|