| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
and server. Together with the syslogd ktrace this helps debugging.
|
|
|
|
| |
declared in conditional statement.
|
|
|
|
| |
log files in syslog.conf and must close and reopen them at SIGHUP.
|
|
|
|
|
| |
Increase timeouts and remove races, so that the syslogd tests pass
on my sparc64 machine.
|
| |
|
|
|
|
| |
when it receives a SIGHUP.
|
| |
|
| |
|
|
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.
|