| Age | Commit message (Collapse) | Author |
|---|
|
on my old sparc64.
|
|
From Florian Riehm.
|
|
|
|
an established connection has been closed.
|
|
response's content length may be an unexpected value as an error
page is shown.
|
|
write to trigger connection close, allow errors EPIPE or ECONNRESET.
|
|
when it receives a SIGHUP.
|
|
|
|
logging of SSL errors. Do not import unneeded Socket constants.
|
|
rsyslogd from ports. If the rsyslog package is installed, rsyslogd
is used as drain to test interoperability. This will be especially
useful for syslog via TCP and TLS.
|
|
|
|
its log file. Change regression tests form ssl to tls.
|
|
ok bluhm@
|
|
|
|
|
|
select(2) is used by syslogd.
|
|
spaces in the syslog messages.
|
|
|
|
very difficult to do so with standard tools
|
|
|
|
the short host name.
|
|
Also check that the maximum number of -a path is handled correctly.
|
|
the ktrace output of syslogd. Also make the tests work without DNS
and without sudo.
|
|
|
|
machine, each test kills any syslogd first. At the end the system's
syslogd gets restarted.
The test framework runs a client, and a server, and a syslogd. The
messages are passed via the log socket or via UDP from the client
to syslogd. From there UDP transport is used to reach the server.
All processes write log files where the message has to show up.
The test arguments are kept in the args-*.pl files.
The content of a log file, the data sent to a pipe process and what
the server received are checked. The invocation of the sendsyslog(2)
syscall is checked with ktrace, the open file descriptors of syslogd
are checked with fstat.
|
|
on the system may create log entries during the test run that show
up in the log file. Ignore those additional lines.
|
|
environment variables over sudo into syslogd. Run the tests with
the select(2) and poll(2) and kqueue(2) backend. Call "make libevent"
for these tests.
|
|
machine, each test kills any syslogd first. At the end the system's
syslogd gets restarted.
The test framework runs a client, and a server, and a syslogd. The
messages are passed via the log socket or via UDP from the client
to syslogd. From there UDP transport is used to reach the server.
All processes write log files where the message has to show up.
The test arguments are kept in the args-*.pl files.
The content of a log file, the data sent to a pipe process and what
the server received are checked. The invocation of the sendsyslog(2)
syscall is checked with ktrace, the open file descriptors of syslogd
are checked with fstat.
|
|
Yep espie@
|
|
|
|
command line switch and udp4:// or udp6:// loghost prefix.
|
|
|
|
machine, each test kills any syslogd first. At the end the system's
syslogd gets restarted.
The test framework runs a client, and a server, and a syslogd. The
messages are passed via the log socket or via UDP from the client
to syslogd. From there UDP transport is used to reach the server.
All processes write log files where the message has to show up.
The test arguments are kept in the args-*.pl files.
The content of a log file, the data sent to a pipe process and what
the server received are checked. The invocation of the sendsyslog(2)
syscall is checked with ktrace, the open file descriptors of syslogd
are checked with fstat.
|
|
|
|
machine, each test kills any syslogd first. At the end the system's
syslogd gets restarted.
The test framework runs a client, and a server, and a syslogd. The
messages are passed via the log socket or via UDP from the client
to syslogd. From there UDP transport is used to reach the server.
All processes write log files where the message has to show up.
The test arguments are kept in the args-*.pl files.
The content of a log file, the data sent to a pipe process and what
the server received are checked. The invocation of the sendsyslog(2)
syscall is checked with ktrace, the open file descriptors of syslogd
are checked with fstat.
|
|
This includes coding style, better error messages and variable
naming.
|
|
do. Also explain the optional environment variables.
|
|
with ony byte content length triggered relayd to hang. This has
been fixed already.
|
|
|
|
to specify an array of md5 hashes in the test arguments and check
all of them in the client and server log files. So test that relayd
does not modify the http body.
|
|
test more strict again. Backout rev 1.2 of args-timeout-http.pl.
|
|
everybody stand back. i know regular expressions.
|
|
ok reyk
|
|
ok reyk
|
|
ok reyk
|
|
ok bluhm@ benno@
|
|
files. We do not want to put a license header into each subtest.
suggested by reyk@
|
|
|
|
common web servers). Add a related regress test.
OK benno@
|
|
one fresh daemon is started with an individual config. It is talking
OSPF via a tun interface. At the process side of the tun device a
client is running. This test programm is parsing the OSPF packets
and generates new ones. It simulates other OSPF daemons.
For now only hello packets are tested. Each test has a task list
which drives the ospfd through its interface state machine. The
plan is to extend the framework for the other OSPF packet types and
state machines. Eventualy the generated kernel routing messages
could also be checked.
I have developed this test suite together with Florian Riehm.
|
