1*1f53c19fSbluhmRun syslogd regressions tests. As only one syslogd can run per 2*1f53c19fSbluhmmachine, each test kills any syslogd first. At the end the system's 3*1f53c19fSbluhmsyslogd gets restarted. 4*1f53c19fSbluhmThe test framework runs a client, and a server, and a syslogd. The 5*1f53c19fSbluhmmessages are passed via the log socket or via UDP from the client 6*1f53c19fSbluhmto syslogd. From there UDP transport is used to reach the server. 7*1f53c19fSbluhmAll processes write log files where the message has to show up. 8*1f53c19fSbluhmThe test arguments are kept in the args-*.pl files. 9*1f53c19fSbluhmThe content of a log file, the data sent to a pipe process and what 10*1f53c19fSbluhmthe server received are checked. The invocation of the sendsyslog(2) 11*1f53c19fSbluhmsyscall is checked with ktrace, the open file descriptors of syslogd 12*1f53c19fSbluhmare checked with fstat. 13*1f53c19fSbluhm 14*1f53c19fSbluhmSUDO=sudo 15*1f53c19fSbluhmAs syslogd needs root privileges either run the tests as root or 16*1f53c19fSbluhmset this variable and run make as a regular user. Only the code 17*1f53c19fSbluhmthat requires it, is run as root. 18*1f53c19fSbluhm 19*1f53c19fSbluhmKTRACE=ktrace 20*1f53c19fSbluhmSet this variable if you want a ktrace output from syslogd. Note that 21*1f53c19fSbluhmktrace is invoked after sudo as sudo would disable it. 22*1f53c19fSbluhm 23*1f53c19fSbluhmSYSLOGD=/usr/src/usr.sbin/syslogd/obj/syslogd 24*1f53c19fSbluhmStart an alternative syslogd program that is not in the path. 25