wireguard-openbsd/regress/usr.sbin/syslogd/args-ttymsg-delay.pl, branch jd/queueboosts WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/regress/usr.sbin/syslogd/args-ttymsg-delay.pl?h=jd%2Fqueueboosts 2016-06-22T19:29:29Z Syslogd can send messages to a user, test what happens if the 2016-06-22T19:29:29Z bluhm bluhm@openbsd.org 2016-06-22T19:29:29Z urn:sha1:2b05856b72008aca43a9cfc136be33ff4579986b 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 a 2015-12-30T13:15:52Z bluhm bluhm@openbsd.org 2015-12-30T13:15:52Z urn:sha1:29e70a6fb22bfd08b1cffac72e37e53ca37b1421 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. Add tests that call the syscalls sendsyslog(2) and sendsyslog2(2) 2015-12-04T13:49:42Z bluhm bluhm@openbsd.org 2015-12-04T13:49:42Z urn:sha1:ef01d180277bb9d2ab1000a61103676542d37a9c directly. Check that syslogd delays a blocking write to tty and that that all 2015-10-23T14:06:55Z bluhm bluhm@openbsd.org 2015-10-23T14:06:55Z urn:sha1:c3c9e5634124c50cfdfc5850596e07efbe564473 messages still appear on the tty.