summaryrefslogtreecommitdiffstats
path: root/regress/usr.sbin/syslogd/Syslogd.pm (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Kernel drops fewer messages in sendsyslog(2), adapt syslogd(8)bluhm2021-03-091-1/+7
| | | | | tests. Kernel stashes logs temporarily, test it. Fix some races in existing tests.
* If KTRACE environment is set, generate ktrace output also for clientbluhm2020-07-241-5/+7
| | | | and server. Together with the syslogd ktrace this helps debugging.
* Fix more races in syslogd test.bluhm2019-09-101-15/+18
|
* Fix a race in the syslogd test. It did not wait long enough forbluhm2018-04-111-6/+6
| | | | syslogd to shutdown. So the test could miss some log messages.
* Test that the syslogd program can be started with a relative path.bluhm2016-12-271-3/+8
|
* To test the pipe feature, a dd is started and writing into a logbluhm2016-11-281-4/+22
| | | | | | file as user _syslogd. Since /usr/obj is 0770 now, user _syslogd cannot access this file there anymore. Create pipe.log in temporary directory in /tmp instead.
* Fix races during syslogd startup and shutdown in privsep tests.bluhm2016-10-121-5/+28
|
* Allow to run the syslogd tests as root without SUDO also if thebluhm2016-07-121-2/+2
| | | | libevent method environment is set.
* Syslogd can send messages to a user, test what happens if thebluhm2016-06-221-2/+20
| | | | | | terminal is blocking to receive messages. Stop the fake user terminal and look for a delayed write debug message from syslogd. This makes the test more reliable.
* Test logging to console by redirecting the system's console into abluhm2015-12-301-20/+30
| | | | | | | file. All subtests get an additional /dev/console entry in syslog.conf, then check that messages appear in the console file. Add a test that stops syslogd, calls sendsyslog2() with LOG_CONS and checks that the message appears in the console file.
* Test syslogd logging to a tty which belongs to a user. This isbluhm2015-10-191-1/+25
| | | | | done with a utmp entry for a pty fake login. All messages are read from the pty and written into a log file.
* Do not inherit the event environment, delete and set explicitlybluhm2015-08-251-2/+2
| | | | after sudo.
* Allow to use $curdir, $objdir, $host, $hostname in the test configbluhm2015-07-201-8/+13
| | | | | file. They are substituted automatically, to avoid this in each single test.
* Kill a possibly running syslogd with -9 before testing.bluhm2015-07-161-2/+2
|
* Rework how fstat and ktrace pattern are specified in the testbluhm2015-06-151-6/+27
| | | | | | | arguments. Add tests to check wether syslogd privsep works. This is done for debug and foreground and daemon mode. Fstat is checked for chroot and sockets. Ktrace dump is grepped for setting uid and gid.
* Adapt the maxunix test, the syslogd -a error semantic has changed.bluhm2015-02-131-1/+2
| | | | | Increase timeouts and remove races, so that the syslogd tests pass on my sparc64 machine.
* Test the x509 certificate validation of syslog over TLS.bluhm2015-01-281-1/+4
|
* Make syslogd tests more reliable on slow machines. All tests passbluhm2015-01-221-2/+2
| | | | on my old sparc64.
* Test that syslogd sending over TCP does not leak a file descriptorbluhm2015-01-011-13/+19
| | | | when it receives a SIGHUP.
* Add regression tests where OpenBSD syslogd is sending messages tobluhm2014-12-281-2/+2
| | | | | | 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.
* Add a test the checks the syslogd !prog !!prog !* feature.bluhm2014-10-291-1/+2
|
* Add tests for syslogd's memory buffer and read it with syslogc.bluhm2014-09-131-6/+12
|
* To examine the operation of the signal handlers, the tests grep inbluhm2014-09-021-1/+6
| | | | | the ktrace output of syslogd. Also make the tests work without DNS and without sudo.
* Add tests that run the syslogd signal handlers.bluhm2014-09-021-2/+61
|
* Prepare for testing libevent in syslogd. Pass the EVENT_NO...bluhm2014-08-291-2/+8
| | | | | | 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.
* Run syslogd regressions tests. As only one syslogd can run perbluhm2014-08-201-0/+128
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.
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.