projects / unix-history / blame
| Commit | Line | Data |
|---|---|---|
| 4ee2fd4d KM |
1 | .\" Copyright (c) 1983 Regents of the University of California. |
| 2 | .\" All rights reserved. The Berkeley software License Agreement | |
| 3 | .\" specifies the terms and conditions for redistribution. | |
| 4 | .\" | |
| 5 | .\" @(#)htable.8 5.1 (Berkeley) %G% | |
| 6 | .\" | |
| 7 | .TH HTABLE 8 "4 March 1983" | |
| 8 | .UC 5 | |
| 9 | .SH NAME | |
| 10 | htable \- convert NIC standard format host tables | |
| 11 | .SH SYNOPSIS | |
| 12 | .B /etc/htable | |
| 13 | [ | |
| 14 | .B \-c | |
| 15 | .I connected-nets | |
| 16 | ] [ | |
| 17 | .B \-l | |
| 18 | .I local-nets | |
| 19 | ] | |
| 20 | .I file | |
| 21 | .SH DESCRIPTION | |
| 22 | .I Htable | |
| 23 | is used to convert host files in the format specified | |
| 24 | in Internet RFC 810 to the format used by the network | |
| 25 | library routines. Three files are created as a result | |
| 26 | of running | |
| 27 | .IR htable : | |
| 28 | .IR hosts , | |
| 29 | .IR networks , | |
| 30 | and | |
| 31 | .IR gateways . | |
| 32 | The | |
| 33 | .I hosts | |
| 34 | file is used by the | |
| 35 | .IR gethostent (3N) | |
| 36 | routines in mapping host names to addresses. | |
| 37 | The | |
| 38 | .I networks | |
| 39 | file is used by the | |
| 40 | .IR getnetent (3N) | |
| 41 | routines in mapping network names to numbers. | |
| 42 | The | |
| 43 | .I gateways | |
| 44 | file is used by the routing daemon | |
| 45 | in identifying ``passive'' Internet gateways; | |
| 46 | see | |
| 47 | .IR routed (8C) | |
| 48 | for an explanation. | |
| 49 | .PP | |
| 50 | If any of the files | |
| 51 | .IR localhosts , | |
| 52 | .IR localnetworks , | |
| 53 | or | |
| 54 | .I localgateways | |
| 55 | are present in the current directory, | |
| 56 | the file's contents is prepended to the | |
| 57 | output file. | |
| 58 | Of these, only the gateways file is interpreted. | |
| 59 | This allows sites to maintain local aliases and | |
| 60 | entries which are not normally present in the | |
| 61 | master database. | |
| 62 | Only one gateway to each network will be placed in the gateways file; | |
| 63 | a gateway listed in the localgateways file will override any in the | |
| 64 | input file. | |
| 65 | .PP | |
| 66 | A list of networks to which the host is directly connected is specified with the | |
| 67 | .B \-c | |
| 68 | flag. | |
| 69 | The networks, separated by commas, | |
| 70 | may be given by name or in internet-standard dot notation, | |
| 71 | e.g. | |
| 72 | .B \-c | |
| 73 | arpanet,128.32,local-ether-net. | |
| 74 | .I Htable | |
| 75 | only includes gateways | |
| 76 | which are directly connected to one of the networks specified, | |
| 77 | or which can be reached from another gateway on a connected net. | |
| 78 | .PP | |
| 79 | If the | |
| 80 | .B \-l | |
| 81 | option is given with a list of networks (in the same format as for | |
| 82 | .BR \-c ), | |
| 83 | these networks will be treated as ``local,'' | |
| 84 | and information about hosts on local networks is | |
| 85 | taken only from the localhosts file. | |
| 86 | Entries for local hosts from the main database will be omitted. | |
| 87 | This allows the localhosts file to completely override | |
| 88 | any entries in the input file. | |
| 89 | .PP | |
| 90 | .I Htable | |
| 91 | is best used in conjunction with the | |
| 92 | .IR gettable (8C) | |
| 93 | program which retrieves the NIC database from a host. | |
| 94 | .SH "SEE ALSO" | |
| 95 | intro(3N), | |
| 96 | gettable(8C) |