19f5e6548Sbluhm# Test UDP with rsyslogd as sender. 29f5e6548Sbluhm# The client writes a message to rsyslogd UDP socket. 39f5e6548Sbluhm# The rsyslogd forwards the message to syslogd UDP bind socket. 49f5e6548Sbluhm# The syslogd writes it into a file and through a pipe. 59f5e6548Sbluhm# The syslogd passes it via UDP to the rsyslogd. 69f5e6548Sbluhm# The rsyslogd receives the message on its UDP socket. 79f5e6548Sbluhm# Find the message in rsyslogd, file, pipe, syslogd, server log. 89f5e6548Sbluhm# Check that the message is in rsyslogd, syslogd, server log. 99f5e6548Sbluhm 109f5e6548Sbluhmuse strict; 119f5e6548Sbluhmuse warnings; 12eab741e3Sbluhmuse Socket; 139f5e6548Sbluhm 149f5e6548Sbluhmour %args = ( 159f5e6548Sbluhm client => { 169f5e6548Sbluhm connect => { domain => AF_INET, proto => "udp", addr => "127.0.0.1" }, 179f5e6548Sbluhm }, 189f5e6548Sbluhm rsyslogd => { 199f5e6548Sbluhm listen => { domain => AF_INET, proto => "udp", addr => "127.0.0.1" }, 209f5e6548Sbluhm connect => { domain => AF_INET, proto => "udp", addr => "127.0.0.1", 219f5e6548Sbluhm port => 514 }, 22*e0736e0cSbluhm loggrep => { 23*e0736e0cSbluhm qr/omfile.* /.get_testgrep() => 1, 24*e0736e0cSbluhm }, 259f5e6548Sbluhm }, 269f5e6548Sbluhm syslogd => { 279f5e6548Sbluhm options => ["-U", "127.0.0.1:514"], 289f5e6548Sbluhm }, 299f5e6548Sbluhm); 309f5e6548Sbluhm 319f5e6548Sbluhm1; 32