The following is a list of tasks which must be completed following a new installation of PMDF.
product-name.license, located in the PMDF
table directory. You will have a separate license file for each PMDF
product you have licensed for the system in question. For instance, a
PMDF-MTA license would be stored in a file named
/pmdf/table/PMDF-MTA-SUN.license; a PMDF-ACCESS license
would be stored in a file named
/pmdf/table/PMDF-ACCESS-SUN.license. Issuer:Innosoft Authorization Number:auth-number Product Name:product-name Producer:Innosoft Product Release Date:release-date Product Token:token Checksum:checksumwhere
auth-number, token,
release-date, and checksum
are specific to your PMDF license, and where
product-name is a product name such as
PMDF-MTA-SUN, PMDF-ACCESS-SUN, PMDF-DIRSYNC-SUN, PMDF-LAN-SUN,
PMDF-POPSTORE-SUN, PMDF-MSGSTORE-SUN, PMDF-XGS-SUN, PMDF-X400-SUN, or
PMDF-TLS-SUN. /usr/bin in the shell's search path, thereby making the
pmdf command available in the form documented. If this is
not the case, then you may either add /usr/bin to your
shell's search path, or use the fully qualified command name,
/usr/bin/pmdf. # /pmdf/bin/http_server -sand then point your web browser (Netscape version 3.0 or later, or Microsoft Internet Explorer version 4.0 or later), with JavaScript enabled, at
http://localhost:7633/or for a PMDF-ACCESS system issue the command
# pmdf configure accessRefer to Chapters 5 and 6 (PMDF-MTA regular configuration), Chapters 17 and 18 (PMDF-MTA firewall configuration), or Chapters 5 and 7 (PMDF-ACCESS configuration) for information, step-by-step procedures, and an example configuration.
post.sh,
return.sh, and pmdf_lg_purge in the
/pmdf/bin directory. You need to use cron to
schedule three periodic jobs to run these shell scripts. Innosoft
generally recommends that the shell script post.sh be
scheduled to run every four hours and that the shell script
return.sh be scheduled to run at 30 minutes after midnight
each day; however, you may wish to schedule them differently according
to the needs of your site. Innosoft also suggests, particularly if your
site includes multiple PMDF nodes, that you consider setting the
minutes-after-the-hour offset at which the post.sh shell
script runs to different values on different nodes to better balance
mail flow.
Typical scheduling for such cron jobs can be established
by issuing the commands:
³
# su pmdf $ crontab /pmdf/table/cronjobs $ exit
sendmail system startup script with PMDF's
pmdf startup script. This may be performed
4 by issuing the command:
5
# /pmdf/bin/symlink install
sendmail, you must replace sendmail with
PMDF's sendmail. First save the original
sendmail by renaming it to sendmail.org, and
then create a symbolic link that links sendmail to
/pmdf/bin/sendmail as follows:
# mv /usr/lib/sendmail /usr/lib/sendmail.org # ln -s /pmdf/bin/sendmail /usr/lib/sendmailYou should also kill any old, pre-PMDF
sendmail processes
which might exist and be accepting connections. This may also be
necessary if an operating system upgrade starts up non-PMDF
sendmail processes. (Note that killing such processes is
not necessary after an upgrade of PMDF. Even after the first
installation of PMDF or after an upgrade of the operating system, there
will be no non-PMDF sendmail processes if the system has
been rebooted and the previous post-installation tasks have been
performed.) To see if there are any such sendmail
processes, issue the command:
# ps -ef | grep sendmailIf there any such sendmail processes, you will see something similar to the following:
root 23913 1 0 Apr 05 ? 0:01 /usr/lib/sendmail -bd -q1h
You should kill any such processes using the kill command;
e.g.,
# kill 23913
# pmdf startup
/pmdf/doc directory. PMDF provides
an HTTP server for serving out this documentation to Web browsers. To
start up the PMDF HTTP server, the PMDF Service Dispatcher must be
configured to handle the HTTP service, and access to the HTTP server
must be enabled, and then the Dispatcher must be started up (or
restarted, if it was already running). The web-based PMDF-MTA
configuration utility, discussed in Chapter 5 and Chapter 6 ,
will automatically configure the PMDF Dispatcher. man -k command in order to display a list
of PMDF man pages, then you will need to manually issue the command:
# catman 1pmdf 8pmdfNote that this command may take many minutes to complete.
man.cf file. That file will look something like:
# # Default configuration file for the SUNWman on-line manual pages. # MANSECTS=1,1m,1c,1f,1s,1b,2,3,3c,3s,3x,3xc,3n,3r,3t,3xn,3m,3k,3g,3e,3b,9f,9s,9e,9,4,5,7,7d,7i,7m,7p,7fs,4b,6,l,nYou should add
1pmdf,8pmdf to the list of MANSECTS, so
that the file is along the lines of:
# # Default configuration file for the SUNWman on-line manual pages. # MANSECTS=1,1m,1c,1f,1s,1 b,2,3,3c,3s,3x,3xc,3n,3r,3t,3xn,3m,3k,3g,3e,3b,9f,9s,9e,9,4,5,7,7d,7i,7m,7p,7fs,4b,6,l,n,1pmdf,8pmdfThis will enable users to use commands such as
man
pmdf_convertdb instead of having to specify a section as
man 8pmdf pmdf_convertdb.
cron entries, then you may perform the
following steps. To submit commands to the cron daemon,
first become user pmdf: # su pmdfTo edit the crontab entries, issue the command
$ crontab -eand use the editor thus invoked to add entries such as the following:
30 0 * * * /pmdf/bin/return.sh >/pmdf/log/return.log-`/pmdf/bin/unique_id` 2>&1 0 0,4,8,12,16,20 * * * /pmdf/bin/post.sh >/pmdf/log/post.log-`/pmdf/bin/unique_id` 2>&1 0 0,10,20,30,40,50 * * * * /pmdf/bin/pmdf_lg_purge >/dev/null 2>&1The first value in the second line, shown as
0 in the example above, is the minutes-after-the-hour
offset; particularly if you have multiple PMDF UNIX nodes, then this is
a value which you might wish to stagger between different nodes,
e.g., 0 on one node, 10 on a second
node, 20 on a third node, etc. Also note the use
of log files in the above; such log files can be useful in tracking
down problems with the operation of return and
post. Make sure to exit from the pmdf user
shell when you have finished adding these entries; i.e.,
$ exit
/etc/rc0.d, /etc/rc1.d, and
/etc/rc2.d, there are files whose names begin with either
the letter "K" or the letter
"S", followed by a two-digit number, followed by
a command name. Remove the links where this command name is
sendmail, and create a corresponding link with
pmdf substituted for sendmail , making sure
to use the same inital letter and two-digit number. For example, you
might see links such as the following: # ls -l /etc/rc0.d/*sendmail-rwxr--r-- 4 root sys 1183 Oct 25 04:14 /etc/rc0.d/K57sendmail # ls -l /etc/rc1.d/*sendmail-rwxr--r-- 4 root sys 1183 Oct 25 04:14 /etc/rc1.d/K57sendmail # ls -l /etc/rc2.d/*sendmail-rwxr--r-- 4 root sys 1183 Oct 25 04:14 /etc/rc2.d/S88sendmailIn this case you would issue the following commands:
# rm /etc/rc0.d/K57sendmail# rm /etc/rc1.d/K57sendmail# rm /etc/rc2.d/S88sendmail# cd /etc/rc0.d# ln -s ../init.d/pmdf K57pmdf# cd /etc/rc1.d# ln -s ../init.d/pmdf K57pmdf# cd /etc/rc2.d# ln -s ../init.d/pmdf S88pmdfIn the example above, the first three commands remove the
sendmail files, and the remaining commands
create the corresponding pmdf links. /pmdf/bin/symlink may be undone by issuing the command:
# /pmdf/bin/symlink backout