| Age | Commit message (Collapse) | Author |
|---|
|
tests are depending less on the timing. Fix a race in the buffer
sync test. Now make regress of syslogd passes on my amd64, i386,
sparc64, alpha machines.
|
|
counter. Adapt tests.
|
|
|
|
Increase timeouts and remove races, so that the syslogd tests pass
on my sparc64 machine.
|
|
lost log messages. Improve the synchronisation of client and server.
|
|
messages, in case some got lost. Slow down client when sending
multiple log messages. Sort patterns when checking log files. TLS
error messages have changed, adapt tests.
|
|
seconds in the write_lines() loop. This slows down the client, so
all messages reach syslogd and flood its buffers. Increase the
timeout to wait until all buffers are full. Use this code in all
TCP/TLS buffer and memory overflow tests.
|
|
|
|
Add tests for truncated buffer handling.
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
