1 I assume that you have already obtained the LDAP libraries and installed
2 them in the appropriate place. This kit should fit into the directory
3 structure created by LDAP. You should use the root.Makefile.diffs file to
4 patch the LDAP Makefile so that it knows how to build whois++. This may fail
5 depending on what version of LDAP you have but the rejections should be
6 trival to fix (hopefully UMich will release a new version RSN).
8 This program makes use of a number of definitions defined in the main LDAP
9 Makefile but it also has a number of it's own definitions that you will
10 have to modify (all definitions are located in the Makefile).
12 CONFIG_DIRECTORY At present the configuration directory only contains
13 the template directory. The files in this directory contain the
14 attribute fields to return when a template is returned. The objectClass
15 of an object determines the whois++ template.
17 HELP_DIRECTORY The server has a number of help files that it may
18 display when queried by a client. These files are stored under the
21 LDAPHOST Which host is running a ldap server. This program
22 communicates to the X.500 Directory via LDAP so you must be able to
23 identify a host that is able to provide this communication.
25 FACILITY Some error diagnostics are reported via syslog, as is
26 normal queries if logging is enabled. This variable specifies which
27 facility to use. I use local3 so I can create a separate log file just
28 for whois++ but you may wish to log under daemon.
30 SYSLIBS Any additional libraries required. Ultrix requires -li
31 to get the Internationalisation support. I also use -lsyslog in order
32 to link with a 4.3BSD style syslog rather than the ancient syslog that
33 DEC normally ship with Ultrix.
35 INTERNATIONAL Define this is you have POSIX international support.
36 At present this is only used for displaying dates so it's not really
37 important but I intend to use this facility to support the language
38 constraint in a future release.
39 Available under Ultrix but not SunOS.
41 Once you have modified these variable you should be able to just type "make",
42 if you are in the whois++ directory, or "make ldap-whois++" from the main
43 LDAP directory. All going well there should be no problems so "make install",
44 or "make inst-whois++".
46 You should now copy the tailor file (whois++dtailor) to the ETCDIR and modify
47 the base statement to indicate to whois++ where in the DIT whois++ should base
48 its searches. You may also wish to define a user and password if you need to
49 authenticate the server.
51 Modify /etc/inetd.conf to include the new whois++ service with a line such as
52 whois stream tcp nowait ETCDIR/whois++d whois++d
53 where ETCDIR is the value of your ETCDIR variable.
54 You might like to add the -l flag (if you want to log queries) and -i if you
55 have an info attribute in the base entry (this will be displayed as a system
58 Now send a HUP (or kill and restart) /etc/inetd.
60 Note that if you turn on RFC931 lookups you will need the rfc931.c
61 module from Wietse Venema's log_tcp package (archie should be able to find
65 mrp@itd.adelaide.edu.au