11622 clean up rarer mandoc lint warnings

          --- old/usr/src/man/man1/whois.1
          +++ new/usr/src/man/man1/whois.1
   1    1  .TH WHOIS 1 "Oct 2, 2009"
   2    2  .SH NAME
   3    3  \fBwhois\fP
   4    4  \- Internet domain name and network number directory service
   5    5  .SH SYNOPSIS
   6      -.br
   7    6  \fBwhois\fP
   8    7  [\fB\-aAbfgiIklmQr\fP]
   9    8  [\fB\-c\fP \fIcountry-code\fP | \fIFl\fP h \fIhost\fP]
  10    9  [\fB\-p\fP \fIport\fP]
  11   10  \fIname\fP...
  12   11  .SH DESCRIPTION
  13   12  The
  14   13  \fBwhois\fP
  15   14  utility looks up records in the databases maintained by several
  16   15  Network Information Centers (NICs).

  17   16  
  18   17  The options are as follows:
  19   18  .TP
  20   19  \fB\-a\fP
  21   20  Use the American Registry for Internet Numbers (ARIN) database.
  22   21  It contains network numbers used in those parts of the world covered neither by
  23   22  APNIC, AfriNIC, LACNIC, nor by RIPE.
  24   23  
  25   24  (Hint: All point of contact handles in the ARIN whois database end with -ARIN.)
  26   25  
  27   26  .TP
  28   27  \fB\-A\fP
  29   28  Use the Asia/Pacific Network Information Center (APNIC) database.
  30   29  It contains network numbers used in East Asia, Australia,
  31   30  New Zealand, and the Pacific islands.
  32   31  .TP
  33   32  \fB\-b\fP
  34   33  Use the Network Abuse Clearinghouse database.
  35   34  It contains addresses to which network abuse should be reported,
  36   35  indexed by domain name.
  37   36  .TP
  38   37  \fB\-c\fP \fIcountry-code\fP
  39   38  This is the equivalent of using the
  40   39  \fB\-h\fP
  41   40  option with an argument of \fIcountry-code\fP.whois-servers.net.
  42   41  .TP
  43   42  \fB\-f\fP
  44   43  Use the African Network Information Centre (AfriNIC) database.
  45   44  It contains network numbers used in Africa and the islands of the
  46   45  western Indian Ocean.
  47   46  .TP
  48   47  \fB\-g\fP
  49   48  Use the US non-military federal government database, which contains points of
  50   49  contact for subdomains of
  51   50  \fI\&.GOV\fP.
  52   51  .TP
  53   52  \fB\-h\fP \fIhost\fP
  54   53  Use the specified host instead of the default variant.
  55   54  Either a host name or an IP address may be specified.
  56   55  
  57   56  By default
  58   57  \fBwhois\fP
  59   58  constructs the name of a whois server to use from the top-level domain (TLD)
  60   59  of the supplied (single) argument, and appending .whois-servers.net .
  61   60  This effectively allows a suitable whois server to be selected
  62   61  automatically for a large number of TLDs.
  63   62  
  64   63  In the event that an IP
  65   64  address is specified, the whois server will default to the American
  66   65  Registry for Internet Numbers (ARIN).
  67   66  If a query to ARIN references APNIC, AfriNIC, LACNIC, or RIPE,
  68   67  that server will be queried also, provided that the
  69   68  \fB\-Q\fP
  70   69  option is not specified.
  71   70  
  72   71  If the query is not a domain name or IP address,
  73   72  \fBwhois\fP
  74   73  will fall back to
  75   74  \fIwhois.crsnic.net\fP.
  76   75  .TP
  77   76  \fB\-i\fP
  78   77  Use the Network Solutions Registry for Internet Numbers
  79   78  (\fIwhois.networksolutions.com\fP)
  80   79  database.
  81   80  It contains network numbers and domain contact information for most of
  82   81  \fI\&.COM\fP,.NET,.ORG
  83   82  and
  84   83  \fI\&.EDU\fP
  85   84  domains.
  86   85  
  87   86  .B NOTE !
  88   87  The registration of these domains is now done by a number of
  89   88  independent and competing registrars and this database holds no information
  90   89  on the domains registered by organizations other than Network Solutions, Inc.
  91   90  Also, note that the InterNIC database
  92   91  (\fIwhois.internic.net\fP)
  93   92  is no longer handled by Network Solutions, Inc.
  94   93  For details, see
  95   94  \fIhttp://www.internic.net/\fP.
  96   95  
  97   96  (Hint: Contact information, identified by the term
  98   97  .IR handle ,
  99   98  can be looked up by prefixing "handle" to the NIC
 100   99  handle in the query.)
 101  100  .TP
 102  101  \fB\-I\fP
 103  102  Use the Internet Assigned Numbers Authority (IANA) database.
 104  103  It contains network information for top-level domains.
 105  104  .TP
 106  105  \fB\-k\fP
 107  106  Use the National Internet Development Agency of Korea's (KRNIC)
 108  107  database.
 109  108  It contains network numbers and domain contact information
 110  109  for Korea.
 111  110  .TP
 112  111  \fB\-l\fP
 113  112  Use the Latin American and Caribbean IP address Regional Registry
 114  113  (Tn LACNIC)
 115  114  database.
 116  115  It contains network numbers used in much of Latin America and the
 117  116  Caribbean.
 118  117  .TP
 119  118  \fB\-m\fP
 120  119  Use the Route Arbiter Database (RADB) database.
 121  120  It contains route policy specifications for a large
 122  121  number of operators' networks.
 123  122  .TP
 124  123  \fB\-p\fP \fIport\fP
 125  124  Connect to the whois server on
 126  125  \fIport\fP.
 127  126  If this option is not specified,
 128  127  \fBwhois\fP
 129  128  defaults to port 43.
 130  129  .TP
 131  130  \fB\-Q\fP
 132  131  Do a quick lookup.
 133  132  This means that
 134  133  \fBwhois\fP
 135  134  will not attempt to lookup the name in the authoritative whois
 136  135  server (if one is listed).
 137  136  This option has no effect when combined with any other options.
 138  137  .TP
 139  138  \fB\-r\fP
 140  139  Use the R\(aaeseaux IP Europ\(aaeens (RIPE) database.
 141  140  It contains network numbers and domain contact information
 142  141  for Europe.
 143  142  
 144  143  The operands specified to
 145  144  \fBwhois\fP
 146  145  are treated independently and may be used
 147  146  as queries on different whois servers.
 148  147  .SH EXIT STATUS
 149  148  The \fBwhois\fP utility exits 0 on success, and >0 if an error occurs.
 150  149  .SH EXAMPLES
 151  150  Most types of data, such as domain names and IP addresses, can be used as
 152  151  arguments to
 153  152  \fBwhois\fP
 154  153  without any options, and
 155  154  \fBwhois\fP
 156  155  will choose the correct whois server to query.
 157  156  Some exceptions, where
 158  157  \fBwhois\fP
 159  158  will not be able to handle data correctly, are detailed below.
 160  159  
 161  160  To obtain contact information about an
 162  161  administrator located in the Russian TLD domain RU,
 163  162  use the
 164  163  \fB\-c\fP
 165  164  option as shown in the following example, where
 166  165  \fICONTACT-ID\fP
 167  166  is substituted with the actual contact identifier.
 168  167  
 169  168  whois -c RU CONTACT-ID
 170  169  
 171  170  (Note: This example is specific to the TLD RU,
 172  171  but other TLDs can be queried by using a similar syntax.)
 173  172  
 174  173  The following example demonstrates how to query
 175  174  a whois server using a non-standard port, where
 176  175  ``query-data''
 177  176  is the query to be sent to
 178  177  ``whois.example.com''
 179  178  on port
 180  179  ``rwhois''
 181  180  (written numerically as 4321).
 182  181  
 183  182  whois -h whois.example.com -p rwhois query-data
 184  183  .SH SEE ALSO
 185  184  
 186  185  Vic White and Ken Harrenstien, \fINICNAME/WHOIS\fP, 1 March 1982, RFC 812.
 187  186  .SH HISTORY
 188  187  The
 189  188  \fBwhois\fP
 190  189  command appeared in
 191  190  4.3BSD.

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX