Lines Matching refs:wrapper
3 This is the 7.6 version of the TCP/IP daemon wrapper package.
39 6.1 - Known wrapper limitations
59 The package provides tiny daemon wrapper programs that can be installed
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
136 The wrapper programs rely on a simple, but powerful mechanism. Instead
138 into running a small wrapper program. The wrapper logs the client host
140 the wrapper executes the desired server program and goes away.
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
151 a wrapper has done its work there is no overhead on the client-server
162 There are two ways to use the wrapper programs:
165 the resulting holes with copies of the wrapper programs. This
174 When a tftp request arrives, inetd will run the wrapper program
176 wrapper will use when logging the request and when scanning the
178 server program that the wrapper will attempt to run when all is
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
189 daemon (syslogd). The disposition of the wrapper logs is determined by
216 By default, the wrapper logs go to the same place as the transaction
235 When compiled with -DHOSTS_ACCESS, the wrapper programs support a
266 When the wrapper discovers that the TLI interface sits on top of a
286 The wrapper programs verify the client host name that is 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
429 With the wrapper software, `daemon@host' access control patterns can be
450 The wrapper software provides easy-to-use tools to generate pre-login
501 The war story behind the tcp wrapper tools is described in:
576 much more source code than the daemon wrapper programs. Available
606 6.1 - Known wrapper limitations
648 wrapper's logging severity.
654 not a bug in the wrapper programs: complain to your vendor, and don't
696 copies of the wrapper programs.
698 If you don't run Ultrix, you won't need the miscd wrapper program. The
712 in your wrapper and inetd configuration files.
714 With the `tcpdmatch' program you can examine how the wrapper would
755 File protections: the wrapper, all files used by the wrapper, and all
758 install the wrapper set-uid.
762 REAL_DAEMON_DIR macro in the Makefile, and install the miscd wrapper
784 in your wrapper and inetd configuration files.
786 With the `tcpdmatch' program you can examine how the wrapper would
816 File protections: the wrapper, all files used by the wrapper, and all
819 install the wrapper set-uid.
850 you want to monitor the systat service, install the miscd wrapper in a
945 This entry causes the inetd to run the wrapper program (tcpd) with a
946 process name `in.tftpd'. This is the name that the wrapper will use
960 simulate what happens when the wrapper is unable to look up the client