Problem
I would like to have my system periodically check for missing patches and apply them automatically.
NOTES: patchck's obsolete automated installation capabilities, previously
provided by the patchck AUTO option and the autopathck shell script,
have been removed from patchck. patchck is designed to offer
installation choices, to streamline the installation process, and
display key information such as when to reboot and needed
post-installation configuration messages. patchck therefore
should not be run in the background. Solution
One feature of the patchck utility is to automatically update your system.
NOTES: autopatchck and this TA is obsolete and no longer supported.
The solution below and this TA is for historical information only.
See problem section above.This is done using the script:/usr/lib/patchck.d/autopatchckTo have your system updated monthly, add this to your root crontab as:
0 0 1 * * /usr/lib/patchck.d/autopatchckIn conjunction with this utility it is also suggested that you use the patchck variables, MAIL_LOGS & MAIL_LOGS_TO.
Set these in a system specific configuration file,
/usr/lib/patchck.d/`uname -n`.patchck.confMAIL_LOGS=ALL
MAIL_LOGS_TO=admin@systems.comWith this in place, the patchck utility will selfupdate, check for new patches and will mail the patchck logs to the administrator specified in the MAIL_LOGS_TO variable.
NOTES: In order to use this tool, the system must be connected to the
internet with the ability to ftp to the patch repository.It is also suggested that the system have a regular backup procedure in place, as it is always a good practice.
Not all patches are automatically installable. The patchck utility
will provide a message indicating that automatic installation is
blocked for a specific patch. Large maintenance packs and other
patches which can't be removed or rolled back will be blocked.
These patches can be installed by patchck, but will require that
you run the utility manually.This procedure should only be used on well maintained systems. A system administrator for a large network of systems may want to test autopatchck on a lab machine before deploying network-wide.
Systems that fail system verification with a large number of errors
may have problems installing new patches. It may be prudent to
correct such errors prior to updating the system. See also
TA126125 - What is `patchck` - the patch management tool?http://www.sco.com/support/patchck.html