The following is a list of tasks which must be completed following an upgrade installation of PMDF.
# pmdf cnbuild
cron to run periodically. If you have not
customized your pmdf crontab entries, then
you may simply issue the commands:
# su pmdf # crontab /pmdf/table/cronjobs # exitOtherwise, if you prefer to add the new
crontab entry
manually so as not to overwrite your existing, possibly customized,
pmdf crontab entries, then issue the commands
# su pmdf # crontab -eand use the editor thus invoked to add an entry such as the following:
0 0,10,20,30,40,50 * * * * /pmdf/bin/pmdf_lg_purge >/dev/null 2>&1Make sure to exit from the
pmdf user shell when you have
finished adding this entry; i.e.,
$ exit
crdb databases must be rebuilt or converted using the
pmdf convertdd utility. The
/pmdf/bin/finddb.sh shell script may be used to attempt to
detect the major PMDF databases; running this utility will create a
script file that may then be run in order to actually convert the
databases.
# /pmdf/bin/finddb.shNote, however, that if you have additional PMDF databases on your system (for instance, users' own personal alias databases), then you will also need to convert those databases. Please also note that the base name (name sans file extension) of the PMDF password database has been changed from
pauth to passworddb, so if
your sites uses the PMDF password database (not all sites do) be sure
to use the new name when you are converting the password database,
e.g.,
# pmdf convertdb /pmdf/table/pauth /pmdf/table/passworddb
# rm /pmdf/table/queue_cache/* # pmdf cache -synchronizeNote that it is a good idea to rebuild the PMDF queue cache database with the above commands or with the command
# pmdf cache -rebuildafter any upgrade of PMDF, including after minor interim releases.
/pmdf/user/ directory on UNIX systems. This database is
only used for management functions and does not in any way impact the
performance of the popstore.) The PMDF popstore user database is
located via the PMDF_POPSTORE_USER_DATABASE PMDF tailor file option,
and so is usually /pmdf/user/userdb. Sites upgrading from
PMDF V5.2 must rebuild their existing popstore user database using the
commands
# rm /pmdf/user/userdb.* # pmdf popstore x_build_user_dbSites which were using the PMDF popstore under PMDF V5.1 and which are upgrading to PMDF V6.0 should create a popstore user database using the command
# pmdf popstore x_build_user_dbafter upgrading to PMDF V6.0. This command will scan the profile directory tree and build a user database.
pmdfcyrus program to deliver to
the Cyrus message store, you should check the permission settings for
the /pmdf/bin/pmdfcyrus image to make sure that they are
still correct. The PMDF installation attempts to set the permissions
properly when it updates the image. But if the permissions are not
correct, you will need to reset them manually with the commands:
# chown cyrus-user /pmdf/bin/pmdfcyrus # chmod 4755 /pmdf/bin/pmdfcyruswhere
cyrus-user is whatever userid was selected
when installing Cyrus, typically cyrus. /pmdf/other/ directory on the PMDF system, or
available directly off the PMDF distribution CD-ROM under the
other directory. Note that this is an ISO 9660 with
Rockridge extensions CD-ROM, readable from many different platforms
including OS/2 and NT.
notes.ini,
defining server tasks from
ServerTasks=...,PNGATECto
ServerTasks=...,PNGATECIN,PNGATECOUT
# pmdf startup
1.5.1 Additional post-installation tasks for sites upgrading from PMDF V5.1 or V5.0
The following is a list of additional post-installation tasks that must
be completed following an upgrade from V5.1 or V5.0 of PMDF-MTA,
PMDF-ACCESS, PMDF-DIRSYNC, PMDF-LAN, PMDF-MB400, or PMDF-X400. Sites
upgrading from PMDF V5.2 or later should skip this section.
/pmdf/table/x400_mappings.sample.
PORT_ACCESS TCP|*|110|*|* $YPOP-RULES TCP|*|143|*|* $YIMAP-RULESand the security configuration file
security.cnf would
need corresponding ruleset definitions of:
[RULESET=DEFAULT] ENABLE=MSGSTORE/*,PASSDB/*,SYSTEM/* ! [RULESET=POP-RULES] ENABLE=MSGSTORE/*,PASSDB/CRAM-MD5,PASSDB/APOP,SYSTEM/* ! [RULESET=IMAP-RULES] ENABLE=SYSTEM/*
/pmdf/bin/pmdfsend rather than the new image
/pmdf/bin/sendmail to replace sendmail) then
you must replace sendmail with PMDF's
/pmdf/bin/sendmail. Change the symbolic link for
sendmail to /pmdf/bin/sendmail as follows:
# ln -s /pmdf/bin/sendmail /usr/sbin/sendmail
/pmdf/bin/post and /pmdf/bin/return in PMDF
V5.0, as of PMDF V5.1 are instead named /pmdf/bin/post.sh
and /pmdf/bin/return.sh, respectively. So if you are
upgrading from PMDF V5.0, you must change the crontab
entries for these jobs to use the new names. This can be performed by
issuing the commands:
²
# su pmdf $ crontab /pmdf/table/cronjobs $ exit
cron entries, as for instance if you have previously
customized those entries for site-specific reasons, then you may
perform the following steps. To submit commands to the
cron daemon, first become the user pmdf:
# su pmdfThen to edit the
crontab entries, issue the commands # su pmdf$ crontab -eand use the editor thus invoked to edit the entries to use the new names, i.e., so that they appear similar to:
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