1# Command line options passed to syslogd generate errors.
2# The client writes a message to Sys::Syslog native method.
3# The syslogd writes it into a file and through a pipe and to tty.
4# The syslogd passes it via UDP to the loghost.
5# The server receives the message on its UDP socket.
6# Find the message in client, file, pipe, console, user, syslogd, server log.
7# Check that syslogd runs despite of errors.
8# Check that startup errors are logged to stderr.
9
10use strict;
11use warnings;
12
13our %args = (
14    syslogd => {
15	cacrt => "default",
16	options => [qw(
17	    -U 127.188.42.23 -U [::ffff:127.188.0.0] -U 127.0.0.1:70000
18	    -T 127.188.42.23:514 -T [::ffff:127.188.0.0]:514 -T 127.0.0.1:70000
19	    -S [::1]:70000
20	    -C CCCC -c cccc -K KKKK -k kkkk
21	    ), '-a', 'A'x1000, '-p', 'P'x1000, '-s', 'S'x1000
22	],
23	loggrep => {
24	    qr/address 127.188.42.23/ => 2,
25	    qr/address ::ffff:127.188.0.0/ => 2,
26	    qr/port 70000/ => 3,
27	    qr/socket bind udp/ => 3,
28	    qr/socket listen tcp/ => 3,
29	    qr/socket listen tls/ => 1,
30	    qr/CA file 'CCCC'/ => 1,
31	    qr/certificate file 'cccc'/ => 1,
32	    qr/CA file 'KKKK'/ => 1,
33	    qr/key file 'kkkk'/ => 1,
34	    qr/socket path too long "AAAA/ => 1,
35	    qr/socket path too long "PPPP/ => 1,
36	    qr/socket path too long "SSSS/ => 1,
37	    qr/log socket PPPP/ => 1,
38	}
39    },
40);
41
421;
43