wireguard-openbsd/regress/usr.sbin/syslogd/args-socket.pl, branch jd/queueboosts WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/regress/usr.sbin/syslogd/args-socket.pl?h=jd%2Fqueueboosts 2017-09-12T15:24:21Z Syslogd does no longer keep the *:514 UDP sockets open by default. 2017-09-12T15:24:21Z bluhm bluhm@openbsd.org 2017-09-12T15:24:21Z urn:sha1:e2a49d81efc03038e49f6939fc70d1ab81c05e2c Adapt tests. Rework how fstat and ktrace pattern are specified in the test 2015-06-15T21:44:57Z bluhm bluhm@openbsd.org 2015-06-15T21:44:57Z urn:sha1:f48a84a70c8ced255fc68039eca171a1ec9c86b2 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. Add tests that run the syslogd signal handlers. 2014-09-02T00:26:30Z bluhm bluhm@openbsd.org 2014-09-02T00:26:30Z urn:sha1:723ac965d6c057b2685852c361a3c2632c5214cb Add tests for syslogd sending and receiving over IPv6 sockets. 2014-08-25T17:55:27Z bluhm bluhm@openbsd.org 2014-08-25T17:55:27Z urn:sha1:73e391cd52522500bfc8225b1450535e6af4298d Run syslogd regressions tests. As only one syslogd can run per 2014-08-20T20:52:14Z bluhm bluhm@openbsd.org 2014-08-20T20:52:14Z urn:sha1:1f53c19fe11027baaa79c8fdd5154bbd2e2d526f 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.