PMDF Installation Guide
Tru64 UNIX Edition
Previous Next Contents Index

1.6 Post-Installation Tasks for New Sites

The following list of tasks must be completed after you install PMDF for the first time:

  1. PMDF documentation assumes your Tru64 UNIX shell process includes /usr/bin in the shell's search path (thereby making the pmdf command available in the form documented). If this is not the case, either add /usr/bin to your shell's search path, or use the fully qualified command name, /usr/bin/pmdf.
  2. Create PMDF's site-specific configuration files, using the automatic configuration generation utility. (See Chapter 3) For example, for a PMDF-MTA system, use the following command: 


    # /pmdf/bin/http_server -s
    and then point your web browser (Netscape version 3.0 or later, or Microsoft Internet Explorer version 4.0 or later), with JavaScript enabled, to 


    http://localhost:7633/
    Refer to the following chapters for configuration instructions and examples:


  3. Review the checklist that is generated by the configuration, and take whatever additional steps are required to complete the configuration of PMDF. (The automatic configuration generator produces a checklist detailing any additional steps that are required to complete the configuration of PMDF.)
  4. Use cron to schedule two periodic jobs and to run the two shell scripts that are located in the /pmdf/bin directory (post.sh and return.sh). Process Software recommends the following: However, you might want to schedule these scripts differently, according to the needs of your site. Process Software also suggests that, if your site has multiple PMDF nodes, you consider setting the minutes-after-the-hour offset for the post.sh shell script (indicating when the script will start running) to different values on different nodes (to better balance mail flow). Use the following commands to schedule cron jobs: 


    # su pmdf
$ crontab /pmdf/table/cronjobs
$ exit

    Note
    If you want to set up site-specific cron entries manually, perform the following steps: Become the pmdf user: 


    # su pmdf
    Edit the crontab entries by using the following command: 


    $ crontab -e
    Use the editor to add entries similar to 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
    The first value in the second line, shown as 0 in the above example, is the minutes-after-the-hour offset. If you have multiple PMDF nodes, then this is a value that you might want to stagger between different nodes. For example, 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. These 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. For example, 


    $ exit


  5. Replace the sendmail system startup script with PMDF's pmdf startup script. This can be done by using the following command: 


    # /pmdf/bin/symlink install

    Note
    In each of the directories /sbin/rc0.d, /sbin/rc2.d, and /sbin/rc3.d, there are files that begin with either the letter " " K or the letter " " S, , followed by a two-digit number, followed by a command name. The startup script removes the links where this command name is sendmail, and creates a corresponding link with pmdf substituted for sendmail, using the same initial letter and two-digit number. For example, original links might be: 


    # ls -l /sbin/rc0.d/*sendmail
lrwxr-xr-x   1 root    10     18 May 19  1994 K25sendmail -> ../init.d/sendmail 
# ls -l /sbin/rc2.d/*sendmail
lrwxr-xr-x   1 root    10     18 May 19  1994 K30sendmail -> ../init.d/sendmail 
# ls -l /sbin/rc3.d/*sendmail
lrwxr-xr-x   1 root    10     18 May 19  1994 S40sendmail -> ../init.d/sendmail
    Using the above example, the following commands are executed: 


    # 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 S40pmdf
    In the above example, the first three commands remove the sendmail links. The remaining commands create the corresponding pmdf links.
    The effect of the /pmdf/bin/symlink can be undone by using the following command: 


    # /pmdf/bin/symlink backout

  6. When you are installing PMDF for the first time, or even after an upgrade of the operating system (if that upgrade installed a new version of sendmail), you must replace sendmail with PMDF's /pmdf/bin/sendmail. First, save the original sendmail by renaming it to sendmail.org. Next, create a symbolic link that links sendmail to /pmdf/bin/sendmail. You can do this by using the following commands: 


    # mv /usr/sbin/sendmail /usr/sbin/sendmail.org
# ln -s /pmdf/bin/sendmail /usr/sbin/sendmail
    You should also kill any old, pre-PMDF sendmail processes that might exist and be accepting connections. This could also be necessary if an operating system upgrade starts up non-PMDF sendmail processes.

    Note
    Killing these 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 sendmail processes, use the following command: 


    # ps ax | grep sendmail
    If there any sendmail processes, you will see something similar to the following: 


    5431 ?? S       0:00.02 -accepting connections (sendmail)
    Use the following command to kill any processes: 


    # kill 5431

  7. The multithreaded PMDF POP3 or IMAP servers are handled by the PMDF Service Dispatcher. If you were previously using non-PMDF servers, you must shut down your old servers before you can use the PMDF multithreaded servers. Before you can use the multithreaded POP3 or IMAP servers, you must also configure the Dispatcher to run the desired service. Dispatcher configuration is usually performed as part of the initial web-based PMDF-MTA configuration. (See Chapters 3, 5, for instructions and sample configurations of the Dispatcher. See Chapter 4 for configuration instructions, and Chapter 5 for an example of configuring the POP and IMAP servers.)
  8. Use the following command to start up the PMDF Job Controller and PMDF Service Dispatcher: 


    # pmdf startup

  9. Configure all PMDF layered products for which you have a license. See the following chapters for configuration information for a particular layered product:

Previous Next Contents Index