The following is a list of tasks which must be completed following a new installation of PMDF.
/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 19 and 20 (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 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 /pmdf/bin/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/sbin/sendmail /usr/sbin/sendmail.org # ln -s /pmdf/bin/sendmail /usr/sbin/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 ax | grep sendmailIf there any such sendmail processes, you will see something similar to the following:
5431 ?? S 0:00.02 -accepting connections (sendmail)You should kill any such processes using the
kill command;
e.g.,
# kill 5431
# pmdf startup
cron entries, then you may perform the
following steps. To submit commands to the cron daemon,
first become user pmdf: # su pmdfThen to 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 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.sh and
post.sh. Make sure to exit from the pmdf user
shell when you have finished adding these entries; i.e.,
$ exit
/sbin/rc0.d, /sbin/rc2.d, and
/sbin/rc3.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. The script removes the links where this command name is
sendmail, and creates a corresponding link with
pmdf substituted for sendmail , making sure
to use the same inital letter and two-digit number. For example,
original links might be: # ls -l /sbin/rc0.d/*sendmaillrwxr-xr-x 1 root 10 18 May 19 1994 K25sendmail -> ../init.d/sendmail # ls -l /sbin/rc2.d/*sendmaillrwxr-xr-x 1 root 10 18 May 19 1994 K30sendmail -> ../init.d/sendmail # ls -l /sbin/rc3.d/*sendmaillrwxr-xr-x 1 root 10 18 May 19 1994 S40sendmail -> ../init.d/sendmailIn this case, the commands executed would be:
# rm /sbin/rc0.d/K25sendmail# rm /sbin/rc2.d/K30sendmail# rm /sbin/rc3.d/S40sendmail# cd /sbin/rc0.d# ln -s ../init.d/pmdf K25pmdf# cd /sbin/rc2.d# ln -s ../init.d/pmdf K30pmdf# cd /sbin/rc3.d# ln -s ../init.d/pmdf S40pmdfIn the example above, the first three commands remove the
sendmail links, and the remaining commands
create the corresponding pmdf links. /pmdf/bin/symlink may be undone by issuing the command:
# /pmdf/bin/symlink backout