"1f53c19f" (history) in projects: openbsd

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched hist:"1 f53c19f" (Results 1 – 15 of 15) sorted by relevance

/openbsd/regress/usr.sbin/syslogd/
H A D	args-client-udp4-nodns.pl	1f53c19f Wed Aug 20 20:52:14 GMT 2014 bluhm <bluhm@openbsd.org> Run syslogd regressions tests. As only one syslogd can run per 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.
H A D	args-client-udp-nodns.pl	1f53c19f Wed Aug 20 20:52:14 GMT 2014 bluhm <bluhm@openbsd.org> Run syslogd regressions tests. As only one syslogd can run per 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.
H A D	args-client-udp4.pl	1f53c19f Wed Aug 20 20:52:14 GMT 2014 bluhm <bluhm@openbsd.org> Run syslogd regressions tests. As only one syslogd can run per 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.
H A D	args-socket.pl	1f53c19f Wed Aug 20 20:52:14 GMT 2014 bluhm <bluhm@openbsd.org> Run syslogd regressions tests. As only one syslogd can run per 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.
H A D	args-default.pl	1f53c19f Wed Aug 20 20:52:14 GMT 2014 bluhm <bluhm@openbsd.org> Run syslogd regressions tests. As only one syslogd can run per 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.
H A D	LICENSE	1f53c19f Wed Aug 20 20:52:14 GMT 2014 bluhm <bluhm@openbsd.org> Run syslogd regressions tests. As only one syslogd can run per 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.
H A D	args-client-udp.pl	1f53c19f Wed Aug 20 20:52:14 GMT 2014 bluhm <bluhm@openbsd.org> Run syslogd regressions tests. As only one syslogd can run per 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.
H A D	README	1f53c19f Wed Aug 20 20:52:14 GMT 2014 bluhm <bluhm@openbsd.org> Run syslogd regressions tests. As only one syslogd can run per 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.
H A D	Proc.pm	1f53c19f Wed Aug 20 20:52:14 GMT 2014 bluhm <bluhm@openbsd.org> Run syslogd regressions tests. As only one syslogd can run per 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.
H A D	syslogd.pl	1f53c19f Wed Aug 20 20:52:14 GMT 2014 bluhm <bluhm@openbsd.org> Run syslogd regressions tests. As only one syslogd can run per 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.
H A D	Server.pm	1f53c19f Wed Aug 20 20:52:14 GMT 2014 bluhm <bluhm@openbsd.org> Run syslogd regressions tests. As only one syslogd can run per 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.
H A D	Client.pm	1f53c19f Wed Aug 20 20:52:14 GMT 2014 bluhm <bluhm@openbsd.org> Run syslogd regressions tests. As only one syslogd can run per 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.
H A D	Syslogd.pm	1f53c19f Wed Aug 20 20:52:14 GMT 2014 bluhm <bluhm@openbsd.org> Run syslogd regressions tests. As only one syslogd can run per 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.
H A D	Makefile	1f53c19f Wed Aug 20 20:52:14 GMT 2014 bluhm <bluhm@openbsd.org> Run syslogd regressions tests. As only one syslogd can run per 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.
H A D	funcs.pl	1f53c19f Wed Aug 20 20:52:14 GMT 2014 bluhm <bluhm@openbsd.org> Run syslogd regressions tests. As only one syslogd can run per 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.