1 .\" Copyright (c) 1993 The University of Adelaide.
2 .\" All rights reserved.
4 .\" Redistribution and use in source and binary forms are permitted
5 .\" provided that the above copyright notice and this paragraph are
6 .\" duplicated in all such forms and that any documentation,
7 .\" advertising materials, and other materials related to such
8 .\" distribution and use acknowledge that the software was developed
9 .\" by the University of Adelaide. The name of the University may not
10 .\" be used to endorse or promote products derived from this software
11 .\" without specific prior written permission.
12 .\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
13 .\" IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
14 .\" WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.
16 .\" @(#)whois++d.man 1.5
18 .TH WHOIS++D 8 "26 April 1993"
20 whois++d \- Whois++ white pages server
55 is an implementation of the new whois++ white pages server. The server is in
56 reality a DUA interface that uses the lightweight directory access protocol
57 [RFC????] to communicate with an X.500 Directory System Agent (DSA) via a
59 server. The whois++ architecture (and command format) is described in an
60 Internet Draft of the IETF's WNILS Working Group.
64 reads it's configuration information from a tailor file (whois++dtailor)
67 but this may be supplemented by command line options, including the
68 specification of a secondary tailor file.
73 Specify the base for all queries, this must be specified either via the
74 commandline or (more normally) via the tailor file.
77 Print debugging information.
78 A number after the ``d'' determines the level of messages printed.
81 Specify the host running the
86 If the entry for the ``base'' of the searches has an info attribute then
87 print it as part of the welcome banner.
90 Enable logging of queries via syslog.
93 Specify the maximum number of entries you wish returned as a result of a
94 search. This is normally controlled by the DSA but if this is not possible
95 then it can be restricted via this option.
98 Specify a timelimit for queries to the DSA. Note this is
100 the timeout limit between queries when using the
105 Specify an additional tailor file. Useful if you only have a binary and the
106 default location is not what you consider to be a ``normal'' place.
109 Specify the user's DN to use when binding to the directory.
112 Return the version number of this server and then exit.
115 Print a list of valid commandline options and then exit.
116 .SH "CONFIGURATION FILE"
119 reads it's configuration file before processing any command line options.
120 The configuration commands that may be included in this tailor file are
122 Specify a file to display as a welcome message.
124 This specifies the entry within the DIT where searches will commence. This is
125 normally set to the organisation's entry.
127 Identifies where the configuration files may be found, currently only used
128 for the template descriptions.
130 This is the distinguished name of the person responsible for this service, and
131 whose entry will be displayed if the client uses the `describe' query. If this
132 is not defined in the configuration file it defaults to the DSA manager.
134 This directory contains the multi-lingual help files. There should be a
135 subdirectory for each language supported and within these subdirectories
136 are helpfiles that are displayed by the server. At a minimum there should be
137 an english directory containing a `general' helpfile (which contains
138 introductory information).
140 Used when the server is queried using the `describe' command. If not specified
141 it will default to the local hostname.
143 Specify the default language to be used when producing diagnostic messages.
145 This specifies the host running a ldap server which can be used to communicate
148 The password to use then binding to the X.500 DSA.
150 The whois++ template name is not always the same as the X.500 object class
151 so this option allows the two values to be associated with each other. The
152 two values are template-name and objectclass-name.
154 The LDAP distinguished name of the user to use when binding to the directory.
155 This is optional but the DSA may restrict the information available to the
156 whois++ server unless it authenticates itself.
158 Multi-lingual support is not available yet.
160 ETCDIR/whois++dtailor whois++ server tailor file