PROBLEM: (QAR 47021, QAR 58632) (Patch ID: OSF425-405233) ******** This patch fixes the following problems with the "at -t" command: o The command did not work with user id's that were not in the password file o The command did not work on the leap year of 2000. PROBLEM: (QAR 52197) (Patch ID: OSF425-405337) ******** Fixes a problem in which the "at" command does not reject illegal time specifications. PROBLEM: (QAR 53239) (Patch ID: OSF425-405337) ******** Fixes a problem in which the "at" command does not accept dates for years 2001-2037. PROBLEM: (QAR 58635) (Patch ID: OSF425-405337) ******** Fixes a problem in which the "at -t" command does not default to zero seconds when the "ss" field is not specified. PROBLEM: (QAR 49235) (Patch ID: OSF425-405337) ******** Fixes a problem in which the "cron" daemon terminates when an "at" job is submitted to a remote system with the "rsh" command. PROBLEM: (QAR 47529, STLQ70084) (Patch ID: OSF425-405337) ******** Fixes a problem in which the "cron" command does not log a message when it is terminated by a SIGTERM signal. PROBLEM: (QAR 59526) (Patch ID: OSF425-405337) ******** Fixes a problem in which the "cron" command does not correctly schedule jobs specified in the crontab file to run at more than one minute. PROBLEM: (QAR 56560, HPAQA2134) (Patch ID: OSF425-405337) ******** Fixes a problem in which the "cron" command does not schedule jobs correctly after a Daylight Savings Time change. The Release Notes contain the man page update for crontab(1). PROBLEM: (QAR 59433, QAR 59434, HPAQ303K0, SQO100438) (Patch ID: OSF425-405337) ******** Fixes a problem in which the "cron" command terminates with a core dump sometime after a "crontab -r" command is executed. PROBLEM: (QAR 47531, QAR 51333, QAR 51676, UTO101072, MCPM70EEQ, MCGMB0H7C) (Patch ID: OSF425-405337) ******** Fixes a problem in which the "at" command may generate messages similar to "at: queue full" or "MAXRUN (25) procs reached". Also implements a more advanced batch facility with user-definable limits. Included here is a short high level description of the new cron features. The Release Notes contain the man page updates for cron(8) and queuedefs(4). Cron used to use a constant MAXRUN (set to 25) to limit the number of jobs running at any given time. This limit is now user definable and is defined by adding a line "max_jobs = x" to the queuedefs file, where "x" is the maximum number of jobs allowed to be run at any given time. Now cron reads "max_jobs" from the queuedefs file, if it is available, and uses it in place of the constant MAXRUN. If a user submits a large number of at/batch/cron jobs, increasing the maximum allowable number of jobs may result in a huge log file. If some or all of these jobs run for a long time then all the other jobs waiting in different queues will be rescheduled every minute resulting in excessive logging of "rescheduled" messages. This can now be controlled by adding another line "log = x" to the queuedefs file, where "x" is the level of logging to be done by the cron daemon. PROBLEM: (SSRT0567U, SSRT0583U, SSRT0590U, SSRT0487U, QAR 54187) (Patch ID: OSF425-405470 Patch ID: OSF425-405547, Patch ID: OSF425-685, Patch ID: OSF425-400404) ******** A potential security vulnerability has been discovered, where under certain circumstances, system integrity may be compromised. This may be in the form of improper file or privilege management. Compaq has corrected this potential vulnerability. PROBLEM: (CLD BCGM40DM9, CLD KAOQ23606, QAR 70043) (Patch ID: OSF425-637) ******** This patch fixes a problem with crontab in which, when root runs 'crontab -e user', the user's crontab file is edited and saved, but isn't re-read by the cron daemon. Instead root's crontab file is re-read. PROBLEM: (BCGMC1ZNX, HPAQ80JML, BCGMA0G3H, BCGMA2191) (PATCH ID: OSF425-960) ******** This patch fixes a problem where some crontab jobs would run multiple times in the same minute. This problem was introduced by another cron patch on a previous patch kit. In fixing an earlier problem, cron was changed so that if a crontab was submitted that contained an entry for the current minute, the entry was run immediately. Previously, the entry was not run. This change in behavior caused a problem for crontab jobs which updated crontab without deleting the entry that started them. Such jobs could be run multiple times during their first minute. PROBLEM: (78912, FNO95387A, BCGM51P8N) (PATCH ID: OSF425-1000) ******** This patch fixes two cron problems: 1) the cron daemon does intensive logging and fills up the disk, and 2) multiple cron daemons continue to run and consume system resources due to the fact that after a user is deleted from the system there are still jobs running on the users behalf.