summaryrefslogtreecommitdiff
path: root/regress/usr.sbin
AgeCommit message (Collapse)Author
2014-12-14By now relayd expects tls in its config file and writes tls intoAlexander Bluhm
its log file. Change regression tests form ssl to tls.
2014-11-25Fix test.Daniel Dickman
ok bluhm@
2014-11-20fix things post signature, as noticed by various peopleMarc Espie
2014-10-29Add a test the checks the syslogd !prog !!prog !* feature.Alexander Bluhm
2014-10-05Test that the specified libevent backend kqueue(2) or poll(2) orAlexander Bluhm
select(2) is used by syslogd.
2014-10-03Add a test that checks that there are no trailing new-lines orAlexander Bluhm
spaces in the syslog messages.
2014-09-20texlive blasts thru the 999 chunks barrierMarc Espie
2014-09-20a small debug script to extract chunks from a chunked archive, as it isMarc Espie
very difficult to do so with standard tools
2014-09-13Add tests for syslogd's memory buffer and read it with syslogc.Alexander Bluhm
2014-09-04Check that messages from sendsyslog(2) or unix domain sockets containAlexander Bluhm
the short host name.
2014-09-03Add tests that send log messages via unix domain sockets to syslogd.Alexander Bluhm
Also check that the maximum number of -a path is handled correctly.
2014-09-02To examine the operation of the signal handlers, the tests grep inAlexander Bluhm
the ktrace output of syslogd. Also make the tests work without DNS and without sudo.
2014-09-02Add tests that run the syslogd signal handlers.Alexander Bluhm
2014-08-20Run syslogd regressions tests. As only one syslogd can run perAlexander Bluhm
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.
2014-08-29Make the syslogd regression tests more reliable. Other processesAlexander Bluhm
on the system may create log entries during the test run that show up in the log file. Ignore those additional lines.
2014-08-29Prepare for testing libevent in syslogd. Pass the EVENT_NO...Alexander Bluhm
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.
2014-08-20Run syslogd regressions tests. As only one syslogd can run perAlexander Bluhm
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.
2014-08-27Remove $_ usage that warns under Perl 5.18.Kent R. Spillner
Yep espie@
2014-08-26Update regress to follow openssl(1) move.Joel Sing
2014-08-25Add tests where the IP address family has been chosen by -4 or -6Alexander Bluhm
command line switch and udp4:// or udp6:// loghost prefix.
2014-08-25Add tests for syslogd sending and receiving over IPv6 sockets.Alexander Bluhm
2014-08-20Run syslogd regressions tests. As only one syslogd can run perAlexander Bluhm
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.
2014-08-20Link ospfd and syslogd regression tests to the build.Alexander Bluhm
2014-08-20Run syslogd regressions tests. As only one syslogd can run perAlexander Bluhm
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.
2014-08-18Make the perl modules consistent for the multiple regression tests.Alexander Bluhm
This includes coding style, better error messages and variable naming.
2014-08-18Add a description of what the relayd and sosplice regression testsAlexander Bluhm
do. Also explain the optional environment variables.
2014-08-18Add test cases for multiple small HTTP requests. Many PUT requestsAlexander Bluhm
with ony byte content length triggered relayd to hang. This has been fixed already.
2014-08-17Sync regress/usr.sbin/relayd with recent http.h changesdoug
2014-07-20A HTTP connection may have multiple requests with content. AllowAlexander Bluhm
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.
2014-07-14Now that the relayd timeouts have been fixed, make the http timeoutAlexander Bluhm
test more strict again. Backout rev 1.2 of args-timeout-http.pl.
2014-07-13fix regress tests after log changes. noticed by bluhm@.Sebastian Benoit
everybody stand back. i know regular expressions.
2014-07-13improve log output for relays. adjust regress testsSebastian Benoit
ok reyk
2014-07-13repair matching of headers, add regress test for this errorSebastian Benoit
ok reyk
2014-07-12fix relay "append header" action, add regression test for appendSebastian Benoit
ok reyk
2014-07-12Test filtering by methodReyk Floeter
ok bluhm@ benno@
2014-07-11Put a license file into the test directories with multiple argumentAlexander Bluhm
files. We do not want to put a license header into each subtest. suggested by reyk@
2014-07-11Add OpenBSD RCS id.Alexander Bluhm
2014-07-11Limit HTTP header length to about 8K (based on the default of 4-8K inReyk Floeter
common web servers). Add a related regress test. OK benno@
2014-07-11Add a test framework for the ospfd routing daemon. For each testAlexander Bluhm
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.
2014-07-11Make the test output easier to read by splitting the test casesAlexander Bluhm
with an empty line and a header line.
2014-07-11Fix dryrun for remote relayd test.Alexander Bluhm
2014-07-11Add a time.log file that accumulates timing information about theAlexander Bluhm
executed tests. This allows to micro benchmark relayd. based on a diff from andre@; OK reyk@
2014-07-11Simplify the code that handles the HTTP headers by using an RB treeReyk Floeter
with associated lists instead of the complicated lookup table and "others" list. This might add a little malloc overhead for common headers but also fixes some issues like the handling of repeated headers - for example, handling of multiple "Set-Cookie" headers. ok bluhm@ (regress part) ok benno@
2014-07-10Test relayd error message for a broken config file.Alexander Bluhm
2014-07-10Check for the exact number of done requests in relayd log.Alexander Bluhm
2014-07-10Print "%s (removed)" into relayd log and test for that string.Alexander Bluhm
suggested by reyk@
2014-07-10To make sure that at least anything is tested, add a length checkAlexander Bluhm
per default for the default length value in check_logs(). If a test doesn't want this check, it has to disable it explicitly with nocheck. Also remove unneeded nocheck switches for deeper testing.
2014-07-10Add support to test handling of repeated headers.Reyk Floeter
From RFC 7230, section 3.2.2: "A sender MUST NOT generate multiple header fields with the same field name in a message unless either the entire field value for that header field is defined as a comma-separated list [i.e., #(values)] or the header field is a well-known exception (as noted below)."
2014-07-10Implement non-persistent connections in a cleaner way. Every testAlexander Bluhm
that offers multiple requets per HTTP connection is run twice. First all requests are run over a single TCP connection. Then for each requests a separate TCP connection is established. If a requests during a persistent connection fails, a reconnect is done as relayd cancels the whole connection. This allows stricter tests for filters. OK reyk@
2014-07-09Changes in relayd's regression tests have to be discussed.Reyk Floeter
As discussed with bluhm@ deraadt@