3 tcpd, tcpdp \- waits for a TCP connection request and starts a server
20 is a daemon, that is, a user-space program that is normally started when the
21 operating system is started and that normally does not terminate until the
23 Conceptually, you can think of
25 as doing nothing but listening to a port for a connection attempt. Several
28 will typically be started, one for each service that is to be provided.
29 When a connection is detected the tcpd for that port
31 and then the child process
33 an instance of the server for that port.
35 The above description is simplified.
36 Normally two versions of the tcpd.c source code are compiled.
38 is the one that waits for a connection. When a connection occurs
43 was started with options or if the child detects that the access
46 exists, the child will
50 which checks that the connection attempt is from an allowed node or network,
51 or that it is not from a disallowed node or network.
53 also tries to look up the name corresponding to an IP address, and denies
54 the connection if a name cannot be found. Finally,
56 determines whether the connection is supposed to be logged.
57 If all is well, the child
63 the server for the service with any arguments specified on the command line
71 allow no more than the specified
81 .B tcpd telnet in.telnetd &
82 # wait for a telnet connection on the normal port
84 .B tcpd 8000 in.httpd /etc/httpd8000.conf &
85 # wait for web page request on port 8000 and use a custom config file for the in.httpd program.
87 Note that command lines must be terminated with "&" to return control to the
88 calling process, leaving the daemon executing as a background process.
90 The above examples show how tcpd might be invoked from /etc/rc or
91 another script that runs during system initialization. You will also
92 see this in the supplied startup scripts:
94 .B daemonize tcpd shell in.rshd
95 # daemonize is a shell function that tests whether a daemon is present and starts it if so, using the & to start it in the background.
97 Another case that should be mentioned is that when a system administrator
98 wants to start (or restart) a daemon from a command line,
100 should be used, like this:
102 .B intr -d tcpd telnet in.telnetd &
103 # remove the daemon from a process group and connect its input to /dev/null and its output to /dev/log.
107 The access control file.
114 That daemons cannot daemonize themselves is a way in which Minix differs from
115 most other Unix-like systems.
117 Allowing access to your system from the net is dangerous. Be sure you
118 know what you are doing. Be sure the owner of your net knows what you are
119 doing. Don't enable services you don't need. Enable logging and look at your
122 None known, let us know...
124 Kees J. Bot <kjb@cs.vu.nl>
126 Man page by Al Woodhull <asw@woodhull.com>