Patch Name: PHCO_22770 Patch Description: s700_800 10.01 cumulative cron/at/crontab patch Creation Date: 01/02/10 Post Date: 01/02/16 Hardware Platforms - OS Releases: s700: 10.01 s800: 10.01 Products: N/A Filesets: OS-Core.CMDS-MIN OS-Core.CMIN-ENG-A-MAN Automatic Reboot?: No Status: General Release Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHCO_22770 Symptoms: PHCO_22770: 1.crontab(1) incorrect functionality. 2.at(1) incorrect argument parsing. 3.Patches for cron(1M) should stop cron and start the new cron. PHCO_17550: at(1) does not accept input of "00" or "0" for year for all locales. PHCO_16953: 1. On trusted systems, cron(1) has slower performance due to calling getspwent() when getspwnam() should have been used. 2. at(1) schedules jobs incorrectly relative to 28 February of non-leap years. 3. at(1) does not recognize year 00 (2000). When year is input as 00, at(1) exits with the error message - "bad date specification" PHCO_15228: Year displayed in two digits PHCO_14058: 1. With libc patch installed, at dumps core. 2. at is not able to correctly schedule jobs for Feb 29 2000 PHCO_10735: Cron used to dump core and die when jobs submitted with at -m were killed. PHCO_10112: The following symptoms correspond to the descriptions in the defect descriptions field for PHCO_10112: 1. option -t now deal with year 2000 input correctly. 2. year limit has been increased from 2030 to 2037. PHCO_7997: 1. at(1) cannot schedule job using weekdays in the last week of the month. 2. cron does not mail stdout and stderr on trusted systems. 3. '.' not present in default PATH PHCO_6862: 1. Cron dumps core intermittently. 2. Cron has a hard-coded limit of MAXRUN (40) child processes which can be running simultaneously. Now the limit has been increased to 100. PHCO_6286: Cron is going into a loop using all available cpu several times a day. This happens intermittently when the system is heavily loaded. Defect Description: PHCO_22770: 1. crontab(1) incorrect functionality. Resolution: Code is modified to take care of this issue. 2. at(1) incorrect argument parsing. Resolution: The code is modified to take care of this. 3. The cron(1M) patches do not stop the old cron daemon and re-start the new cron daemon. Resolution: The cron(1M) patch scripts now stop the old cron daemon and restart the new cron daemon after patch installation. PHCO_17550: at(1) treats year input of 00 or 0 as incorrect when locale is set to one which defines D_T_FMT (date-time) string to have year in fields other than the third. For eg. japanese locale defines the date string to be of format yy/mm/dd. With locale set to japanese, an attempt to schedule a job using at(1) for a date 00/12/20 or 0/12/20 fails. Resolution: at(1) assumed that the year field can be only in the third field of the date string. This assumption has been removed. Also, the function which returned error if the date string had 0 or 00 in the first or second fields has been changed not to check and return error for such a condition. Now, at(1) accepts input of 0 or 00 for year in any field of the date string, as specified by D_T_FMT string for the locale. PHCO_16953: 1. On trusted systems, cron(1) called getspwent() which performs a linear search in the passwd database, instead of getspwnam() which performs a keyed search. 2. Jobs scheduled after 28 Feb are scheduled erratically by at(1). The following shows the incorrect behaviour of at(1). # date 0227112099 Sat Feb 27 11:20:00 GMT 1999 # at now + 2 day warning: commands will be executed using /usr/bin/sh job 920287223.a at Mon Mar 1 11:20:23 1999 # at now + 3 day warning: commands will be executed using /usr/bin/sh job 920287243.a at Mon Mar 1 11:20:43 1999 In the above example, job is scheduled for March 1st for both the inputs "now + 2 day" and "now + 3 day". For the input "now + 3 day", at(1) should have scheduled the job for March 2nd 1999. The source code has been changed to fix the defect. After the fix, at(1) correctly schedules jobs relative to Feb, 28th. In the above example, for input "now + 3 day", at(1) schedules the job for March 2nd. 3. at(1) treats year input of 00 as incorrect. Following shows how at(1) behaves with 00 as input year. # at 12:00 1 Jan 00 bad date specification The command has been changed to accept 00 as year 2000. After the fix, at(1) treats year input of 00 as year 2000 and does not show any error messages. PHCO_15228: Year displayed in two digits. PHCO_14058: The following defects are fixed in this patch: 1.With libc patch PHCO_12009 installed, at on 10.01 dumps core. 2.When using at to schedule a job 29 Feb 2000, the job actually gets scheduled for 1 Mar 2000. PHCO_10735: Cron used to dump core and die when jobs submitted with at -m were killed. PHCO_10112: The following symptoms correspond to the descriptions in the defect descriptions field for PHCO_10112: 1. option -t now deal with year 2000 input correctly. 2. year limit has been increased from 2030 to 2037. PHCO_7997: 1. at(1) cannot schedule job using weekdays in the last week of the month. 2. cron does not mail stdout and stderr on trusted systems. 3. '.' not present in default PATH PHCO_6862: 1. Cron dumps core intermittently. 2. Cron has a hard-coded limit of MAXRUN (40) child processes which can be running simultaneously. Now the limit has been increased to 100. PHCO_6286: Cron is going into a loop using all available cpu several times a day. This happens intermittently when the system is heavily loaded. SR: 8606165710 8606158467 5003451278 4701416891 1653274167 1653269746 1653266239 1653241117 1653215038 4701347153 Patch Files: /usr/lib/nls/msg/C/at.cat /usr/lib/nls/msg/C/cron.cat /usr/lib/nls/msg/C/crontab.cat /usr/sbin/cron /usr/bin/at /usr/bin/crontab /usr/share/man/man1.Z/at.1 /usr/share/man/man1.Z/batch.1 what(1) Output: /usr/lib/nls/msg/C/at.cat: None /usr/lib/nls/msg/C/cron.cat: None /usr/lib/nls/msg/C/crontab.cat: None /usr/sbin/cron: $Revision: 74.5.3.19 $ PATCH/10_01 PHCO_7997 $Revision: 74.2.1.8 $ PATCH_10_01: hpux_rel.o cron.o funcs.o 01/02/10 /usr/bin/at: $Revision: 74.5.3.19 $ $Revision: 74.2.1.4 $ $Revision: 74.2.1.7 $ PATCH_10_01: hpux_rel.o at.o pdt.o ptime.o pdate.o f uncs.o permit.o 01/02/10 /usr/bin/crontab: $Revision: 74.5.3.19 $ PATCH_10_01: hpux_rel.o crontab.o permit.o funcs.o 0 1/02/10 /usr/share/man/man1.Z/at.1: None /usr/share/man/man1.Z/batch.1: None cksum(1) Output: 2031680443 3232 /usr/lib/nls/msg/C/at.cat 4002162402 2532 /usr/lib/nls/msg/C/cron.cat 4098515531 1035 /usr/lib/nls/msg/C/crontab.cat 3181343877 41102 /usr/sbin/cron 3448415927 45190 /usr/bin/at 2645454798 20560 /usr/bin/crontab 2773564955 8834 /usr/share/man/man1.Z/at.1 2773564955 8834 /usr/share/man/man1.Z/batch.1 Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHCO_6286 PHCO_6862 PHCO_7997 PHCO_10112 PHCO_10735 PHCO_14058 PHCO_15228 PHCO_16953 PHCO_17550 Equivalent Patches: PHCO_22767: s700: 11.00 s800: 11.00 PHCO_22768: s700: 10.20 s800: 10.20 PHCO_22769: s700: 10.10 s800: 10.10 Patch Package Size: 190 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHCO_22770 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHCO_22770.depot By default swinstall will archive the original software in /var/adm/sw/patch/PHCO_22770. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. WARNING: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHCO_22770.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHCO_22770.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: None.