Lines Matching refs:programs

59 The package provides tiny daemon wrapper programs that can be installed
72 The programs are very portable. Build procedures are provided for many
84 What to do if this is your first encounter with the wrapper programs:
96 The wrapper programs rely on source address information obtained from
111 the wrapper programs, and introduce some of the terminology that is
122 process. A few examples of client and server programs are shown in the
136 The wrapper programs rely on a simple, but powerful mechanism.  Instead
142 The wrapper programs have no interaction with the client user (or with
149 Another important property is that the wrapper programs are active only
160 related software for ways to deal with such server programs.
162 There are two ways to use the wrapper programs:
165    the resulting holes with copies of the wrapper programs.  This
182 For an account of the history of the wrapper programs, with real-life
188 The wrapper programs send their logging information to the syslog
235 When compiled with -DHOSTS_ACCESS, the wrapper programs support a
286 The wrapper programs verify the client host name that is returned by
288 end, the programs look at the name and addresses that are returned by
318 The wrapper programs can give additional protection against hosts that
331 When the wrapper programs are compiled with -DKILL_IP_OPTIONS, the
332 programs refuse to service TCP connections with IP source routing
389 good reason: programs that run at high privilege levels must be easy to
561 (ftp.win.tue.nl:/pub/security/logdaemon-XX.tar.Z).  These programs are
576 much more source code than the daemon wrapper programs. Available
654 not a bug in the wrapper programs: complain to your vendor, and don't
696 copies of the wrapper programs.
741 vendor-provided daemon programs to the location specified by the
967 programs.  The hosts_access.3 manual page (`nroff -man' format)
993 Many people contributed to the evolution of the programs, by asking