Main index | Section 8 | 日本語 | Options |
By default, a request is honored only if the server
(i.e., the host that
rarpd
is running on)
can "boot" the target; that is, a file or directory matching the glob
/tftpboot/ipaddr*
exists, where
ipaddr
is the target IP address in hex.
For example, the IP address 204.216.27.18 will be replied to if any of
/tftpboot/CCD81B12,
/tftpboot/CCD81B12.SUN3,
or
/tftpboot/CCD81B12-boot
exist.
This requirement can be overridden with the
In normal operation, rarpd forks a copy of itself and runs in the background. Anomalies and errors are reported via syslog(3).
The following options are available:
| |
Listen on all the Ethernets attached to the system.
If
| |
| |
If
| |
| |
Run in the foreground. | |
| |
Specify the pathname of the PID file.
If not specified,
/var/run/rarpd.pid
or
/var/run/rarpd.ifname.pid
will be used depending on the
| |
| |
Supply a response to any RARP request for which an ethernet to IP address mapping exists; do not depend on the existence of /tftpboot/ipaddr*. | |
| |
Supply an alternate tftp root directory to
/tftpboot,
similar to the
| |
| |
Enable verbose syslogging. | |
/etc/ethers
/etc/hosts /tftpboot /var/run/rarpd.pid | |
4 p, RFC 903: Reverse Address Resolution Protocol, June 1984.
, , , ,RARPD (8) | July 9, 2012 |
Main index | Section 8 | 日本語 | Options |
Please direct any comments about this manual page service to Ben Bullock. Privacy policy.
“ | A computer would deserve to be called intelligent if it could deceive a human into believing that it was human. | ” |
— Alan Turing |