2    Summary of Base Operating System Patches

This chapter summarizes the base operating system patches included in Patch Kit-0010.

Table 2-1 lists patches that have been updated.

Table 2-1:  Updated Base Operating System Patches

Patch IDs Change Summary
Patches 931.00, 942.00, 956.00, 961.00, 962.00, 969.00, 971.00, 975.00, 985.00, 988.00, 993.00, 998.00, 1002.00, 1006.00, 1020.00, 1021.00, 1023.00, 1024.00, 1028.00, 1030.00, 1032.00, 1033.00, 1044.00, 1048.00, 1050.00, 1052.00, 1078.00, New
Patches 150.00, 815.00 Superseded by Patch 929.00
Patches 274.00, 909.00 Superseded by Patch 953.00
Patches 60.00, 60.01, 531.00 Superseded by Patch 957.00
Patch 410.01 Superseded by Patch 963.00
Patches 89.00, 389.00, 400.00, 416.00, 752.00, 939.00 Superseded by Patch 965.00
Patch 587.01 Superseded by Patch 968.00
Patches 34.00, 112.00,191.00, 518.00, 586.00, 613.00, 637.00, 610.00, 623.00, 632.00, 654.01, 709.00, 731.00, 967.00, 970.00 Superseded by Patch 978.00
Patches 56.00, 44.00, 85.00, 177.00, 485.00, 547.01, 655.00, 831.01, 940.00, 974.00, 973.00 Superseded by Patch 979.00
Patch 496.00 Superseded by Patch 982.00
Patches 649.01, 409.01, 760.00, 934.00 Superseded by Patch 987.00
Patches 149.00, 188.00, 494.00, 500.00, 595.01 Superseded by Patch 990.00
Patch 812.01 Superseded by Patch 991.00
Patches 80.00, 208.00, 136.00, 230.00, 395.00, 403.03 Superseded by Patch 992.00
Patches 213.00, 265.00, 944.00 Superseded by Patch 995.00
Patch 270.00 Superseded by Patch 996.00
Patches 80.00, 207.00, 136.00, 229.00, 209.00, 395.00, 404.00, 492.00, 894.00, 1003.00 Superseded by Patch 1004.00
Patches 140.00, 746.00 Superseded by Patch 1008.00
Patch 788.00 Superseded by Patch 1012.00
Patches 689.00, 1022.00, 1025.00 Superseded by Patch 1027.00
Patches 67.00, 121.00, 204.00, 527.00, 667.00, 668.01, 695.00, 697.00, 698.00, 696.00 Superseded by Patch 1029.00
Patches 132.00, 283.00, 669.01, 844.01 Superseded by Patch 1034.00
Patches 11.00, 15.00, 18.00, 32.00, 35.00, 37.00, 46.00, 47.00, 47.01, 80.00, 125.00, 125.01, 24.00, 84.00, 96.00, 123.00, 138.00, 136.00, 136.01, 156.00, 198.00, 201.00, 219.00, 219.01, 219.02, 227.00, 244.00, 249.00, 256.00, 271.00, 384.00, 385.00, 390.00, 395.00, 401.00, 483.00, 499.00, 508.00, 583.00, 585.00, 601.00, 650.00, 596.00, 600.00, 603.00, 582.00, 620.00, 88.00, 16.00, 508.01, 672.01, 740.00, 744.00, 747.00, 749.00, 793.00, 794.00, 802.00, 716.00, 763.00, 769.00, 856.00, 17.00, 54.00, 98.00, 181.00, 199.00, 247.00, 502.00, 736.00, 756.00, 82.00, 501.00, 611.01, 764.00, 781.00, 800.00, 19.00, 10.00, 480.00, 809.01, 883.01, 819.00, 923.00, 941.00, 943.00, 989.00, 1000.00, 1015.00, 983.00, 977.00, 254.00, 606.00, 578.01, 1054.00, 958.00, 1038.00 Superseded by Patch 1042.00
Patches 5.00, 2.00, 14.00, 64.00, 36.00, 50.00, 76.00, 100.00, 71.00, 22.00, 86.00, 113.00, 119.00, 106.00, 109.00, 129.00, 95.00, 114.00, 61.00, 103.00, 105.00, 75.00, 78.00, 130.00, 144.00, 87.00, 139.00, 62.00, 133.00, 134.00, 116.00, 148.00, 157.00, 157.01, 145.00, 25.00, 159.00, 167.00, 147.00, 190.00, 141.00, 178.00, 192.00, 222.00, 196.00, 173.00, 197.00, 234.00, 402.00, 184.00, 186.00, 255.00, 257.00, 258.00, 260.00, 267.00, 388.00, 387.00, 272.00, 393.00, 391.00, 214.00, 282.00, 241.00, 187.00, 398.00, 399.00, 394.00, 146.00, 408.00, 281.00, 269.00, 418.00, 419.00, 422.00, 421.00, 423.00, 530.00, 533.00, 488.00, 490.00, 491.00, 546.00, 504.00, 505.00, 511.00, 513.00, 515.00, 517.00, 520.00, 426.00, 414.00, 226.00, 548.00, 559.00, 560.00, 569.00, 570.00, 575.00, 584.00, 592.00, 634.00, 616.00, 633.00, 656.00, 644.00, 648.00, 619.00, 625.00, 624.00, 612.00, 617.00, 621.00, 572.00, 636.00, 640.00, 657.00, 580.00, 594.00, 564.01, 646.00, 579.01, 708.00, 714.00, 719.00, 720.00, 721.00, 727.00, 728.00, 730.00, 738.00, 5751.00, 755.00, 768.00, 770.00, 772.00, 773.00, 774.00, 778.00, 780.00, 783.00, 786.0, 806.00, 810.00, 823.00, 837.00, 853.00, 859.00, 860.00, 864.00, 869.00, 872.00, 879.00, 880.00, 700.00, 715.00, 734.00, 737.00, 739.00, 758.00, 762.00, 766.00, 779.0, 782.00, 792.00, 796.00, 797.00, 803.00, 804.00, 817.00, 820.00, 822.00, 824.00, 833.00, 839.00, 850.00, 855.00, 62.00, 866.00, 870.00, 871.00, 701.00, 835.00, 832.00, 877.00, 882.00, 861.01, 849.01, 827.01, 9.00, 111.00, 111.01, 155.00, 99.00, 189.00, 239.00, 790.00, 878.00, 753.01, 925.00, 927.00, 930.00, 932.00, 935.00, 936.00, 93700, 950.00, 951.00, 952.00, 955.00, 959.00, 960.00, 972.00, 976.00, 981.00, 986.00, 997.00, 999.00, 1005.00, 1010.00, 1011.00, 1013.00, 1014.00, 1018.00, 1019.00, 1035.00, 1036.00, 1037.00, 1039.00, 1043.00, 1045.00, 1046.00, 1047.00, 1051.00, 1056.00, 1059.00, 1061.00, 1063.00, 926.00, 1064.00, 933.00, 1053.00, 1055.00, 1065.00, 1040.00, 6.00, 39.00, 135.00, 245.00, 268.00, 653.00, 28.00, 175.00, 427.00, 561.00, 169.00, 532.00, 571.00, 655.00, 268.01, 673.01, 825.00, 1060.00, 828.00, 1049.00 Superseded by Patch 1058.00
Patches 152.00, 243.00, 263.00, 514.00, 1016.00 Superseded by Patch 1062.00
Patches 16.00, 88.00, 675.01 Superseded by Patch 1066.00
Patch 890.00 Superseded by Patch 1067.00
Patches 56.00, 44.00, 85.00, 177.00, 485.00, 547.00, 677.00, 892.00, 1069.00 Superseded by Patch 1070.00
Patches 1.00, 69.00, 41.00, 21.00, 70.00, 70.01, 110.00, 126.00, 160.00, 128.00, 128.01, 171.00, 153.00, 231.00, 211.00, 259.00, 279.00, 280.00, 253.00, 405.00, 215.00, 415.00, 481.00, 506.00, 507.00, 509.00, 552.00, 577.00, 576.00, 550.00, 537.00, 537.01, 686.00, 573.00, 608.00, 598.00, 589.00, 638.00, 631.00, 622.00, 652.00, 671.00, 630.00, 628.00, 663.00, 635.00, 639.00, 642.00, 659.00, 641.00, 647.00, 609.00, 537.02, 661.01, 704.00, 705.00, 718.00, 723.00, 724.00, 726.00, 733.00, 742.00, 757.00, 765.00, 798.00, 808.00, 821.00, 829.00, 830.00, 834.00, 843.00, 876.00, 725.00, 750.00, 807.00, 884.00, 885.00, 886.00, 891.00, 928.00, 945.00, 946.00, 947.00, 948.00, 949.00, 954.00, 964.00, 966.00, 980.00, 984.00, 994.00, 1001.00, 1007.00, 1009.00, 1017.00, 1041.00, 896.00, 1057.00, 1068.00, 1071.00, 1072.00 Superseded by Patch 1073.00
Patches 94.00, 526.00, 1026.00 Superseded by Patch 1074.00
Patches 132.00, 283.00, 669.01, 902.00 Superseded by Patch 1075.00
Patches 219.00, 220.00, 233.03 Superseded by Patch 1076.00
Patches 748.00, 813.00 Superseded by Patch 1077.00

Table 2-2 provides a summary of patches in Patch Kit-0010.

Table 2-2:  Summary of Base Operating System Patches

Patch IDs Abstract

Patch 3.00

OSF410-035

Patch: PCXAL, LK411, And Similar Keyboards

State: Existing

On systems with PCXAL, LK411, and similar keyboards, sometimes the keyboard stops working.

Patch 4.00

OSF410-038

Patch: Change Cursor Reporting In The Workstation Driver

State: Existing

Issuing a SET_DEVICE_MODE ioctl to the workstation driver to change cursor reporting to relative mode fails.

Patch 8.01

OSF410-042-1

Patch: S3 Trio64V+ Graphics Card Incorrectly Identified

State: Existing

This patch fixes a problem in which the S3 Trio64V+ graphics card (PB2GA-JC or PB2GA-JD) is not being uniquely identified by the driver at startup.

Patch 23.00

OSF410-400126

Patch: Kernel Memory Fault Correction

State: Existing

This patch fixes a "kernel memory fault" in the dqget() routine.

Patch 30.00

OSF410X11-400011

Patch: S3 Trio64 Graphics Card Can Lose Time

State: Existing

Systems with an S3 Trio64 graphics card can lose time (on the order of a few minutes a day).

Patch 51.00

OSF410-400166

Patch: Full Duplex Mode Setting On DEFPA Correction

State: Existing

This patch fixes a problem in which setting full duplex mode on DEFPA using "/usr/sbin/fddi_config -i fta0 -x1" will not enable full duplex mode.

Patch 53.00

OSF410-400168

Patch: netstat Command Output Correction

State: Existing

This patch fixes a problem in which "netstat -I fta0 -s" reports 6 bytes of the 8 byte "Station UID" and "Station ID".

Patch 63.00

OSF410X11-405005

Patch: ATI Mach64 Graphics Card Monitor Handling

State: Existing

On systems with an ATI Mach64 graphics card, sometimes the monitor will lose synchronization or become stuck in power-save mode.

Patch 74.00

OSF410-050

Patch: CD/DSR Not Dropping Right Away After Dial-out

State: Existing

uugetty - CD/DSR not dropping right away after dial-out.

Patch 77.00

OSF410-400183

Patch: rwhod Correction

State: Existing

This patch fixes a problem in which rwhod daemon can cause a core dump with a segmentation fault.

Patch 81.00

OSF410-400191

Patch: NTP Correction

State: Existing

This patch fixes a problem where the NTP deamon (xntpd) does not work using a Spectracom radio clock as a reference.

Patch 91.00

OSF410-053

Patch: Kernel Debugger Corrections

State: Supersedes patch OSF410-046 (26.00)

This patch corrects the following:

  • Fixes a problem with the ikdebug debugger that causes a system to panic with the following message:

    panic: simple_lock: time limit exceeded

  • Fixes a problem in which an AlphaStation 600, as well as other systems, may crash when user mode debuggers are in use (for example, dbx or ladebug).

  • Reduces the kdebug memory usage.

  • Fixes user mode breakpoints/single stepping.

  • Fixes kdebug MP problems.

Patch 102.00

OSF410DX-400007

Patch: DECwindows Session Manager Correction

State: Existing

This patch fixes the following problems in the DECwindows Session Manager (dxsession) application. Ungraceful exit can be made through the window manager's 'Close' button, whose behavior is inconsistent with that of dxsession's 'End Session' button.

Patch 115.00

OSF410-405063

Patch: libaio Correction

State: Existing

This patch fixes a problem that can occur with programs linked with libaio. These programs could dump core with a SIGSEGV signal or corrupt memory when calling the close() function with a bad file descriptor value.

Patch 117.00

OSF410-400223

Patch: talkd Correction, Security (SSRT0446U)

State: Existing

A potential security vulnerability in talkd has been corrected.

Patch 118.00

OSF410DX-003

Patch: Environmental Monitoring Daemon Correction

State: Existing

This patch fixes the problem of the Environmental Monitoring daemon (envmond) failing to start sometimes when the system boots up.

Patch 124.00

OSF410CDE-400009

Patch: dtksh Command Correction

State: Existing

This patch corrects two problems that occur when using the dtksh command:

  • dtksh can lose output lines when a pipe or I/O indirection is used.

  • The following error message may be displayed after using a pipe in dtksh:

    dtksh: hist_flush: EOF seek failed errno=9

Patch 162.00

OSF410-400263

Patch: ar Command Correction

State: Existing

This patch fixes the following problems with the ar command:

  • When creating or modifying an archive, the ar command may leave a large file in /tmp or in the current directory (when the -l option is used).

  • If Patch 46.00 (OSF400-046) was previously installed, the ar command cannot find object modules specified for deletion or extraction if the file name is longer than 13 characters. An error message similar to the following is displayed:

    ar: Error: button_previous.gif not found

Patch 163.00

OSF410-078

Patch: inetd Enhancement

State: Existing

Enhanced /usr/sbin/inetd.

Patch 164.00

OSF410-079

Patch: vipw Issues Warnings Enhancement

State: Existing

/usr/sbin/vipw now issues warning when used to edit a large password file.

Patch 166.00

OSF410-081

Patch: removeuser Calls userdel Deletes Users Account

State: Existing

The script /usr/sbin/removeuser now calls /usr/sbin/userdel to do the actual work of deleting a user's account.

Patch 170.00

OSF410-405087

Patch: PCI Device Using Dense Space I/O Correction

State: Existing

This patch fixes a problem in which an AlphaServer 4100 with a PCI device that uses dense space I/O handles will panic with the following error message:

panic: Machine Check 670

Patch 172.00

OSF410-405095

Patch: comm Command Correction

State: Existing

This patch fixes a problem in the comm command where it will split long line(s) in a file by inserting a in a file by inserting a <carriage return> that exceeds 255 characters. In some cases, characters will be truncated.

Patch 176.00

OSF410-091

Patch: PowerStorm 3D30 PBXGB-AA 4D20 PBXGB-CA Correction

State: Existing

AlphaStation 255 systems with a PowerStorm 3D30 (PBXGB-AA) or PowerStorm 4D20 (PBXGB-CA) graphics card may hang, halt, or crash.

Patch 179.00

OSF410-400268

Patch: Problem, System Time Using MICRO_TIME Kernel Config

State: Existing

This patch fixes the following:

  • Fixes several problems with system time when the MICRO_TIME kernel configuration option is used. It resolves a one second delay in updating secondary processors after changing the system time.

  • BOOTTIME is now written properly to utmp from a secondary processor during boot. Processors are immediately updated when brought on-line during boot or via the psradm utility.

Patch 180.00

OSF410-400269

Patch: yppasswd Command Correction

State: Existing

This patch fixes a problem in which yppasswd users get the error "password mismatch, password unchanged" creating passwords longer than 8 characters.

Patch 185.00

OSF410-400282

Patch: quotas For Filesystems Causes rpc.rquotad To Hang

State: Supersedes patch OSF410-400214 (107.00)

This patch corrects the following:

  • Fixes a problem in which the rpc.rquotad daemon hangs when using quotas for NFS filesystems in a TruCluster or Available Server (ASE) V1.4 environment.

  • Fixes the following problems with the rpc.rquotad:

    • When the NFS server is a member of an ASE or TruCluster environment, the rpc.rquotad daemon may exit abnormally. The abnormal exit causes the quota command on NFS clients to not report quotas for NFS mounted file systems.

    • When the quota command is repeatedly run from a remote system, the virtual size of the rpc.rquotad daemon on the local system will grow due to a memory leak.

Patch 195.00

OSF410-400295

Patch: HX (PMAGB-BA) Graphic Mouse Cursor Correction

State: Existing

This patch fixes a problem with the mouse cursor when the system contains the HX (PMAGB-BA) graphics option. The cursor offset is incorrect on the Y Axis by 2 pixels.

Patch 200.00

OSF410-400305

Patch: diff Command Correction

State: Existing

This patch fixes a problem related to misinterpretation of multibyte characters by the diff command. The problem also affects the delta command of SCCS. The symptom of the problem in the diff command is that it sometimes treats a text file containing multibyte characters as a binary file. The symptom of the problem in the delta command is that it sometimes fails to check in a program source file containing multibyte characters.

Patch 216.00

OSF410-093

Patch: shutdown -r Command Correction

State: Existing

This patch fixes a problem that occurs on an AlphaServer 2100A system. When the system is shut down using the "shutdown -r" command, the system will not reboot.

Patch 223.00

OSF410-100

Patch: adduser Calls useradd To Create New User Account

State: Existing

The shell script /usr/sbin/adduser now calls /usr/sbin/useradd to do the actual work of creating the new user account.

Patch 236.00

OSF410-097

Patch: btextract Utility Correction

State: Supersedes patches OSF410-047 (27.00), OSF410-056 (97.00)

This patch corrects the following:

  • Fixes an automatic reboot problem when the system is booted from tape using the custom_install.sh file in a mini-root environment.

  • Fixes problems encountered when restoring file systems from a tape device using the btextract utility.

  • Fixes several problems for Bootable Tape.

    • While restoring the filesystem from the tape, the filesystem size selected was not sufficient to restore the contents from the tape.

    • The information message for restoring AdvFS additional volumes was not informative.

    • The SWAP SELECTION code for attended restore was failing while restoring customized disks with not default disklabels.

    • Extra mkdir statement was printing on the terminal.

    • The error status from "mt" command was not being checked.

    • Relative path for -s filename was not being accepted by btcreate.

    • The estimated size of the root filesystem should be corrected.

    • The file systems are not mounted automatically by btcreate.

    • The reboot command does not reboot the system while booted from the tape.

Patch 237.03

OSF410-400331D-3

Patch: voliod Command Correction

State: Supersedes patches OSF410-400331-1 (219.01), OSF410-400331-2 (219.02), OSF410-400331D (228.00)

This patch allows the uusend voliod commands to work correctly when the customer builds a hashed passwd database using a non-default page file block size.

Patch 238.00

OSF410-400383

Patch: llogin Command Correction

State: Existing

This patch corrects a problem when exiting an llogin session. If the user does not enter a carriage return to display the shell prompt, the llogin process will continue to run, consuming all the free CPU time available.

Patch 240.00

OSF410-106

Patch: Corrects X.25 Crash On AlphaServer 1000

State: Existing

This patch corrects a system call return value that causes the X.25 layered product to crash. This fixes a problem in which the io_zero() system call returns an incorrect value on an AlphaServer 1000.

Patch 242.00

OSF410-108

Patch: Kernel Memory Fault Correction

State: Existing

An AlphaServer 4100 may panic with a kernel memory fault during boot under the following conditions:

  • The system has more than 32 Mb of memory.

  • The console variable MEMORY_TEST is set to "partial".

Patch 246.00

OSF410-400325

Patch: atom Command Corrections

State: Existing

This patch corrects the following problems:

  • The atom command terminates with SIGSEVG signal if the threaded program being instrumented has a stripped shared library.

  • The "atom -all -env threads" command produces an instrumented version of a threaded (eg DCE) application that will not execute correctly, with either "-tool third" or "-tool hiprof" tool options.

Patch 248.00

OSF410-400377

Patch: Memory Leak With (dlb) Pseudodevice Driver

State: Existing

This patch fixes a memory leak problem that occurs with the STREAMS DATA Link Bridge (dlb) pseudodevice driver. This problem could cause a "freeing free mbuf" panic when system memory is exhausted.

Patch 251.00

OSF410-400337

Patch: doconfig Utility Correction

State: Existing

This patch fixes a problem that causes the 'doconfig' program to hang when invoked by the uuxqt program.

Patch 252.00

OSF410-400340

Patch: date Command Correction

State: Existing

This patch fixes the problem in which 'date' command is unable to set the date to January 1, 1970 00:00:00 GMT or February 29, 2000.

Patch 261.00

OSF410-400359

Patch: auditmask Utility Correction

State: Existing

This patch fixes a problem that affects systems running the audit subsystem. When reading directives from a file, the auditmask utility does not correctly handle lines formatted as follows:

event    fail

Patch 275.00

OSF410CDE-400011

Patch: dtmail Correction

State: Existing

This patch lets dtmail correctly display Japanese and Korean mail messages that do not have a Content-Type header.

Patch 276.00

OSF410X11-400018

Patch: X server Correction

State: Existing

The X server can loop or run out of sockets when dealing with a font server.

Patch 278.00

OSF410DX-400012

Patch: Security, (SSRT0514U)

State: Existing

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.

Patch 489.00

OSF410-400416

Patch: who Command Correction

State: Existing

This patch fixes a problem that occurs when more than 140 users are logged on to a system and the who command is issued. If the output from the command is redirected or piped, the last several lines become corrupt.

Patch 498.00

OSF410-400429

Patch: pcnfsd Correction

State: Existing

This patch provides the followig bug fixes and performance enhancements:

  • When signals causing pcnfsd to terminate or when a SIGPIPE signal was not caught, pcnfsd would exit without producing a core file.

  • The pcnfsd authentication would cause crashes and memory corruption.

Patch 503.00

OSF410-400438

Patch: Segfaults In nm For C++ Compiler Correction

State: Existing

This patch fixes segfaults in nm for object files generated by the C++ compiler.

Patch 512.00

OSF410-400455

Patch: lex Command Correction

State: Existing

This patch fixes a problem with the lex command. Programs built with lex may exhibit various problems which only occur after the following warning:

Maximum token length exceeded

Patch 519.00

OSF410-400465

Patch: LSM volsave Command Correction

State: Existing

This patch fixes a problem with the LSM volsave command. The volsave command returns an exit status of 1 (failure), even when the LSM configuration is successfully saved.

Patch 529.00

OSF410DX-400015

Patch: Security (SSRT0435U)

State: Supersedes patches OSF410DX-400006 (72.00), OSF410DX-400009 (203.00), OSF410DX-400011 (205.00)

This patch corrects the following:

  • 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.

  • Fixes a problem that occurs on systems that have installed DIGITAL UNIX V4.0B Patch 72.00 (OSF410DX-400006). If more than one argument is given on the dop command line, dop passes all arguments as a single argument to the command.

  • The startup of nissetup, latsetup and btcreate /etc/doprc entries via the dop command fails with exit code of 2.

Patch 534.00

OSF410-400473

Patch: DEC C Compiler Correction

State: Supersedes patches OSF410-400149 (42.00), OSF410-400187 (79.00), OSF410-400257 (151.00)

This patch corrects the following:

  • Fixes a DEC C compiler problem that occurred when compiling a structure tag whose length exceeded 256 characters.

  • Provides a new version of the DEC C compiler to fix QAR 49944. It fixes a problem that causes the compiler to generate incorrect code for switch statements whose expression is of type short or type char.

    The version of this fixed compiler is DEC C V5.2-035.

  • Fixes the following DEC C compiler problems:

    • "Assertion failure: Compiler internal error" compiler crash that occurs when compiling xemacs.

    • "Invalid expression" error with valid token-pasting macro.

    • "Fatal: memory access violation" compiler crash when the left side of a structure pointer operator (->) was not an lvalue. This case should produce a compiler error.

  • A compiler code generation problem that caused incorrect code for a left shift on a signed int when compiled in ANSI (-std or -std1) compilation modes.

  • A problem where a structure return temporary is not preserved until later used in an enclosing funtion call; originally reported in the comp.UNIX.osf.osf1 newsgroup.

  • A "GEM ASSERTION, Compiler internal error" problem when compiling a complex conditional expression with -O0.

Patch 536.00

OSF410-400478

Patch: DIGITAL UNIX LAT Correction

State: Existing

When printing using DIGITAL UNIX LAT (V4.0 or later) to a printer connected to a PC running Pathworks, "I/O error" is displayed and nothing is printed.

Patch 549.00

OSF410-405135

Patch: Alpha VME 4/2xx System Panic Correction

State: Supersedes patch OSF410-127 (420.00)

This patch corrects the following:

  • Fixes a problem that occurs when fatal system and processor machine check information is not displayed to the console terminal.

  • Fixes a problem that occurs on Alpha VME 4/2xx systems. The system may panic and display the following error message:

     kernel access memory fault

Patch 565.01

OSF410X11-405008-1

Patch: Memory Leak in X server ListExtensions() Correction

State: Existing

This patch fixes a memory leak in the X server when processing ListExtensions() requests. This problem is seen in particular on systems with a PowerStorm 4D51T graphics card.

Patch 574.01

OSF410-160-1

Patch: New Command, filterlog on AlphaServer 8200/8400

State: Supersedes patch OSF410-150 (567.00)

This patch corrects the following:

  • Fixes a problem specific to the AlphaServer 8200/8400 in which the binary.errlog file becomes corrupt. The following error message is displayed:

    620 System Correctable Error

  • Provides a new command, filterlog, which improves error reporting on AlphaServer 8200/8400 systems.

Patch 590.01

OSF410-405157-1

Patch: lpd Line Printer Daemon Correction

State: Existing

Fixes a problem with the lpd line printer daemon. When "/sbin/init.d/lpd stop" is followed right away by "/sbin/init.d/lpd start", the new lpd fails to start. The error message from syslog is:

/usr/spool/lpd.lock: locking failed: Operation would block

Patch 607.01

OSF410-405193-1

Patch: Security, (SSRT0456U)

State: Supersedes patch OSF410-400412 (487.00)

This patch corrects the following:

  • 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.

  • The rpc.statd process would sometimes disappear without a trace. The fix is to ignore SIGPIPEs (triggered by statd behaviour). Also, this patch catches and logs other signals that would otherwise make rpc.statd disappear without a trace.

Patch 615.01

OSF410-405208-1

Patch: FDDI Driver Reset And Initialization Fix

State: Supersedes patches OSF410-400225 (120.00), OSF410-400409 (392.00), OSF410-400467 (521.00)

This patch corrects the following:

  • An upgrade/replacement for the "FTA" FDDI driver and fixes a DMA Error which can occur with the older driver. If it became necessary to back out a partially constructed frame from the transmit queue, the older driver was unable to properly backed out the frame before restarting. This resulted in the following errors being logged to the /var/adm/messages file:

     vmuni v40asupportos-195-nadeemx: fta0: Halted.
     vmunix: fta0: Link Unavailable.
     vmunix: fta0: Link Available.

  • Resolves a problem in the FDDI driver during device reset and initialization.

  • Fixes a kernel memory fault caused by the fta FDDI driver.

  • Corrects a problem with the FDDI fta driver.

Patch 629.01

OSF410-405218-1

Patch: ncheck Utility On AdvFS Correction

State: Existing

This patch fixes an AdvFS problem. When running the ncheck utility with the -s option on an AdvFS file system, the command never returns but instead justs keeps using cpu cycles. This problem only occurs when there are no special files in the file system.

Patch 645.01

OSF410-405244-1

Patch: kdbx mbuf And Socket Extension Correction

State: Existing

Corrects a problem with the kdbx mbuf and socket extensions. The use of these extensions on some crashdumps resulted in errors and would hang.

Patch 665.01

OSF410CDE-405003-1

Patch: dtbuilder Core Dump Correction

State: Supersedes patch OSF410CDE-400010 (161.00)

This patch corrects the following:

  • The application builder (dtbuilder) core dumps when changing the default button in the revolving property editor.

  • Fixes a segmentation fault in dtbuilder that occurs when a user tries to generate code using a 'When: Dragged From' action in conjunction with the 'list' object type.

Patch 666.01

OSF410CDE-405004-1

Patch: xset Command Correction

State: Existing

This patch fixes a problem where the xset command could not clear the screen saver under CDE.

Patch 670.01

OSF410-405211-1

Patch: /sbin/loader Corrections

State: Supersedes patch OSF410-400152 (45.00)

This patch corrects the following:

  • Fixes a problem that may cause /sbin/loader to fail to resolve duplicate symbols in dlopen'ed shared libraries.

  • Addresses two issues with the /sbin/loader:

    • Fixes an infinite loop in /sbin/loader.

    • Changes the /sbin/loader so that it now reports the names of unresolved symbols in a shared library which is opened by a dlopen() call.

Patch 687.00

OSF410CDE-405008B

Patch: CDE dtterm Correction

State: Supersedes patches OSF410CDE-400004 (65.00), OSF410CDE-400012 (523.00), OSF410CDE-400014B-1 (683.01), OSF410CDE-400014 (525.00)

This patch corrects the following:

  • Users appear to be logged in when they are not because CDE dtterm sometimes doesn't reset the utmp entry on exit.

  • When running the Common Desktop Environment (CDE), a dtterm window in which vi is being used can hang when doing a cut and paste operation from a second window.

  • Provides the ability to let dtterm display all the characters in the PC PC codeset IBM-850.

  • Fixes a problem in which the dtterm Terminal Emulator fails to send the "DO" and "HELP" User Defined Keys when depressed. It also fixes a problem in which proper escape sequences for "F10", "DO", and "HELP" were not being reported when the keys were depressed.

Patch 688.00

OSF410CDE-405010

Patch: CDE Calendar Manager fixes (rpc.cmsd and dtcm)

State: Existing

This patch fixes the following problems with the CDE Calendar Manager:

  • The calendar manager service daemon (rpc.cmsd) core dumps when processing a calendar database file containing invalid entries. These invalid entries would include "remove" entries that specify non-existent keys.

  • Repeating appointments with a frequency of daily are sometimes displayed incorrectly by the calendar manager (dtcm). Some appointments are displayed an hour earlier or an hour later than originally scheduled.

  • The calendar manager (dtcm) will complain that it cannot connect to the calendar manager service daemon (rpc.cmsd) and rpc.cmsd will repeatedly start and die with constantly changing pids.

Patch 690.00

OSF410CDE-405005

Patch: dxkeyboard Application Modification

State: Existing

This patch installs a modified dxkeyboard application that correctly loads the XKB keymap for the Hebrew LK401 keyboard so that the Ctrl+Hebrew toggle key works in a DECterm window.

Patch 691.00

OSF410CDE-405006

Patch: CDE Window Manager Corrections

State: Supersedes patch OSF410CDE-400005 (66.00)

This patch fixes the following problems:

  • Fixes two problems with the CDE window manager:

    • In the first problem, the CADDS5 (a third party cad tool) text window tends to walk off the screen.

    • In the second problem, the CDE icon box moves 29 pixels higher along the x axis each time the user's home session is resumed.

  • Fixes a problem in which deleting applications (icons) from some subpanels hangs the CDE Window Manager. The subpanels affected are "Calendar," "Mail," and "Desktop Style" subpanels.

Patch 692.00

OSF410CDE-405007

Patch: Security, (SSRT0438U)

State: Supersedes patch OSF410CDE-400007 (93.00)

This patch fixes the following problems:

  • 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.

  • Fixes a problem in which the CDE file manager (dtfile) fails to open files that use dtpad as the exec'd action. This includes both double-clicking on the file and using 'Open' from the 'Selected' pulldown menu.

Patch 693.01

OSF410CDE-405008-1

Patch: CDE dtterm Correction

State: Supersedes patches OSF410CDE-400004 (65.00), OSF410CDE-400012 (523.00), OSF410CDE-400014 (525.00)

This patch corrects the following:

  • Users appear to be logged in when they are not because CDE dtterm sometimes doesn't reset the utmp entry on exit.

  • When running the Common Desktop Environment (CDE), a dtterm window in which vi is being used can hang when doing a cut and paste operation from a second window.

  • Provides the ability to let dtterm display all the characters in the PC PC codeset IBM-850.

  • Fixes a problem in which the dtterm Terminal Emulator fails to send the "DO" and "HELP" User Defined Keys when depressed. It also fixes a problem in which proper escape sequences for "F10", "DO", and "HELP" were not being reported when the keys were depressed.

Patch 694.00

OSF410CDE-405009

Patch: dtcm (CDE) Calendar Manager Correction

State: Existing

This patch fixes a problem where the Common Desktop Environment (CDE) calendar manager (dtcm) will hang if you enter an appointment 25 days or more in advance when there are no intervening appointments.

Patch 699.00

OSF410DX-405009

Patch: dxdiff Command Correction

State: Existing

This patch fixes a problem where dxdiff will core dump when comparing files with long lines.

Patch 707.00

OSF410-405258

Patch: FDDI Memory Leak Correction

State: Supersedes patches OSF410-400275 (182.00), OSF410-400330 (250.00), OSF410-405186-1 (614.01)

This patch corrects the following:

  • Fixes memory leaks with the FDDI and Token Ring method routines used with Extensible SNMP subagent (ESNMP).

  • The SNMP agent returns incorrect data when requested for the MIB II Address Translation Table (atTable). The agent returns correct data for ipNetToMediaTable, which supercedes atTable in MIB II.

    This patch removes support for atTable, so that common applications (like NetView autodiscovery) will use the ipNetToMediaTable instead.

  • Fixes the os_mibs source file, hrm_fs.c, which makes a call to the statfs function with 2 arguments, when statfs expects 3 arguments.

  • Fxes the problem where a malformed trap message sent at boot-time by the DIGITAL UNIX SNMP daemon to a Windows NT Network Management Station (NMS) could cause the NMS application or the NT operating system to crash.

Patch 710.00

OSF410-405262

Patch: ed Editor Correction

State: Existing

This patch fixes a problem in which the ed command when used with the -G option prints extra characters.

Patch 713.00

OSF410-405266

Patch: ld -r Changes Symbol Preemption Correction

State: Supersedes patches OSF410-400174 (59.00), OSF410-400375 (273.00), OSF410-405212-1 (626.01)

This patch corrects the following:

  • Fixes a problem where use of "ld -r" will change symbol preemption behavior.

  • Fixes four linker problems: Hidden/export symbols, Assert getting generated with R_GPVALUE relocations, improper Text segment alignment processing, and linker memory managment problem processing C++ symbols.

  • Fixes a problem in the streams code which could have resulted in data corruption.

  • Fixes a problem where the linker might crash when printing out lengthy error diagnostics.

  • Fix for a linker problem that could cause incorrect symbol resolution in call_shared applications. The result is the application may use a shared library's version of a symbol rather than a symbol with the same name defined in the application.

Patch 717.00

OSF410-405273

Patch: AdvFS boot Correction

State: Existing

This patch fixes a problem in which AdvFS boot code has trouble traversing symbolic links.

Patch 722.01

OSF410-405279-1

Patch: Security, ftp Command (SSRT0505U)

State: Supersedes patches OSF410-400144 (38.00), OSF410-400396 (482.00), OSF410-400150 (43.00), OSF410-405188 (597.00), OSF410-405161-1 (588.01)

This patch corrects the following:

  • Fixes a problem with the ftp command. If you ftp to an IBM MVS system using the IP address, the IBM system will refuse the connection. This problem can be encountered on any system that validates TOS (Type Of Service) requests if the file /etc/iptos is not used on the client.

  • 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.

  • Fixes hang conditions experienced with the following networking commands and utilities rsh(1) telnet(1) ftp(1) rdate(8) |ping(8) and yppush(8).

  • Corrects a regression problem with the rsh(1) command.

  • Fixes a problem where telnet dumps core if the USER environment variable is the last variable in the enviroment list.

  • Corrects a problem with rsh(1) that is most visible with long-distance (slow) links where a packet might get dropped.

Patch 729.00

OSF410-405290

Patch: last Command Corrections

State: Existing

This patch fixes a problem with the last(8) command. Users that have logged out of a system are still listed as active in the /var/adm/wtmp accounting file.

Patch 732.01

OSF410-405295-1

Patch: lpq Command Correction

State: Existing

This patch contains many fixes to improve the reliability and efficiency of DIGITAL UNIX print services.

Patch 735.00

OSF410-405300

Patch: find Command Correction

State: Supersedes patch OSF410-400379 (484.00)

This patch fixes the following problems:

  • Fixes various problems with the find command.

  • Fixes the "find" command in which files in directories which were mounted with the "-fstype nfsv2" argument were not found.

Patch 743.00

OSF410-405311

Patch: mailx Command Correction

State: Supersedes patch OSF410-400172 (57.00)

This patch fixes the following problems:

  • Fixes two problems with the mailx command.

  • 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.

Patch 754.00

OSF410-405329

Patch: Security (SSRT0548U, SSRT0412U)

State: Supersedes patch OSF410-405264 (712.00)

This patch fixes the following:

  • Fixes a problem with the tip command. A user can not escape to a local shell from tip when using csh.

  • A potential security vulnerability has been discovered in the 'tip' command, where under certain circumstances users may gain unauthorized access. Compaq has corrected this potential vulnerability.

Patch 759.00

OSF410-405336

Patch: LEX Correction

State: Supersedes patch OSF410-400177 (73.00)

This patch fixes the following problems:

  • Fixes a LEX problem. Without this patch, LEX rejects quoted regular expressions where the ending quote is preceded by a double backslash backslash, as in:

    "\\"xxx"

    and produces the following message:

     "lex:(Warning at line 8)Non-terminated string"

  • Fixes a problem in lex that causes it to not recognize the end of a comment when the final "/" is preceded by more than one consecutive "*".

Patch 761.00

OSF410-405338

Patch: Line Printer Performance Fix

State: Existing

This patch fixes a problem with the performance of some line printers on a 4100 cpu.

Patch 767.00

OSF410-405346

Patch: System Crashes

State: Existing

This patch fixes a problem where the machine server system calls are not being type checked properly, potentially causing system crashes by unprivileged programs.

Patch 771.00

OSF410-405353

Patch: dd Command Correction

State: Supersedes patches OSF410-400211 (101.00), OSF410-400211-1 (101.01), OSF410-400211-2 (232.00), OSF410-405195-1 (618.01)

This patch corrects the following:

  • Fixes a problem in which the dd command can corrupt output on very large files (2GB or greater) when the "conv=sparse" option is used.

  • Fixes a problem that occurs with the dd command. When the seek option to the dd command is used to insert data into an existing output file, the resulting file is incorrect and all of the original data is lost.

  • Fixes a problem with the dd command in which dd aborts after a read error. This problem occurs even when the "conv=noerror" parameter is specified.

Patch 775.00

OSF410-405359

Patch: advscan Command Correction

State: Supersedes patch OSF410-405263 (711.00)

This patch fixes the following:

  • Fixes a problem caused by the advscan -r command. The command would link LSM volumes to the raw device instead of the block device when it attempted to recreate LSM volume links. As a result, the directory for the domain name in the /etc/fdmns file was incorrect and data corruption occurred.

  • Fixes a problem in which the "advscan -a" command causes a memory fault (core dump) while processing LSM volumes.

Patch 776.00

OSF410-405360

Patch: expr Command Correction

State: Existing

This patch fixes a problem with the expr command in which the leading zeros are truncated if CMD_ENV is set to bsd.

Patch 777.00

OSF410-405361

Patch: faa FDDI Driver Kernel Memory Fault Correction

State: Supersedes patches OSF410-400280 (183.00), OSF410-405196 (702.00)

This patch fixes the following problems:

  • Fixes a kernel memory fault caused by the faa FDDI driver. The panic was due to incomplete handling of an error condition by them driver ("Timeout in command request"). The command request buffer was freed; however, the reference to it was not removed from the command request list. When this list was later accessed, the invalid memory reference panic occurred.

  • Fixes a kernel memory fault in faa_service_rcv_q() in the faa FDDI driver.

  • Fixes a problem in which a system with a FutureBus+ FDDI adapter experiences problems when a command issued to the adapter fails.

Patch 784.00

OSF410-405369

Patch: rpc.lockd Correction

State: Supersedes patches OSF410-400246 (142.00), OSF410-405178-1 (605.01)

This patch fixes several problems with the network lock daemon, rpc.lockd:

  • NFS mounted file systems may hang.

  • An error occurs with NFS mounted user mail files. This error prevents the files from being locked and prints out the following message:

    cannot lockf

  • An NFS problem may occur. The system displays the following error message:

    NFS error 48 cannot bind sockets

  • Addresses various rpc.lockd problems.

  • Corrects two problems:

    • Moves locked files from the message queue to the held list once.

    • Adds code to allow locked files leftover from a server reboot, to timeout and be transmitted to the server.

Patch 785.00

OSF410-405370

Patch: SMP System Hang When Calling the flock Function

State: Existing

This patch fixes a problem that can cause calls to flock() to hang a process on an SMP system if two or more processes are attempting to obtain and release an flock() on the same file.

Patch 787.00

OSF410-405372

Patch: rdist Utility Correction

State: Supersedes patch OSF410-400424 (493.00)

This patch fixes the following problems:

  • Fix for rdist utility to prevent segmentation fault.

  • Fixes a problem where rdist dumps core when trying to copy a partition using the rdist command.

Patch 789.00

OSF410-405375

Patch: rmfdmn Command Correction

State: Supersedes patch OSF410-405314 (745.00)

This patch fixes the following:

  • Fixes a problem with the rmfdmn command, which previously displayed success messages on the standard error device instead of the standard output device.

  • Fixes a problem with the rmfdmn command. The command would fail when it attempted to rename the domain to be deleted, so the domain was not deleted. However, the command returned success for the operation.

Patch 791.00

OSF410-405377

Patch: Pseudo TTY Corrections

State: Supersedes patches OSF410-400092 (13.00), OSF410-405042 (31.00)

This patch corrects the following:

  • Fixes a problem that causes the system to "assert_wait" panic and the stack contains streams modules.

  • A problem where a remote user will kill rlogin or telnet and the server host will have an orphaned login process and rlogind or telnetd process in sleep state indefinitely. This is seen only with Asian tty (atty) or any other host which is running c-list rather than STREAMS tty's.

  • Fixes a panic caused by freeing a pty on a reopen of the controlling tty.

Patch 795.00

OSF410-405382

Patch: showfile Command Correction

State: Existing

This patch fixes a problem with the showfile command, which incorrectly returned an error status when it attempted to display a file that was a symbolic link.

Patch 799.00

OSF410-405387

Patch: cron Command Correction

State: Supersedes patch OSF410-400194 (83.00)

This patch fixes the following problems:

  • Fixes a problem in which the cron command deletes non-local file system files mounted in either the /tmp, /var/tmp, or /var/preserve directories.

  • Prevents the crontab file from incorrectly deleting files found in file systems mounted under the /var/preserve, /tmp, and /var/tmp directories.

Patch 801.00

OSF410-405390

Patch: diskx Command Correction

State: Existing

This patch corrects the following problems:

  • Fixes a problem in which the /usr/field/diskx command fails with data validation errors when specifying a block device special file for testing.

  • Provides diskx with the ablity to test 9 Gigabyte drives and provides added flexibility in diagnosing hardware problems.

Patch 805.00

OSF410-405395

Patch: Security (SSRT0448U, SSRT0452U)

State: Supersedes patches OSF410-400167 (52.00), OSF410-400428 (497.00)

This patch corrects the following:

  • 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.

  • Fixes a problem with the ftp daemon, ftpd, and its use of authenticated user information. The daemon was using incorrect information for logging and validation of usernames.

Patch 811.00

OSF410-405406

Patch: Security, sendmail (SSRT0421U)

State: Supersedes patch OSF410-400160-1 (49.01)

This patch corrects the following:

  • A potential security vulnerability has been discovered with the sendmail command, where under certain circumstances, users may gain unauthorized access. Compaq has corrected this potential vulnerability.

  • Fixes a problem with the sendmail program. Sendmail would dump core and not process any more jobs in the queue when it encountered control characters in a qf file.

Patch 814.01

OSF410-405411-1

Patch: library clock_settime Correction

State: Supersedes patch OSF410-400215 (108.00)

This patch fixes the following:

  • When setting the date with the clock_settime rtl service routine, the date will not get past the date of "Sat Sep 8 19:46:39 2001". If you try to set past this date the routine returns a EINVAL error.

  • Fixes the following two problems with realtime library:

    • A locking problem when calling sem_close() with an invalid descriptor.

    • A memory leak.

Patch 818.00

OSF410-405418

Patch: dbx Correction

State: Supersedes patches OSF410-400205 (90.00), OSF410-405257 (706.00), OSF410-405413 (816.00)

This patch fixes the following problems:

  • Fixes a problem that causes dbx to hang when stepping past a system() function call.

  • Fixes a dbx problem with listing a large FORTRAN program that contains alternate entry points.

  • Fixes a problem with dbx when debugging programs that have large source files. In some cases dbx may abort with a segmentation fault.

  • Fixes a problem with dbx. A segmentation fault may occur when displaying an array or when showing the type and dimensions of an array.

Patch 826.00

OSF410-405433

Patch: Lock Timeout/Kernel Memory Fault On 8200/8400s

State: Supersedes patch OSF410-405246-1 (664.01)

This patch fixes the following problems:

  • Fixes a problem on DIGITAL's 8200/8400 machines where cpus may be bombarded with interrupts. The high amount of interrupts may cause simple lock timeouts and kernel memory faults.

  • Fixes the following problems found on AlphaServer 8400/8200 class machine:

    • A system hang or error messages being printed to the console. This is seen when a loadable driver is unloaded.

    • A pcia error system panic or machine check.

Patch 836.00

OSF410-405447

Patch: Kernel Build config Command Correction

State: Existing

This patch fixes a problem in which the kernel build config command (obj/alpha/kernel/bin/config) core dumps if the fopen function fails.

Patch 838.00

OSF410-405449

Patch: Bourne Shell Performance Improvement

State: Existing

This patch fixes a problem where the performance of the Bourne shell may be slow when there are many automounted directories in the search path (as defined by the PATH environment variable).

Patch 840.00

OSF410-405451

Patch: Audit Record Correction

State: Existing

This patch fixes a problem in which audit records are generated for selected operations against objects that are not in the filesystem.

Patch 841.01

OSF410-405453-1

Patch: Curses Library Correction

State: Existing

This patch fixes a problem with the curses library. The infocmp command dumped core because two curses terminal capability tables were out of sync with each other.

Patch 842.00

OSF410-405454

Patch: EISA Bus Handling Corrections

State: Supersedes patch OSF410-400170 (55.00)

This patch fixes two problems that occur on systems with an EISA bus:

  • A system running four DE425 adapters off an EISA bus may hang.

  • If a device's EISA configuration file contains a function DISABLE keyword and the DISABLE option is selected, the device's driver may not be configured and probed at bus configuration time.

  • Fixes a problem in which EISA/ISA buses do not correctly match functions for loadable drivers.

  • EISA configuration code returns a non-null Function_Name field for the token ring card. This field is ignored if the driver is configured statically. However, when configured dynamically, scan_eisa_slot attempts to exactly match whatever is specified in the sysconfigtab entry with what is returned by the token ring card.

Patch 845.01

OSF410X11-405011-1

Patch: xterm Correction, Security (SSRT0422U, SSRT0547U)

State: Supersedes patches OSF410X11-400010 (29.00), OSF410X11-400017 (206.00), OSF410X11-400021 (386.00)

This patch corrects the following:

  • Fixes a problem in which the output of the "last" or "finger" command lists users that are not currently logged in.

  • 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.

  • Fixes a memory leak in Xlib when using fonts in an international (I18N) environment. This problem affects Netscape Navigator in particular.

Patch 847.00

OSF410X11-405013

Patch: Screen Flickers In Power_Save Mode Correction

State: Supersedes patches OSF410X11-400013 (104.00), OSF410X11-400014 (131.00), OSF410X11-405012 (846.00)

This patch corrects the following:

  • On systems with PowerStorm 4D40T, 4D50T, or 4D60T graphics options, the X server may hang every 49 days.

  • Screen flickers on and off when in power-save mode.

  • Fixes a problem where the X server may generate a core dump during shutdown on a dataless management services (DMS) client system.

  • Fixes a problem that prevents an X server from starting. The following error message is displayed:

    Fatal server error:
    Cannot establish any listening sockets.
    Make sure an X server isn't already running.

Patch 848.00

OSF410DX-004

Patch: (svrServer_mib) Correction

State: Existing

This patch corrects the following error message seen in the daemon.log file:

svrSystem_mib[1434]:svrSystem_mib **ERROR esnmp_poll.c line 685:
Method routine returned invalid status:2

Patch 852.00

OSF410-166

Patch: AlphaStation 255 Hangs Or Crashes When Rebooted

State: Supersedes patch OSF410-140-1 (556.01)

This patch fixes the following problems:

  • Fixes a problem in which the AlphaStation 255 will either hang or crash when the system is rebooted.

  • Fixes a problem with the KZPAA driver not recognizing an optical jukebox.

Patch 854.01

OSF410-169-1

Patch: AdvFS rmvol Command Fix

State: Existing

This patch fixes an AdvFS problem that occurs when the rmvol command is stopped before the command successfully removes a volume from a domain. As a result, the showfdmn and addvol commands interpreted the volume as still in the domain (although with no data available) and a balance operation returned the following AdvFS error message:

get vol params error EBAD_VDI (-1030)

Patch 865.00

OSF410-188

Patch: Default C Compiler Correction

State: Supersedes patches OSF410-124 (417.00), OSF410-173 (857.00)

This patch fixes the following problems:

  • Fixes a problem that occurs when the default C compiler is used to compile a program using the following switches on the command line: -c -compress -fast.

  • Implements a new cc switch to allow the passing of the ld "-input file" switch to the linker via cc, without changing its relative position in the ld command line. The current method for doing this (-Wl,-input,filename) changes the order in which such a file is presented to the linker, and can result in an invalid transfer address in an executable, resulting in a segmentation fault.

  • Fixes a problem in cc that causes it to set the incorrect optimization level when the user specifies the "-O -migrate" options.

Patch 868.00

OSF410-192

Patch: Print To Console Terminal Correction

State: Supersedes patches OSF410-139-1 (555.01), OSF410-191 (867.00)

This patch fixes the following problems:

  • Fixes a problem for several platforms that do not print to the console terminal during a panic correctly. The particular platforms involved are AlphaStation 600, AlphaPC 164, AlphaServer 1000A 5/XXX, AlphaServer 1000 5/XXX, AXPvme 100 SBC, and DIGITAL Personal Workstation 433au, 500au, 600au.

  • Fixes a problem in which correctable memory errors are being logged to the system console as well as to the binary error log.

  • Fixes a problem that can cause bad pages to not be flagged during memory testing.

Patch 873.00

OSF410-198

Patch: syslogd Corrections, Security (SSRT0499U)

State: Supersedes patches OSF410-088 (174.00), OSF410-119 (425.00), OSF410-119-1 (425.01), OSF410-142-1 (558.01)

This patch corrects the following:

  • Fixes a problem in which the syslogd program cannot properly forward large messages to remote systems. It will either write them to the wrong facility (specified in /etc/syslog.conf) or write incomplete data.

  • 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.

  • This patch fixes a problem in which the syslogd daemon may hang when writing to a named pipe log file.

  • Fixes a problem in which syslogd will core dump if /etc/syslog.auth file has greater than 23 lines.

Patch 875.00

OSF410-200

Patch: Compiler Correction

State: Existing

This patch fixes a compiler problem that was causing CPU EXCEPTION errors to be generated in the system binary error log. The problem was experienced during bootstrap on 2100A cpus.

Patch 881.00

OSF410-210

Patch: cpio Command Correction

State: Supersedes patches OSF410-065 (122.00), OSF410-138 (554.00), OSF410-152 (568.00), OSF410-405149-1 (604.01), OSF410-165 (851.00), OSF410-186 (863.00)

This patch corrects the following:

  • Fixes a problem with the cpio command in which cpio fails to create multiple archives on 150 MB or 250 MB tape.

  • Fixes a problem where during tape operations, the SPACE commands can not be interrupted.

  • Fixes a problem in which a system panics with a "kernel memory fault" error message. The problem occurs when a tape drive is plugged into the slot previously occupied by a disk.

  • Fixes a problem where during tape operations, the SPACE commands can not be interrupted.

  • Corrects a problem where the code around referencing a tape device pointer is not synchronized and a kernel memory fault results.

  • Fixes an ASE NFS problem that occurs on ASE systems with KZPBA disk controllers. The system crashes with a "simple_lock timeout" panic.

  • Under certain conditions, the message "ctape_strategy: READ case and density info not valid" was being printed for every read from tape. This change will print the message only once.

Patch 887.00

OSF410-405453B

Patch: Curses Library Correction

State: Existing

This patch fixes a problem with the curses library. The infocmp command dumped core because two curses terminal capability tables were out of sync with each other.

Patch 888.00

OSF410-405328B

Patch: acctcom Command Correction

State: Supersedes patch OSF410-400230 (127.00)

This patch fixes the following:

  • Fixes a problem in which the size field of a process displayed by the acctcom command is displayed incorrectly.

  • Corrects a small accounting problem where the measured time for a process was an integral rather than mean value.

Patch 889.00

OSF410-405411B

Patch: library clock_settime Correction

State: Supersedes patches OSF410-400215 (108.00), OSF410-400215B (682.00)

This patch fixes the following:

  • When setting the date with the clock_settime rtl service routine, the date will not get past the date of "Sat Sep 8 19:46:39 2001" If you try to set past this date the routine returns a EINVAL error.

  • Fixes the following two problems with realtime library:

    • A locking problem when calling sem_close() with an invalid descriptor.

    • A memory leak.

Patch 895.00

OSF410-405403C

Patch: Header File Corrections, Security (SSRT0296U)

State: Supersedes patches OSF410-400239-1 (136.01), OSF410-400331-1 (219.01), OSF410-400331-3 (227.00), OSF410-999 (407.00), OSF410-405440C (893.00)

This patch contains changes to header files contained in the optionally loaded OSFINCLUDE410 subset. The following problems were corrected in the header files:

  • A potential security vulnerability has been discovered in BIND, 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.

  • Allows customers to create hashed passwd databases from large passwd files by using a new option (-s) to the mkpasswd command. The -s option increases the block size of the database page file.

  • Fixes a problem in which multithreaded applications that reference a pthread_mutex_destroy routine may fail with EBUSY or the application may hang.

  • Fixes libtli/libxti to correctly handle a continuation data message still on the stream head.

Patch 897.00

OSF410-405295B

Patch: lpq Command Correction

State: Supersedes patch OSF410-400290 (193.00)

This patch fixes the following problems:

  • Fixes a problem where the lpq command causes the program to crash (Memory fault).

  • Fixes to improve the reliability and efficiency of DIGITAL UNIX print services.

Patch 898.00

OSF410-400331E

Patch: OSFSCCS Subset Command Correction

State: Supersedes patches OSF410-400331 (219.00), OSF410-400331C (225.00), OSF410-400331C-1 (235.00)

This patch allows the OSFSCCS subset commands to work correctly when the customer builds a hashed passwd database using a non-default page file block size.

Patch 899.00

OSF410X11-400019B

Patch: DECwindows Motif Toolkit

State: Supersedes patch OSF410X11-400019 (277.00)

This patch fixes the following problem in the Bookreader library, which is part of the DECwindows Motif toolkit.

When called from an application, Bookreader changes the caller's effective UID to the real UID, but then never restores it to the original effective UID before returning control to the calling program. If an application like dxchpwd is run from a non-root account, it fails with a privilege violation.

Patch 900.00

OSF410-400468B

Patch: dtterm Displays All Characters In PC Codeset IBM-850

State: Supersedes patches OSF410X11-405007 (535.00), OSF410-400468 (551.00)

This patch provides the ability to let dtterm display all the characters in the PC codeset IBM-850.

Patch 901.00

OSF410-405279B

Patch: Security, ftp Command (SSRT0505U)

State: Supersedes patches OSF410-400144 (38.00), OSF410-400396 (482.00), OSF410-400150 (43.00), OSF410-405188 (597.00), OSF410-405161-1 (588.01)

This patch corrects the following:

  • Fixes a problem with the ftp command. If you ftp to an IBM MVS system using the IP address, the IBM system will refuse the connection. This problem can be encountered on any system that validates TOS (Type Of Service) requests if the file /etc/iptos is not used on the client.

  • 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.

  • Fixes hang conditions experienced with the following networking commands and utilities rsh(1) telnet(1) ftp(1) rdate(8) |ping(8) and yppush(8).

  • Corrects a regression problem with the rsh(1) command.

  • Fixes a problem where telnet dumps core if the USER environment variable is the last variable in the environment list.

  • Corrects a problem with rsh(1) that is most visible with long-distance (slow) links where a packet might get dropped.

Patch 903.00

OSF410X11-405011B

Patch: xterm XLIBA, Security (SSRT0422U, SSRT0547U)

State: Supersedes patches OSF410X11-400010 (29.00), OSF410X11-400017 (206.00), OSF410X11-400021 (386.00), OSF410X11-405011 (845.00)

This patch corrects the following:

  • Fixes a problem in which the output of the "last" or "finger" command lists users that are not currently logged in.

  • 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.

  • Fixes a memory leak in Xlib when using fonts in an international (I18N) environment. This problem affects Netscape Navigator in particular.

Patch 904.00

OSF410CDE-400006B-2

Patch: Security, (SSRT0498U)

State: Supersedes patches OSF410CDE-400006 (92.00), OSF410CDE-400006B-1 (679.01)

This patch fixes a problem in which users logging into a system that has a nodename longer than 32 characters cause ttsession to core dump. This only happens when using CDE desktop.

Patch 905.00

OSF410CDE-400006-2

Patch: Nodename Length Correction

State: Supersedes patch OSF410CDE-400006-1 (92.01)

This patch fixes a problem in which users logging into a system that has a nodename longer than 32 characters cause ttsession to core dump. This only happens when using CDE desktop.

Patch 906.00

OSF410-400331C-3

Patch: OSFSCCS Subset Command Correction

State: Supersedes patches OSF410-400331 (219.00), OSF410-400331C (225.00), OSF410-400331C-1 (235.00)

Allows the OSFSCCS subset commands to work correctly when the customer builds a hashed passwd database using a non-default page file block size.

Patch 907.00

OSF410-400364-1

Patch: System Run Level Correction

State: Supersedes patch OSF410-400364 (266.00)

This patch fixes two system run level problems:

  • On a system running LSM, whenever there is a run level change, the lsmbstartup script runs. This causes root to be mounted read/write in single-user mode.

  • The bcheckrc command script continues to run even if there is an invalid root entry. This leaves the system in an unusable state in single-user mode.

Patch 908.00

OSF410-400364B-1

Patch: System Run Level Correction

State: Supersedes patches OSF410-400364 (266.00), OSF410-400364B (681.00)

This patch fixes two system run level problems:

  • On a system running LSM, whenever there is a run level change, the lsmbstartup script runs. This causes root to be mounted read/write in single-user mode.

  • The bcheckrc command script continues to run even if there is an invalid root entry. This leaves the system in an unusable state in single-user mode.

Patch 910.00

OSF410-400371B-1

Patch: uprofile And kprofile Command Corrections

State: Supersedes patches OSF410-400371 (274.00), OSF410-400371B (685.00)

This patch corrects the following problems:

  • The uprofile and kprofile commands report incorrect statistics on an SMP system or when trying to measure EV5 events other than cycles.

  • The pfm driver ioctl PCNT5GETCNT returns incorrect data.

  • An unstoppable stream of pfm interrupts is produced if an EV5 machine is rebooted with the pfm driver active.

  • The pfm(8), uprofile(1), and kprofile(1) manpages do not describe the EV5 statistics supported by the software.

All users of the pfm driver and uprofile or kprofile commands should install this patch.

Patch 911.00

OSF410X11-400019-1

Patch: DECwindows Motif Toolkit

State: Supersedes patch OSF410X11-400019 (277.00)

This patch fixes the following problem in the Bookreader library, which is part of the DECwindows Motif toolkit.

When called from an application, Bookreader changes the caller's effective UID to the real UID, but then never restores it to the original effective UID before returning control to the calling program. If an application like dxchpwd is run from a non-root account, it fails with a privilege violation.

Patch 912.00

OSF410-400365-1

Patch: btree File Format Correction

State: Supersedes patch OSF410-400365 (406.00)

This patch fixes a problem that affects systems using databases with the btree file format. Only applications using btree in libdb.a or libdb.so are affected and may return incorrect data or crash.

Patch 913.00

OSF410-400365B-1

Patch: Library btree File Format Correction

State: Supersedes patches OSF410-400365 (406.00), OSF410-400365B (680.00)

This patch fixes a problem that affects systems using databases with the btree file format. Only applications using btree in libdb.a or libdb.so are affected and may return incorrect data or crash.

Patch 914.00

OSF410CDE-400013-1

Patch: Security, (SSRT0498U)

State: Supersedes patch OSF410CDE-400013 (524.00)

A potential security vulnerability has been discovered in "libDtSvc", where under certain circumstances users may gain unauthorized access. Compaq has corrected this potential vulnerability.

Patch 915.00

OSF410CDE-400013B-1

Patch: Security, (SSRT0498U)

State: Supersedes patches OSF410CDE-400013 (524.00), OSF410CDE-400013B (678.00)

A potential security vulnerability has been discovered in "libDtSvc", where under certain circumstances users may gain unauthorized access. Compaq has corrected this potential vulnerability.

Patch 916.00

OSF410-400468-1

Patch: dtterm Displays All Characters In PC Codeset IBM-850

State: Supersedes patches OSF410X11-405007 (535.00), OSF410-400468 (551.00)

This patch provides the ability to let dtterm display all the characters in the PC codeset IBM-850.

Patch 917.00

OSF410-405248-1

Patch: Shared libcxx Library Fix

State: Supersedes patches OSF410-400487 (538.00), OSF410-405248 (643.00)

This patch corrects the following:

  • Provides the required run-time support for images created by the DIGITAL C++ V6.0 and above compiler.

    Contact the DIGITAL C++ compiler group (cxx@lego.zko.dec.com) for details.

  • An updated libcxx.so which provides the required run-time support for images created by DIGITAL C++ V6.0 and above. Customers who are using DIGITAL C++ V6.0 can use the undocumented compiler switch:

    -use_system_libcxx

    which will cause the compiler to use the system libcxx.so file when linking.

    DIGITAL C++ V6.0 customers should only use this switch if the resulting images are to be executed either on other systems which have had the libcxx.so patch installed, or on DIGITAL UNIX 4.0D and above systems.

Patch 918.00

OSF410-405248B-2

Patch: Static libcxx Library Fix

State: Supersedes patches OSF410-400487 (538.00), OSF410-405248 (643.00), OSF410-405248B (684.00)

This patch corrects the following:

  • Provides the required run-time support for images created by the DIGITAL C++ V6.0 and above compiler.

    Contact the DIGITAL C++ compiler group (cxx@lego.zko.dec.com) for details.

  • An updated libcxx.so which provides the required run-time support for images created by DIGITAL C++ V6.0 and above. Customers who are using DIGITAL C++ V6.0 can use the undocumented compiler switch:

    -use_system_libcxx

    which will cause the compiler to use the system libcxx.so file when linking. DIGITAL C++ V6.0 customers should only use this switch if the resulting images are to be executed either on other systems which have had the libcxx.so patch installed, or on DIGITAL UNIX V4.0D and above systems.

Patch 919.00

OSF410-400362B-1

Patch: Static libm Corrections

State: Supersedes patches OSF410-400083 (12.00), OSF410-400293 (194.00), OSF410-400362 (262.00), OSF410-400362B (676.00)

This patch corrects the following:

  • Fixes the problem of the math library functions not returning the correct NaN value as defined in the Alpha AXP Architecture Reference.

  • Fixes a problem with fastmath functions F_Exp() and F_Pow() that cause floating exception core dumps.

Patch 920.00

OSF410-400362-1

Patch: libm Corrections

State: Supersedes patches OSF410-400083 (12.00), OSF410-400293 (194.00), OSF410-400362 (262.00)

This patch corrects the following:

  • Fixes the problem of the math library functions not returning the correct NaN value as defined in the Alpha AXP Architecture Reference.

  • Fixes a problem with fastmath functions F_Exp() and F_Pow() that cause floating exception core dumps.

Patch 921.00

OSF410-400371C

Patch: uprofile SDE Command Corrections

State: Supersedes patches OSF410-400371 (274.00), OSF410-400371B (685.00)

This patch corrects the following problems:

  • The uprofile and kprofile commands report incorrect statistics on an SMP system or when trying to measure EV5 events other than cycles.

  • The pfm driver ioctl PCNT5GETCNT returns incorrect data.

  • An unstoppable stream of pfm interrupts is produced if an EV5 machine is rebooted with the pfm driver active.

  • The pfm(8), uprofile(1), and kprofile(1) manpages do not describe the EV5 statistics supported by the software.

All users of the pfm driver and uprofile or kprofile commands should install this patch.

Patch 922.00

OSF410X11-405011C

Patch: xterm XDEV, Security (SSRT0422U, SSRT0547U)

State: Supersedes patches OSF410X11-400010 (29.00), OSF410X11-400017 (206.00), OSF410X11-400021 (386.00), OSF410X11-405011 (845.00)

This patch corrects the following:

  • Fixes a problem in which the output of the "last" or "finger" command lists users that are not currently logged in.

  • 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.

  • Fixes a memory leak in Xlib when using fonts in an international (I18N) environment. This problem affects Netscape Navigator in particular.

Patch 929.00

OSF410-405463

Patch: Fixes For voltrace, volsetup, & vold

State: Supersedes patches OSF410-400255 (150.00), OSF410-405412 (815.00)

This patch fixes the following problems:

  • Fixes a problem that occurs on SMP systems using LSM in which the system panics with a "simple lock time limit exceeded" message.

  • Fixes a problem in lsm. A data corruption occurs when readv/writev coallesced via physio while in read/writeback mode.

  • Corrects the following problems:

    • voltrace sometimes prints records out of sequence.

    • volsetup would fail to add disks to LSM because the volboot file is full.

    • vold would dump core when a user attempts to add a 257th configuration copy to a disk group.

Patch 931.00

OSF410-405465

Patch: Security (SSRT0565U)

State: New

A potential security vulnerability has been discovered, where under certain circumstances, a terminal session may be compromised. This may be in the form of improper file or privilege management. Compaq has corrected this potential vulnerability.

Patch 942.00

OSF410-405478

Patch: Fix For doconfig -a and -m Options

State: New. Supersedes patch OSF410-405474 (938.00)

This patch corrects the following:

  • The doconfig program incorrectly exits with a zero return code if a failure occurs.

  • Fixes the doconfig command. The -a and -m options prompt the user if doconfig encounters a failure. The -a and -m options are supposed to be non-interactive in an situation.

Patch 953.00

OSF410-405493

Patch: Security (SSRT0577U)

State: Supersedes patches OSF410-400371 (274.00), OSF410-400371-1 (909.00)

This patch corrects the following problems:

  • The uprofile and kprofile commands report incorrect statistics on an SMP system or when trying to measure EV5 events other than cycles.

  • The pfm driver ioctl PCNT5GETCNT returns incorrect data.

  • An unstoppable stream of pfm interrupts is produced if an EV5 machine is rebooted with the pfm driver active.

  • The pfm(8), uprofile(1), and kprofile(1) manpages do not describe the EV5 statistics supported by the software.

  • 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.

All users of the pfm driver and uprofile or kprofile commands should install this patch.

Patch 956.00

OSF410-405496

Patch: quotaon Cmd Returns Incorrect Error Status

State: New

This patch fixes a problem in which the quotaon command returned an incorrect error status if the file system did not exist.

Patch 957.00

OSF410-405498

Patch: KMF When Running Token Ring Adaptor & ATMworks 351

State: Supersedes patches OSF410-405043 (60.00), OSF410-405043-1 (60.01), OSF410-405127 (531.00)

This patch corrects the following:

  • Fixes a Token Ring transmission timeout. The driver can experience "ID 380PCI20001 (8/13/95)" in the TI380PCI Errata on the AlphaServer 4100 platform.

  • An upgrade/replacement for the Token Ring driver. Fixes an intermittent kernel memory fault problem. To ensure data integrity, additional enhancements to transmit and receive list processing routines have also been added.

  • Fixes a kernel memory fault that can occur when running a system with a token ring adaptor and ATMworks 351.

Patch 961.00

OSF410-405503

Patch: tcpslice Cmd Has Probs Filtering tcpdump Dump Files

State: New

This patch fixes a problem in which the tcpslice command has problems filtering tcpdump dump files when a year greater than 1999 is used as an end date.

Patch 962.00

OSF410-405504

Patch: file Cmd Interprets /etc/magic File Incorrectly

State: New

This patch corrects the behavior of the file command when a WAV audio file is specified as input.

Patch 963.00

OSF410-405506

Patch: Security, (SSRT0495U)

State: Supersedes patch OSF410-400406-1 (410.01)

This patch corrects the following problems:

  • 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.

  • The man command recognizes only ten entries in the MANPATH environmental variable. This patch removes the limit on the number of MANPATH entries.

Patch 965.00

OSF410-405510

Patch: ex And vi Editor Corrections

State: Supersedes patches OSF410-400204 (89.00), OSF410-400390 (389.00), OSF410-114 (400.00), OSF410-121 (416.00), OSF410-405327 (752.00), OSF410-405475 (939.00)

This patch corrects the following problems in the ex and vi editors:

  • Blank lines in the .exrc file prevent the vi editor from executing.

  • The ex editor does not properly manage the file name buffers when a "write append" command fails.

  • The vi editor may erroneously report a "Bad file number" error message when switching between files.

  • The vi command, "ce", does not work as expected.

  • Fixes a problem that causes the vi command to core dump. The problem occurs if one line is yanked into a named buffer. For example, the following command, which should mark the current line and copy the line into buffer "a", will generate a core dump:

    may'a

  • Fixes a problem in which the vi command, "ce", does not work as expected.

  • Fixes a problem with the vi editor envrionment variable EXINIT that occurs when EXINIT includes the editors so subcommand.

  • Corrects the following two problems which can occur when using vi to edit files 100MB or larger:

    • The terminal settings can be disrupted causing the window to be unusable.

    • A core dump may occur.

  • Fixes a problem where vi puts the server port into PASSALL MODE (where XON/XOFF is no longer effective). This creates garbage in the file.

Patch 968.00

OSF410-405514

Patch: sort Command Correction

State: Supersedes patch OSF410-405154-1 (587.01)

This patch fixes the following:

  • Fixes the error condition that the sort command may erroneously skip 8-bit characters when the -d or -i option is specified.

  • Fixes a problem in which "sort -i a_file >b_file" aborts with message "A line of the input file contains more than 20480 characters." when LANG = da_DK.ISO8859-1.

Patch 969.00

OSF410-405516

Patch: binmail Delivering Partial Mail Messages

State: New

This patch corrects a problem with binmail which was resulting in partial delivery of mail messages when account quota or disk capacity was reached.

Patch 971.00

OSF410-405518

Patch: Fix For tail Command

State: New

This patch corrects erroneous behavior when the tail command is used with both the -n and -r flags.

Patch 975.00

OSF410-405524

Patch: gzip Cmd Has Problem Uncompressing Files

State: New

This patch fixes a problem in which gzip command had problems in uncompressing files larger then 4GB.

Patch 978.00

OSF410-405532

Patch: ATM CLIP Interface May Run Out Of Memory

State: Supersedes patches OSF410-400138 (34.00), OSF410-400219 (112.00), OSF410-400288 (191.00), OSF410-400464 (518.00), OSF410-405158 (586.00), OSF410-405163 (613.00), OSF410-405164 (637.00), OSF410-405183 (610.00), OSF410-405220 (623.00), OSF410-405225 (632.00), OSF410-405234-1 (654.01), OSF410-405261 (709.00), OSF410-405294 (731.00), OSF410-405513 (967.00), OSF410-405517 (970.00)

This patch corrects the following:

  • Fixes problems in the error paths of the ATM subsystem. A majority of these result in system crashes. These crashes are most prevalent when stressing LAN Emulation (LANE).

  • Fixes two panics in the lta driver, ATM LANE interoperability problems with IBM switches, and slow recovery of UNI 3.0 signalling from network interruptions.

  • When tcpdump is run with ATM LAN emulation, a kernel memory fault occurs.

  • Fixes a problem with the ATMworks 351 (Meteor) loadable driver.

  • Fixes a problem when ATM ELANs are configured and an ATM switch reboots. This can cause a temporary connectivity problem. Hosts on Ethernet segments may not be able communicate with the DIGITAL UNIX ATM ELAN hosts until the expiration of router ARP timers.

  • Fixes a problem that occurs on a system running ATM. The system panics with a "kernel memory fault" due to a simple lock time violation.

    Prior to the crash, the pvc flag is observed as stale on a permanent virtual circuit. The crash occurs after the pvc is deleted with the following command:

    # atmconfig -pvc .....

Patch 978.00

continued

  • Fixes two kernel memory faults and a system startup crash caused by the ATM convergence subsystem.

  • Fixes the conformance problem with the DIGITAL UNIX LAN Emulation. The DIGITAL UNIX LAN Emulation client now complies with the LANE V1 spec when locating the LAN Emulation Configuration Server (LECS). The client now asks the switch via ILMI for the ATM address of the LECS.

  • ATM will fail to connect on incoming calls that are UNI version 3.1. In some cases incorrect data for the Elan name was being used. This would cause D/UNIX to try to join an invalid Elan. This fix allows the "elan_name" option to be set with the "les" option.

  • Fixes two problems in ATM. A Virtual Circuit may hang when running Classical IP under a very heavy load, and the kernel malloc pool could be corrupted, causing kernel memory faults.

  • Fixes a problem in which an ATM CLIP connection does not send data.

  • Fixes an interoperability problem with CISCO CLIP clients.

  • Fixs an ATM Lane problem where the arp table grows significantly.

  • Fixes a problem in which systems that use the DIGITAL UNIX ATM LANE interface may panic with the following message.

    kernel memory fault

  • Fixes a problem in which systems that use the Compaq Tru64 UNIX ATM CLIP interface may run out of memory.

Patch 979.00

OSF410-405533A

Patch: Fix For XTI Over TCP/IP Problem

State: Supersedes patches OSF410-400171 (56.00), OSF410-400151 (44.00), OSF410-400196 (85.00), OSF410-400264 (177.00), OSF410-400385 (485.00), OSF410-400405-1 (547.01), OSF410-405237 (655.00), OSF410-405440-1 (831.01), OSF410-405476 (940.00), OSF410-405523 (974.00), OSF410-405522A (973.00)

This patch corrects the following:

  • Fixes the problem of t_optmgmt() T_NEGOTIATE calls returning T_SUCCESS, but not actually negotiating the socket options. This behavior is a UNIX95 specification standard compliance bug.

  • Fixes a problem that manifests itself by the system hanging or becoming inoperable when a number of XTI connections reaches 500.

  • This patch resolves a hang in the xticlose() routine and a kernel memory fault in the xti_discon_req() routine.

  • Corrects a problem with the xti/streams interface module which could result in a kernel memory fault panic during use by xti application programs.

  • Fixes a mutex lock problem in TLI. The problem causes multithreaded TLI applications to block forever.

  • Fixes a problem with the implementation of the TPI interface. This problem occurs if you are using DIGITAL's XTI libxti library with a third-party (non-DIGITAL) STREAMS driver.

  • Fixes a problem that occurs on a system when running STREAMS. The system panics with the following error message:

    "kernel memory fault"

  • Fixes libtli/libxti to correctly handle a continuation data message still on the stream head.

  • Fixes a problem in which the xti_discon_ind() function allocates a data buffer for zero-length data.

  • Fixes a problem with XTI over TCP/IP when tcp_sendspace and tcp_recvspace have been decreased to 1k. When sending 4k data (using t_snd), the call is successfull but no data has been sent and no message is returned.

  • Fixes a streams problem in libxti. The t_getprotaddr() function will cause a memory core dump if either of its second or third argument is NULL.

  • Fixes a problem in which an application using the X/Open Transport Interface (XTI) and the DECnet/OSI transport provider is unable to disconnect a rejected request.

Patch 982.00

OSF410-405537

Patch: Security, (SSRT0490U)

State: Supersedes patch OSF410-400427 (496.00)

This patch fixes the following:

  • 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.

  • Fixes two restore utility problems that were causing segmentation faults. Additionally, the restore utility now uses /var/tmp for temporary files: previously, it had incorrectly used /tmp.

Patch 985.00

OSF410-405540

Patch: Fix For yacc

State: New

This patch fixes a problem in yacc that causes it to generate parse tables that result in the parser not executing a user-specified error recovery action.

Patch 987.00

OSF410-405547

Patch: Security (SSRT0487U, SSRT0567U, SSRT0583U)

State: Supersedes patches OSF410-405233-1 (649.01), OSF410-400404-1 (409.01), OSF410-405337 (760.00), OSF410-405470 (934.00)

This patch fixes the following problems:

  • 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.

  • Fixes the following problems with the "at -t" command:

    • The command did not work with user id's that were not in the password file.

    • The command did not work on the leap year of 2000.

  • Corrects several problems with the "at", "cron", and "crontab" commands.

Patch 988.00

OSF410-405548

Patch: Security (SSRT0583U)

State: New

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.

Patch 990.00

OSF410-405550

Patch: ATM Driver May Cause System Panic

State: Supersedes patches OSF410-400253 (149.00), OSF410-400286 (188.00), OSF410-400425 (494.00), OSF410-400432 (500.00), OSF410-405174-1 (595.01)

This patch corrects the following:

  • An upgrade/replacement for the OTTO/OPPO ATM driver and fixes a number flow control and signalling problems. If you are seeing "No Buffer Space" messages, experiencing pauses or hangs when receiving data on signalling/ilmi pvc's, or have any problems with FLOWMASTER flow control with CLIP or LANE over ATM, you should install this patch.

  • Contains performance enhancements to the ATM OTTO driver when greater than 300 VCs are configured. This replacement driver uses hash buckets to improve search time in the VC data structures resulting in significant performance gains.

  • On reboot, a panic could be encountered before getting into single user mode. The panic would occur inside the ltaintr routine and this routine would be noted in the dump stack trace. This problem was seen on Personal Workstation 500ua (MIATA) and the ATM 350 card.

    The second problem is a panic: thread_block: interrupt level call when rt_preempt_opt (REALTIME preemption) is enabled. A typical stack trace would look like this for the top of the stack:

    panic
    thread_block()
    thread_preempt()
    panic
    thread_block()
    unix_release_force()
    unix_release()
    schedtransmit()
    softclock_scan()

    or this:

    panic
    thread_block()
    thread_preempt()
    panic
    thread_block()
    unix_release_force()
    unix_release()
    ottooutput()
    atm_cmm_send()

  • An upgrade enhancement to the ATM350 driver. This patch prevents panics in driver routines that can be called from different interrupt levels.

  • Fixes a panic from the ATM OTTO/OPPO driver.

  • Corrects a problem in the ATM driver which could result in data inconsistency and system panic.

Patch 991.00

OSF410-405551A

Patch: setacl Command Correction

State: Supersedes patch OSF410-405407-1 (812.01)

This patch corrects the following:

  • Corrects the problem with setacl not being able to handle a user ID beginning with a numeral.

  • Fixes a memory leak in retrieve_file_acl.

Patch 992.00

OSF410-405552A

Patch: uucp Cmd Correction, Security (SSRT0296U, SSRT0556U)

State: Supersedes patches OSF410-400189 (80.00), OSF410-400189C (208.00), OSF410-400239 (136.00), OSF410-400189C-1 (230.00), OSF410-400408 (395.00), OSF410-400408B-3 (403.03)

This patch corrects the following:

  • A potential security vulnerability has been discovered in BIND (Domain Name Service), 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.

  • There is a problem in the Bind 4.9.3 patch which may cause incorrect messages to be reported. It may also cause statically linked programs using certain network functions in libc to core dump.

Patch 993.00

OSF410-405553

Patch: Fixes Problem With "mkdir -p" Command

State: New

This patch fixes a problem with the "mkdir -p" command. "mkdir -p" would not return an error if the last component in the pathname already exists.

Patch 995.00

OSF410-405557

Patch: awk Utility Correction

State: Supersedes patches OSF410-400318 (213.00), OSF410-400358 (265.00), OSF410-405482 (944.00)

This patch corrects the following:

  • Fixes problem in which "awk" consumes memory until the machine swaps itself and core dumps with following error:

    write failed, file system is full
    Memory fault - core dumped

  • Fixes a problem in which the awk -FS command does not display the correct output.

  • Fixes a problem in the awk command. The maximum number of fields per record was changed from 99 to 199.

  • Fixes problem with awk printing incorrectly.

Patch 996.00

OSF410-405559

Patch: LSM Command "volrootmir -a" Fails

State: Supersedes patch OSF410-400370 (270.00)

This patch corrects the following:

  • Fixes several LSM problems related to the volunroot, volrootmir, and vol-reconfig scripts.

  • Fixes a problem wherer the LSM command "volrootmir -a" fails if the source and target disks are not the same type.

Patch 998.00

OSF410-405561

Patch: Fix For POP Mail Handler

State: Existing

This patch corrects two problems with the POP mail handler:

  • Netscape Mail clients are unable to access their mailboxes after an initial session. The /usr/spool/pop/username.lock file is left over and must be removed manually.

  • The POP mail handler fails to properly rename its temp file after receiving a quit command.

Patch 1002.00

OSF410-405566

Patch: volrecover Does Not Return Error Status

State: Existing

This patch corrects a problem in which a failure of the volrecover utility will not return a failed status code.

Patch 1004.00

OSF410-405569

Patch: named, screend Correction, Security (SSRT0296U)

State: Supersedes patches OSF410-400189 (80.00), OSF410-400189B (207.00), OSF410-400239 (136.00), OSF410-400189B-1 (229.00), OSF410-400313 (209.00), OSF410-400408 (395.00), OSF410-400408C (404.00), OSF410-400422 (492.00), OSF410-405403B (894.00), OSF410-405568 (1003.00)

This patch corrects the following:

  • A potential security vulnerability has been discovered in BIND (Domain Name Service), 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.

  • Corrects a problem where, if the FLAG bit is set in the IP header, screend incorrectly reports:

    ACCEPT: Not first frag, off 64

  • There is a problem in the Bind 4.9.3 patch which may cause incorrect messages to be reported. It may also cause statically linked programs using cetain network functions in libc to core dump.

  • Fixes a problem in which a BIND server may find that named will place a warning message in the daemon.log that was not previously seen.

  • Fixes a problem in which a BIND server writes files to the /etc/namedb directory instead of the /var/tmp directory.

Patch 1006.00

OSF410-405571

Patch: Fix For ipcs Command

State: Existing

This patch corrects a problem that prevents a user from using the ipcs command on a system whose kernel has been booted from a file that is not /vmunix.

Patch 1008.00

OSF410-405575A

Patch: kloadsrv May Cause System Panic

State: Supersedes patches OSF410-400243 (140.00), OSF410-405315 (746.00)

This patch fixes the following problems:

  • Fixes a problem in which loadable kernel modules that are loaded with the kloadsrv daemon at run time, may cause a system panic.

  • Ensures that kloadsrv remains running when the system is shut down to the single user run level.

  • Fixes the following problems:

    • Segmentation fault in /sbin/loadsrv.

    • In the License Management Facility, incorrect amount of memory is copied, which potentially can cause data corruption.

Patch 1012.00

OSF410-405580

Patch: automount daemon Correction

State: Supersedes patch OSF410-405374 (788.00)

This patch corrects the following:

  • Fixes an automount problem. An automount map file entry that included a comment was being parsed incorrectly, resulting in an error.

  • Fixes a problem in which the automount daemon hangs when invoked by the rsh command.

Patch 1020.00

OSF410-405592

Patch: Possible Memory Corruption Caused By devz

State: Existing

This patch fixes a possible memory corruption caused by devz.

Patch 1021.00

OSF410CDE-405013

Patch: Security (SSRT0566U)

State: Existing

A potential security vulnerability has been discovered where under certain circumstances users may gain unauthorized access. Compaq has corrected this potential vulnerability.

Patch 1023.00

OSF410CDE-405015

Patch: Security (SSRT0585U)

State: Existing

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.

Patch 1024.00

OSF410CDE-405018

Patch: Various CDE Fixes

State: Existing

This patch fixes the following problems in the Common Desktop Environment:

  • "dtaction" fails to validate a password when C2 Enhanced Security is installed.

  • The text field which accepts the password does not allow the user to backspace, erase, or type over a previously entered wrong password.

Patch 1027.00

OSF410CDE-405022

Patch: Security (SSRT0571U)

State: Supersedes patches OSF410CDE-405011 (689.00), OSF410CDE-405014 (1022.00), OSF410CDE-405020 (1025.00)

This patch corrects the following:

  • Fixes a problem where dtmail can core dump when there exists long lines in Sun Mail Tool attachments. This causes a buffer overflow.

  • Fixes the problem where dtmail corrupts binary attachments that are sent as Sun Mail Tool attachments.

  • A potential security vulnerability has been discovered where under certain circumstances users may gain unauthorized access. Compaq has corrected this potential vulnerability.

  • Fixes a problem where the CDE mail interface (dtmail) does not display the date and time of mail messages in the Message Header list when the time zone is set to certain time zones such as GB-Eire.

Patch 1028.00

OSF410CDE-405023

Patch: CDE File Manager (dtfile) Leaves Defunct Processes

State: Existing

This patch fixes a problem where the CDE File Manager (dtfile) sometimes left defunct processes.

Patch 1029.00

OSF410DX-405010

Patch: Account Management Command Correction

State: Supersedes patches OSF410DX-400005 (67.00), OSF410DX-400008 (121.00), OSF410DX-400010 (204.00), OSF410DX-400013 (527.00), OSF410DX-405004 (667.00), OSF410DX-405003-1 (668.01), OSF410DX-405005 (695.00), OSF410DX-405007 (697.00), OSF410DX-405008 (698.00), OSF410DX-405006 (696.00)

This patch corrects the following:

  • When creating a new user account with a home directory of root, permissions on the root directory are changed to 700, rendering the root file system inaccessible to non-root users. DIGITAL UNIX 4.0B Patch Kit 1 causes a problem with the System V Environment (SVE) /usr/opt/svr4/usr/bin/passwd command. If an invalid password is entered, subsequent invocations of the passwd command, /usr/bin/X11/dxaccounts command, or the account management commands fail with the following error:

    The password and group files are currently locked by another user.

  • Fixes for miscellaneous problems with the account management commands, specifically the Account Manager graphical user interface (/usr/bin/X11/dxaccounts) and the command line interface (useradd, userdel, groupadd, etc).

  • Fixes a problem that causes the account management commands (dxaccounts, useradd, and usermod) to split long NIS group lines incorrectly. This causes a majority of users to have improper access to files, directories, and applications and also causes the newgrp command to fail.

  • When Enhanced Security is enabled, the useradd and usermod commands incorrectly set the password expired and password lifetime attributes to 0 when not specified on the Command line.

  • The administrative_lock_applied command line option for useradd and usermod does not correctly lock and unlock an account.

  • When Enhanced Security is enabled, userdel command incorrectly removes an account from /etc/passwd.

  • When issuing a useradd -D or usermod -D command to view the account manager defaults, the Inactive (days) value would always show the character "s" rather than nothing when the Inactive days status has been defeated with a -1 value.

  • Fixes the following problems encountered when using the Account Manager application (dxaccounts):

    • When modifying an existing NIS "+" or NIS "-" user account by turning off the NIS Overrides toggle, the User ID field is incorrectly set to 0.

    • While adding a NIS "+" or NIS "-" user, dxaccounts requires a password to be set.

  • Fixes a problem where Dxaccounts allows the ":" character to be accepted in the user shell, home directory, fullname, office, office phone, and home phone fields. This caused the /etc/passwd file to become corrupted.

  • Fixes the problem where usermod -g will lock the user account if it is unlocked.

Patch 1029.00

continued

  • Fixes a problem where the account manager graphical interface (dxaccounts) will core dump on systems running enhanced security when performing a "Find Local User..." or "Find NIS User..." operation in which "Secondary Groups" is the only search criteria that has been specified.

  • Fixes a problem using templates for pre-expired passwords. When the administrator creates a template and within the template chooses force password change at the next login, the user is NOT being asked to change his password as he should.

  • Fixes a problem where a large number of shells in /etc/shells (greater than 10) can cause dxaccounts to coredump or have unpredictable behavior.

Patch 1030.00

OSF410DX-405011

Patch: Fix For dxpause

State: Existing

This patch fixes the problem where the dxcalendar reminder displays through the pause screen (dxpause) and remains on the top of the pause window.

Patch 1032.00

OSF410X11-405014

Patch: Enhancement For makedepend Command

State: Existing

Increases the maximum number of files that one file can depend on in the makedepend utility from 1024 to 4096.

Patch 1033.00

OSF410X11-405015

Patch: xfs Sometimes Fails With A Seg Fault

State: Existing

This patch fixes a problem where the X font server (xfs) sometimes failed with a segmentation fault when it received an invalid request.

Patch 1034.00

OSF410X11-405016A

Patch: Motif Toolkit Correction

State: Supersedes patches OSF410X11-400015 (132.00), OSF410X11-400020 (283.00), OSF410X11-405009-1 (669.01), OSF410X11-405010-1 (844.01)

This patch corrects the following:

  • Fixes a Motif toolkit drag-n-drop operation failure that may cause Motif applications to abort.

  • Fixes the memory leak in the Motif text widget when changing colors using XtVaSetValues().

  • Fixes a small memory leak in the Motif text widget.

  • Fixes the Motif tear off menu core dump problem. The problem is seen when the tear off menu from a pulldown menu is closed/destroyed.

  • Fixes a problem with Motif Drag-and-Drop where if a parent drop site was unregistered before a child drop site, subsequently unregistering the child drop site would cause a segmentation fault.

Patch 1042.00

OSF410-223

Patch: Security (SSRT0496U, SSRT0563U)

State: Supersedes patches OSF410-400080 (11.00), OSF410-400106 (15.00), OSF410-400119 (18.00), OSF410-400133 (32.00), OSF410-400139 (35.00), OSF410-400143 (37.00), OSF410-400153 (46.00), OSF410-400154 (47.00), OSF410-400154-1 (47.01), OSF410-400189 (80.00), OSF410-400227 (125.00), OSF410-400227-1 (125.01), OSF410-400131 (24.00), OSF410-400195 (84.00), OSF410-400210 (96.00), OSF410-400226 (123.00), OSF410-400241 (138.00), OSF410-400239 (136.00), OSF410-400239-1 (136.01), OSF410-400261 (156.00), OSF410-400302 (198.00), OSF410-400307 (201.00), OSF410-400331 (219.00), OSF410-400331-1 (219.01), OSF410-400331-2 (219.02), OSF410-400331-3 (227.00), OSF410-400323 (244.00), OSF410-400334 (249.00), OSF410-400348 (256.00), OSF410-400372 (271.00), OSF410-400400 (384.00), OSF410-400402 (385.00), OSF410-400403 (390.00), OSF410-400408 (395.00), OSF410-400410 (401.00), OSF410-400417 (483.00), OSF410-400430 (499.00), OSF410-400448 (508.00), OSF410-405168 (583.00), OSF410-405169 (585.00), OSF410-405175 (601.00), OSF410-405179 (650.00), OSF410-405181 (596.00), OSF410-405191 (600.00), OSF410-405192 (603.00), OSF410-405165 (582.00), OSF410-405217 (620.00), OSF410-400203 (88.00), OSF410-400115 (16.00), OSF410-400448-1 (508.01), OSF410-156C-1 (672.01), OSF410-405308 (740.00), OSF410-405312 (744.00), OSF410-405317 (747.00), OSF410-405321 (749.00), OSF410-405380 (793.00), OSF410-40538 (794.00), OSF410-405391 (802.00), OSF410-405272 (716.00), OSF410-405341 (763.00), OSF410-405349 (769.00), OSF410-172 (856.00) OSF410-400118 (17.00), OSF410-400169 (54.00), OSF410-057 (98.00), OSF410-400270 (181.00), OSF410-400304 (199.00), OSF410-400326 (247.00), OSF410-400435 (502.00), OSF410-405301 (736.00), OSF410-405331 (756.00), OSF410-400193 (82.00), OSF410-400434 (501.00), OSF410-405159-1 (611.01), OSF410-405343 (764.00), OSF410-405365 (781.00), OSF410-405389 (800.00), OSF410-400122 (19.00), OSF410-400079 (10.00), OSF410-400382 (480.00), OSF410-405403-1 (809.01), OSF410-400437-1 (883.01), OSF410-405422 (819.00), OSF410-405520 (923.00), OSF410-405477 (941.00), OSF410-405479 (943.00), OSF410-405549A (989.00), OSF410-405564 (1000.00), OSF410-405586 (1015.00), OSF410-405538 (983.00), OSF410-405528 (977.00), OSF410-400343 (254.00), OSF410-405201 (606.00), OSF410-405227-1 (578.01), OSF410-240 (1054.00), OSF410-405500 (958.00), OSF410-217A (1038.00)

This patch corrects the following:

  • Fixes a problem in which multithreaded applications that reference a pthread_mutex_destroy routine may fail with EBUSY or the application may hang.

  • Fixes a problem with the DECthreads "legacy" library. Specifically, this patch addresses the potential hang of programs that use the Draft 4 interface for pthread_once().

  • Fixes a problem whereby mkpasswd fails for /etc/passwd files that are very large (containing roughly 30 thousand to 80 thousand entries).

  • Fixes problems in threaded applications with incorrect signal behavior and thread creation failures using user allocated stacks.

  • Fixes threaded applications seeing a deadlock with fork(), premature stack overflows, corrupted mutexes, and orphaned condition variable or mutex blocking structures.

Patch 1042.00

continued

  • Fixes problems in threaded programs related to DECthreads bugchecks, fork(), stack corruptions, and exception handling problems. This patch may also fix problems with non-threaded programs relating exception handling.

  • Fixes problems that might cause threaded programs running under DIGITAL UNIX V4.0 to hang. Specifically, this patch addresses situations related to DECthread bugcheck, pthread_once() or cma_once(), and unhandled exceptions.

  • A potential security vulnerability has been discovered in BIND, 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.

  • Fixes a problem in which mallopt(M_MXFAST), instead of making malloc() faster, makes it as much as 65 times slower.

  • Fixes a problem where a call to popen() hangs after a bad call to pclose() in a threaded program.

  • Fixes a problem that may cause older call_shared FORTRAN applications to find missing symbols in libc.so.

  • Fixes a deadlock problem that may occur with multithreaded applications calling any of the functions for getting system database information (gethostent, getservent, etc.) and which also call fork. The deadlock may occur when such applications are run on systems configured to use YP services.

  • Fixes a problem that occurs after a user logs into a system with an SRV4-style LAT device. When the ttyslot function is called, the system fails to find the device and returns a value of zero, indicating an error in the ttyslot function.

  • Fixes a problem that prevents gethostent() from returning all YP or bind served entries.

Patch 1042.00

continued

  • Fixes a problem in which the interaction of signals with setjmp/longjmp called repeatedly in a loop was causing a segmentation violation and core dump in a customer's application.

  • Fixes problems with redundant close operations on file descriptors by Network Information Services (NIS) and Remote Procedure Calls (RPC) in multithreaded applications.

  • Fixes a problem in which the rcmd function may cause the system to dump core.

  • Fixes the following two problems that occur in the DECthreads core library:

    • The process blocked signal mask, as set by sigprocmask(), is cleared in the child process following a fork().

    • Under certain load conditions, a DECthreads bugcheck occurs in pthread_kill(). This results in a core dump.

  • Allows customers to create hashed passwd databases from large passwd files by using a new option (-s) to the mkpasswd command. The -s option increases the block size of the database page file.

  • Fixes a TCP/IP problem that can occur with programs linked with the libc library. These programs may return a value of (-1) when calling the svc_tcp() function.

  • Fixes a deadlock issue between fork() processing and exception handling on DIGITAL UNIX 4.0. An exception occuring during a fork() operation would cause the child and parent processes to hang with no cpu activity.

  • The mkpasswd command dumps core when user just types 'mkpasswd -s' with no other arguments. It also wasn't using the page block size of an existing database if the -s option was not specified.

Patch 1042.00

continued

  • Fixes two problems in the DECthreads library:

    • On multiprocessor platforms, condition variable broadcasts were occasionally being lost.

    • Stack unwinding during exception processing was losing contexts, resulting in incorrect stack traces.

  • Corrects a problem related to the statically initialized mutexes in DECthreads library (libpthread.so)

  • Fixes a problem whereby a call to the libc dbm_open() routine followed immediately by a call to dbm_close() causes hashed database directory files to be truncated.

  • Corrects a problem which occurs when pthread_cond_timedwait() is called with a large timeout value (greater than 23 days).

  • There is a problem in the Bind 4.9.3 patch which may cause incorrect messages to be reported. It may also cause statically linked programs using certain network functions in libc to core dump.

  • Fixes a problem with call_shared executables that are linked with libc.a instead of libc.so. A symptom of this problem is that routines like dlopen(3) and __fini_* routines are not run.

  • Fixes a problem with the auditd daemon. If auditd is logging to a server and the server becomes unavailable, the CPU usage for the daemon rises dramatically.

  • Fixes a problem in which RPC client functions do not correctly handle system calls interrupted by a signal (EINTR errors).

  • Fixes a problem that causes the readdir_r() function to read past the end of its input buffer.

  • Fixes a DECthreads problem in which a threaded program may unexpectedly abort a process.

Patch 1042.00

continued

  • Fixes a bug found in "pthread_kill" call. The bug may cause a thread program to terminate when the program tries to send a kill signal to a terminated thread.

  • Fixes a problem whereby exceptions propagating out of (or thrown from) __init routines in C (or C++) programs are not caught by the last chance handler and result in an infinite loop.

  • Fixes a problem with the syslog function. Some syslog messages may fail to get written to a log file when the system is experiencing a heavy I/O load.

  • Fixes a problem with rexec(3) losing socket descriptors.

  • Fixes a problem with the statvfs function. statvfs returns a wrong status when the file system is full.

  • Under enhanced security, sometimes users (even root) are unable to log in on graphics console, even after using dxdevices or edauth to clear the t_failures count.

  • On systems running enhanced security, user-written applications that call auth_for_terminal() may fail with a segmentation fault.

  • Fixes a problem which occurs when a program attempts to create a thread with stacksize or guardsize greater than maximum signed long integer.

  • Fixes a scanset processing problem in swscanf().

  • Fixes a problem that causes a segmentation fault when doprnt calls strlen with non-null-terminated char arrays.

  • Fixes a problem with disklabel, where the command failed if the device was unable to provide disk geometry information.

  • Fixes a call to dbm_open() followed immediately by a call to dbm_close() caused hashed database directory files to be unnecessarily flushed.

    The ndbm routines were not threadsafe because of the definition and use of buffer ovfbuf, and dbm_open had some problems in its error handling code.

    The calculation of the page block size in dbm_open() did not make some necessary checks on size limits.

  • Fixes a problem with printing floating point values using the width and precision specifiers. Previously, the leading and trailing zero counts were often miscalculated.

  • Fixes a memory leak in the libc glob() function.

Patch 1042.00

continued

  • Fixes a virtual memory problem that may cause the system to panic with one of the following messages:

    pmap_begin_mutex_region timeout

    or

    simple_lock timeout

  • Fixes a problem in the DECthreads library for DIGITAL UNIX. During a fork() operation, DECthreads temporarily replaces its signal-to-exception mapping for synchronous signals by installing the system default handler. This fix permits any user-installed handlers to remain in place during the fork() operation.

  • Fixes a problem in the audit daemon when it is used as a network server. Child auditd processes that are serving network connections fail to reap their child processes (such as when log files are compressed), leaving them as defunct processes on the system.

  • Resolves a problem with Enhanced Security not handling a voucher correctly from some other security mechanism such as DCE. The scenario to reproduce the problem would be:

    A user incorrectly enters his username at the first "login:" prompt, but subsequently corrects the login name when prompted again after the first failure. Without this patch, the user upon successfully typing their login/password on the second try would still receive the message "login incorrect".

  • Adds automatic detection of a cdfs file system for the mount(8) command.

  • Fixes a problem that occurs if the kernel tunable variable "old-obreak" is set to zero and the system is running the Korn shell (ksh). The shell gets caught in an infinite loop printing a message similar to the following. Eventually the process will core dump:

    /adp/bin/adpbkup[135]: no space

  • Fixes a problem with the ksh shell program. ksh prevents a command which runs in a subprocess from writing to a tape device.

Patch 1042.00

continued

  • Fixes a problem that occurs when using the Korn shell (ksh). Keyboard input is not echoed when a user exits via a trap, after editor options have been set in ksh.

  • Fixes a problem in which the ksh command periodically prints erroneous characters instead of the command that was typed.

  • Fixes a problem in which the ksh shell sometimes reverses the group id (GID) and the effective group id (egid) of the calling process.

  • Fixes problems that occur when using the ksh shell. When the PATH for a command is not found, the following error message is displayed. Also, when the set command is executed, the system core dumps:

    /bin/ksh: invalid multi-byte character

  • Fixes a problem that occurs when using the Korn shell (ksh). Variables set with the typeset -L[n] built-in command do not work correctly when other subshells are spawned.

  • Fixes a problem that was caused by the Korn shell running in EMACS mode. When a window was resized with a width that exceeded 160 characters, the next command (or even a return) would cause the ksh utility to core dump.

  • Fixes a problem in the kornshell in which the "lt" operator didn't work correctly when the first expression was more than ten digits.

  • Fixes a problem when builtin variables (ex. TMOUT) are exported as readonly with values > 256. The "set" command (display all variables) will cause ksh to core dump with the error "stack overflow".

  • Fixes several serious problems with the "csh" command. Some of these problems can cause the "grep" and "find" commands to fail, when the user runs the commands under the "csh" shell.

  • Fixes a problem that occurs when using the C shell (csh). When a command that does both wildcard expansion and command substitution is run in csh, incorrect results are produced.

Patch 1042.00

continued

  • Fixes the problem that csh may omit the data byte 0x80 when processing a string in the ja_JP.SJIS or zh_TW.big5 locales.

  • Corrects a problem which results in a superuser being able to inadvertently bring the system down to single user mode by accidentally killing pid 1 (init) when trying to kill a background job (%1).

  • Fixes a memory management problem that occurs on systems running the Korn shell. Incorrect results occur when the length of the parameter to the echo command is altered.

  • Corrects quota command to return most severe error status on exit.

  • Fixes problems that occur with the dump and rdump commands. The commands will fail with the following error message:

    available blocks n < estimated  blocks m

    When a member of group "operator" logged into the console and (r)dump was invoked with the -n flag, an extraneous file (/dev/:0) was created.

  • Fixes a problem in which the dump command fails when the full pathname of the output file is not given.

  • Fixes a problem in which the vquota, vedquota, quota, edquota, dump, csh, and nslookup commands will sometimes display incorrect error messages for non-English locales.

  • Fixes a problem with the edquota utility, which prevented a user from creating quotas for UIDs or GIDs that did not already exist in the /etc/passwd or /etc/group files.

  • Fixes a problem in which BIND client applications are not able to resolve node names. Network applications running on a BIND client such as ping, telnet, and ftp using node names that are resolved by a BIND server will result in resolution errors such as "unknown host".

  • Fixes a problem in the csh shell that caused a change in the way wildcard patterns were matched. The problem resulted in the error:

    Glob aborted - Permission denied.

Patch 1042.00

continued

  • Fixes a problem with /usr/bin/ksh and the named-pipe (FIFO) communication that is used by applications.

  • Fixes a problem from a previous libc patch in which the gethostbyaddr function is not able to resolve node names. Non-standard characters that fall out of the standard set, such as underscores, cause a node name resolution problem for the gethostbyaddr function.

  • Fixes a problem where C shell background processes started from within a terminal emulator window (dtterm, dxterm, or xterm) exit when the terminal emulator window is closed.

  • This problem fixes unexpected logouts and terminal hangups encountered when using the /bin/su command and /bin/ksh as a login shell.

  • Corrects a problem that was causing ksh to core dump in vi editting mode. ksh was core dumping intermittently when using "." to repeat a command.

  • ksh does a segmentation fault and core dumps when displaying a here-document.

  • Fixes a problem in mountd where lines in the /etc/exports file could be no longer than 1023 characters. With this patch, a trailing backslash character in the /etc/exports file allows continuations beyond 1023 characters.

  • Fixes a problem in mountd. The NFS server allows read/write access to clients not on the exports list and other clients to be incorrectly denied access.

  • Fixes a problem with the mount command where it sometimes kills other processes.

  • Fixes a problem when using rsh to run shutdown on a client server. The correct console messages are displayed, but the system hangs instead of shutting down.

Patch 1044.00

OSF410-225

Patch: voldiskadm Fix

State: Existing

This patch corrects a LSM problem where voldiskadm was not properly handling the removal and replacement of disks that were in an error state.

Patch 1048.00

OSF410-234

Patch: Port Entries Do not Exist For DEC5031 Platform

State: Existing

This patch fixes a problem where the comm, floppy, and parallel port entries do not exist for the DEC5031 platform in the eisa_option_data.c file but are specified in the /etc/sysconfigtab file. This makes an installation from an EISA device impossible.

Patch 1050.00

OSF410-236

Patch: rcmgr Causing Corruption of rc.config File

State: New

This patch fixes a problem with the corruption of the /etc/rc.config file when more than one rcmgr process attempts to write to the rc.config.

Patch 1052.00

OSF410-238

Patch: bparm Subsystem Causing System Panic

State: New

This patch fixes a problem that caused a panic to occur when the generic subsystem attribute kmem-debug is set to 1 and the bparm subsystem is queried with the sysconfig -q command.

Patch 1058.00

OSF410-244

Patch: Security, Various Kernel Fixes (SSRT0482U, SSRT0536U)

State: Supersedes patches OSF410-039 (5.00), OSF410-034 (2.00), OSF410-400100 (14.00), OSF410-405036 (64.00), OSF410-400141 (36.00), OSF410-400165 (50.00), OSF410-052 (76.00), OSF410-059 (100.00), OSF410-405054 (71.00), OSF410-400127 (22.00), OSF410-400197 (86.00), OSF410-062 (113.00), OSF410-063 (119.00), OSF410-405062 (106.00), OSF410-400216 (109.00), OSF410-400232 (129.00), OSF410-400208 (95.00), OSF410-400198 (114.00), OSF410-405044 (61.00), OSF410-405053 (103.00), OSF410-405059 (105.00), OSF410-049 (75.00), OSF410-400186 (78.00), OSF410-400233 (130.00), OSF410-400250 (144.00), OSF410-400201 (87.00), OSF410-400242 (139.00), OSF410-405045 (62.00), OSF410-068 (133.00), OSF410-400235 (134.00), OSF410-400221 (116.00), OSF410-405068 (148.00), OSF410-405058 (157.00), OSF410-405058-1 (157.01), OSF410-070 (145.00), OSF410-400130 (25.00), OSF410-074 (159.00), OSF410-085 (167.00), OSF410-405067 (147.00), OSF410-405098 (190.00), OSF410-400245 (141.00), OSF410-400266 (178.00), OSF410-400289 (192.00), OSF410-400351 (222.00), OSF410-400296 (196.00), OSF410-087 (173.00), OSF410-400298 (197.00), OSF410-400298-1 (234.00), OSF410-095 (402.00), OSF410-400281 (184.00), OSF410-400283 (186.00), OSF410-400346 (255.00), OSF410-400353 (257.00), OSF410-400354 (258.00), OSF410-400356 (260.00), OSF410-400367 (267.00), OSF410-400373 (388.00), OSF410-400378 (387.00), OSF410-400384 (272.00), OSF410-400401 (393.00), OSF410-400407 (391.00), OSF410-405103 (214.00), OSF410-405116 (282.00), OSF410-102 (241.00), OSF410-400284 (187.00), OSF410-112 (398.00), OSF410-113 (399.00), OSF410-400397 (394.00), OSF410-405065 (146.00), OSF410-405123 (408.00), OSF410-405114 (281.00), OSF410-400369 (269.00), OSF410-122 (418.00), OSF410-123 (419.00), OSF410-128 (422.00), OSF410-130 (421.00), OSF410-135 (423.00), OSF410-405121 (530.00), OSF410-405134 (533.00), OSF410-400414 (488.00), OSF410-400418 (490.00), OSF410-400420 (491.00), OSF410-400421 (546.00), OSF410-400441 (504.00), OSF410-400442 (505.00), OSF410-400451 (511.00), OSF410-400456 (513.00), OSF410-400458 (515.00), OSF410-400461 (517.00), OSF410-400466 (520.00), OSF410-129 (426.00), OSF410-405136 (414.00), OSF410-405114A (226.00), OSF410-400469 (548.00), OSF410-143 (559.00), OSF410-145 (560.00), OSF410-155 (569.00), OSF410-158 (570.00), OSF410-157 (575.00), OSF410-405153 (584.00), OSF410-405155 (592.00), OSF410-405162 (634.00), OSF410-405176 (616.00), OSF410-405185 (633.00), OSF410-405198 (656.00), OSF410-405199 (644.00), OSF410-405200 (648.00), OSF410-405204 (619.00), OSF410-405206 (625.00), OSF410-405207 (624.00), OSF410-405209 (612.00), OSF410-405210 (617.00), OSF410-405216 (621.00), OSF410-156 (572.00), OSF410-405221 (636.00), OSF410-405229 (640.00), OSF410-405238 (657.00), OSF410-405281 (580.00), OSF410-405187 (594.00), OSF410-405187-1 (564.01), OSF410-405243 (646.00), OSF410-405292-1 (579.01), OSF410-405259 (708.00), OSF410-405268 (714.00), OSF410-405276 (719.00), OSF410-405277 (720.00), OSF410-405278 (721.00), OSF410-405287 (727.00), OSF410-405289 (728.00), OSF410-405293 (730.00), OSF410-405305 (738.00), OSF410-405325 (751.00), OSF410-405330 (755.00), OSF410-405348 (768.00), OSF410-405352 (770.00), OSF410-405355 (772.00), OSF410-405356 (773.00), OSF410-405357 (774.00), OSF410-405362 (778.00), OSF410-405364 (780.00), OSF410-405368 (783.00), OSF410-405371 (786.00), OSF410-405397 (806.00), OSF410-405404 (810.00), OSF410-405430 (823.00), OSF410-405448 (837.00), OSF410-167 (853.00), OSF410-176 (859.00), OSF410-178 (860.00), OSF410-187 (864.00), OSF410-193 (869.00), OSF410-196 (872.00),

Patch 1058.00

continued

OSF410-206 (879.00), OSF410-208 (880.00), OSF410-405189 (700.00), OSF410-405269 (715.00), OSF410-405299 (734.00), OSF410-405302 (737.00), OSF410-405307 (739.00), OSF410-405335 (758.00), OSF410-405340 (762.00), OSF410-405345 (766.00), OSF410-405363 (779.00), OSF410-405366 (782.00), OSF410-405378 (792.00), OSF410-405383 (796.00), OSF410-405384 (797.00), OSF410-405392 (803.00), OSF410-405394 (804.00), OSF410-405416 (817.00), OSF410-405426 (820.00), OSF410-405429 (822.00), OSF410-405431 (824.00), OSF410-405443 (833.00), OSF410-405450 (839.00), OSF410-164 (850.00), OSF410-170 (855.00), OSF410-182 (862.00), OSF410-189 (866.00), OSF410-194 (870.00), OSF410-195 (871.00), OSF410-405190 (701.00), OSF410-405445 (835.00), OSF410-405442 (832.00), OSF410-203 (877.00), OSF410-213 (882.00), OSF410-180-1 (861.01), OSF410-159-1 (849.01), OSF410-405434-1 (827.01), OSF410-400066 (9.00), OSF410-400218 (111.00), OSF410-400218-1 (111.01), OSF410-058B (155.00), OSF410-058 (99.00), OSF410-405097 (189.00), OSF410-098 (239.00), OSF410-405376 (790.00), OSF410-205 (878.00), OSF410-405328-1 (753.01), OSF410-405455 (925.00), OSF410-405459 (927.00), OSF410-405464 (930.00), OSF410-405466 (932.00), OSF410-405471 (935.00), OSF410-405472 (936.00), OSF410-405473 (937.00), OSF410-405490 (950.00), OSF410-405491 (951.00), OSF410-405492 (952.00), OSF410-405495 (955.00), OSF410-405501 (959.00), OSF410-405502 (960.00), OSF410-405519 (972.00), OSF410-405527 (976.00), OSF410-405535 (981.00), OSF410-405546 (986.00), OSF410-405560 (997.00), OSF410-405563 (999.00), OSF410-405570 (1005.00), OSF410-405578 (1010.00), OSF410-405579 (1011.00), OSF410-405583 (1013.00), OSF410-405584 (1014.00), OSF410-405589 (1018.00), OSF410-405590 (1019.00), OSF410-214 (1035.00), OSF410-215 (1036.00), OSF410-216 (1037.00), OSF410-218 (1039.00), OSF410-224 (1043.00), OSF410-227 (1045.00), OSF410-228 (1046.00), OSF410-232 (1047.00), OSF410-237 (1051.00), OSF410-242 (1056.00), OSF410-245 (1059.00), OSF410-247 (1061.00), OSF410-250 (1063.00), OSF410-405456 (926.00), OSF410-252 (1064.00), OSF410-405468A (933.00), OSF410-239A (1053.00), OSF410-241A (1055.00), OSF410-253A (1065.00), OSF410-219 (1040.00), OSF410-405023 (6.00), OSF410-400146 (39.00), OSF410-400236 (135.00), OSF410-400324 (245.00), OSF410-400368 (268.00), OSF410-405184 (653.00), OSF410-048 (28.00), OSF410-090 (175.00), OSF410-136 (427.00), OSF410-147 (561.00), OSF410-405080 (169.00), OSF410-405128 (532.00), OSF410-151 (571.00), OSF410-405237 (655.00), OSF410-400368-1 (268.01), OSF410-405202-1 (673.01), OSF410-405432 (825.00), OSF410-246 (1060.00), OSF410-405436 (828.00), OSF410-235 (1049.00)

Patch 1058.00

continued

This patch corrects the following problems:

  • Provides support for the fuser utility. This utility displays a list of processes that are holding references to a file on the file system that cannot be unmounted.

  • Fixes an isp1020 SCSI driver performance regression.

  • Provides HSZ70 support.

  • Fixes a problem in which the ufs property list can become corrupted.

  • Fixes a problem with the fsck command. When fsck is run on a non-existent file system or on a currently mounted file system, it returns a success status of zero. It should return a non-zero status.

  • Greatly improves DIGITAL UNIX networking performance and is targeted at high traffic Web server systems or any system which handles a large number of TCP connections simultaneously; e.g., more than several thousand at one time.

  • A kernel panic with a "kernel memory fault", typically in either the vm_pg_alloc() or vm_zeroed_pg_alloc() routines.

  • Fixes a problem in which network applications communicating to one of the host's own addresses, may hang, or receive the error message:

    no buffer space available

    The problem occurs due to a queue full condition on the interface.

  • Fixes a problem in which the the lastcomm accounting command doesn't print the "S" flag at appropriate times. This patch also improves the performance of lastcomm.

  • Resolves a TCP/IP network hang due to IP Q ACK deadlock. When this condition occurs the IP Q becomes full due to saturation. Representative console messages indicating this condition are shown below:

    SIS00-00-root: IP q full, 315617 packets dropped in the last 5 mins.

Patch 1058.00

continued

  • Fixes a performance problem that occurs with UFS file systems.

  • Fixes a number of problems relating to signals and POSIX 1003.1b timers in multithreaded programs running on multiprocessor systems. These problems can result in missed timer-expiration signals and system crashes.

  • Probe of isp fails intermittently during boot.

  • Fixes a kernel memory fault in ether_output packet filter, when running tcpdump.

  • Fixes ICMP REDIRECTS. When an ICMP REDIRECT is received, the routing table was updated properly, but the IP layer didn't use then new route information.

  • Fixes a problem in which the system can panic with "lock already owned by thread".

  • Fixes a problem that occurs on all systems that use networking system.

  • Provides a kernel fix for network sockets left in FIN_WAIT_1 state forever. This patch contains a "tunable" kernel parameter. It is recommended that only experienced system administrators attempt to set this parameter from the default value.

  • Fixes a problem that occurs when the system panics with the following error message:

    kernel memory fault

  • Fixes a problem with the exec() system function. A shell script that has "#! " as the first line of the script, invokes the program but does not set the effective user id for the execution of the program.

  • Fixes a problem that can occur with programs linked with libaio. These programs could dump core with a SIGSEGV signal or corrupt memory when calling the close() function with a bad file descriptor value.

  • Resolves a kernel memory fault.

  • System panics with message:

    vm_map_swapout: negative resident count

  • The user or sytem UAC_NOPRINT settings are ignored when an unaligned access trap on a user address was taken while in kernel mode; the unwanted error message is still printed.

  • NetWorker Version 4.2c requires this patch for new fcntl functionality. This layered product will not run desirably without this patch.

  • Allows tuneablity for existing two level task swapping scheme.

  • The ObjectStore application from Object Design, Inc. fails with the following error:

    Fatal error Invalid argument(errno = 22)
    munmap failed: cl_mmap:"

Patch 1058.00

continued

  • Fixes a system crash when setting the date on SMP systems.

  • Devices sometimes cannot be accessed by the system after getting selection timeouts.

  • Fixes a network socket problem with select() missing state changes on clients from non-write to writable.

  • Fixes some hangs that can occur during the "syncing disks..." portion of panic processing, improves the reliability of getting a dump after a system panic, and also makes it more likely that AdvFS buffers will be synced to disk after a system panic.

  • The vmstat(1) command displays negative numbers when used with the "-P" option. Problem may not appear on all platorms or configurations. It is dependent on how the system constructs various internal data structures.

  • Prevents a "kernel memory fault" in bread() during sync operations.

  • Fixes "kernel memory fault" panics from the kernel malloc() routine, and threads hanging in vfs_busy() when file-on-file mounting (kernel option FFM_FS) is used with fattach()/fdetach() or System V STREAMS.

  • Fixes a problem that prevents an "options DCEDFS" line from being added to the kernel configuration file. Without the fix, the kernel build will fail with the error:

    ld: dcedfs.mod: setjmp: multiply defined

  • Fixes a panic which occurs when a UNIX domain socket lock is being held while calling vrele().

  • An enhanced fix to the solockpair() routine. This fix was needed because the routine was freeing a socket lock structure that was concurrently spun upon in lock_write(). Typical problem symptoms include kernel memory faults with sockets, mbufs, and mblocks as well as hangs. Applications using sockets in a multithreaded, multi-cpu environment can experience a number of lock violations with the socket structures. This patch is MANDATORY to install on all systems. It will be effective on Uniprocessor systems when lockmode debugging is invoked.

Patch 1058.00

continued

  • Provides additional event logging by the SCSI/CAM disk driver to the binary.errlog file.

  • Fixes a problem that occurs when using real-time applications. When writing large (sequential) files to a UFS file system, time constraints associated with the application may be violated.

  • Fixes a panic that prints "kernel memory fault".

  • Fixes a "recursion count overflow" problem that occurs on DIGITAL UNIX systems.

  • Greatly reduces the number of "NFS stale file handle" messages logged to an NFS server system console.

  • Fixes a problem with the "ifconfig -a" command. At times, the command will not display all of the network interfaces.

  • Eliminates panics that will occur when attempting to execute shell scripts on a filesystem mounted with the "noexec" option.

  • Corrects a problem with an NFS V3 mounted AdvFS file system where under heavy I/O load, data being written to a file may be lost. Additionally, because file stats are not being saved, the file modification time may revert to a previous value.

  • Adds a mechanism to the poll() system call to allow it to be used as a timer.

  • Add TCP/IP support for third party drivers.

  • System experiences simple lock timeout panics in virtual memory routines when free memory is short and system is trying to reclaim memory.

  • 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.

  • Fixes a problem that causes systems to panic with a "kernel memory fault" from u_dev_lockop(). This has happened when a database tried to memory map a file.

  • Fixes the problem of audit_tool terminating prematurely the reading of a complete large log file via zcat. This usually occurs under GUI control.

  • This is a mandatory patch for the following systems and conditions:

    • Systems that use program debuggers such as TotalView, Ladebug, dbx, or gdb.

    • Systems that use the /proc file system in any other way (for example, the System V Environment ps command).

    • Systems that experience panics and hangs in the /proc file system.

    • Systems that panic when running multithreaded programs that call an exec() function.

    • Provides a mandatory patch for SMP systems with AdvFS file systems. Fixes a performance degredation problem that may occur.

    • Improves the performance of applications that map hundreds of thousands of files into the virtual address space.

    • Fixes a problem in which a filesystem cannot be unmounted. The system displays a "Device busy" error message.

Patch 1058.00

continued

  • Fixes a problem that occurs when starting up a system that is running the auditing subsystem and the performance manager. The system panics with the following error message:

    kernel memory fault

  • Contains two vm fixes in both the UFS and NFS code that collectively resolve a multitude of nfs and nfsd hangs.

  • Back-port of DIGITAL UNIX V4.0D-style multi-option kmem_debug settings. Changed all-or-one kmem_debug bucket selection to all-or-as-selected. Added two new kmem_debug options, KMEM_DEBUG_LINKS and KMEM_DEBUG_PROTECT.

  • Fixes an inode locking problem in the UFS iupdat() and itimes() functions.

  • Fixes a problem in which a system may crash if multiple bad blocks on a SCSI device are encountered simultaneously.

  • After a disk error occurs, mirror set switching may not happen soon enough to ensure high availability, or in some cases may not happen at all.

  • Fixes a problem that may occur after a system panics. The system may hang when trying to do a crash dump.

  • Fixes a problem that may cause a program to cause the IEEE floating point emulator to emit this message:

    FATAL IEEE FLOATING POINT EMULATION ON ERROR

  • Fixes a problem where conversion from double-precision floating point numbers to single-precision floating point numbers may not round properly in IEEE mode when the result should be the smallest denormal.

  • Corrects a raw I/O data corruption problem that occurs when using database applications. The problem is seen when the new-wire-method is active.

  • While sendsig() is prepairing a SIGFPE signal, the system panics with a kernel memory fault.

    The ieee_get_fp_control() routine uses the macros NXM_IEEE_STATE_COPYIN() and NXM_IEEE_STATE_COPYOUT(). These macros inadvertantly corrupt pcb->pcb_nofault.

    This patch solves the problem by saving and restoring the pcb nofault handler.

    The stack trace will be:

            panic("kernel memory fault")
            trap()
            _XentMM()
            sendsig()
            psig()
            trap()
            _XentIF()

    The faulting VA will contain an address similar to:

    0x000000011ffff???

    And the instructions leading to the faulting pc will be:

    bsr     ra, ieee_get_fp_control(line 61)
    lda     a0, 16383(zero)
    stq     v0, 560(s5)

Patch 1058.00

continued

  • Infrequently, under heavy disk I/O loads, user data can be written to the wrong disk, resulting in data corruption.

  • Provides the following support:

    • Support the HSZ70 Raid controller on the Fast10 Wide Differential KZPSA adapter in cluster environments under DIGITAL UNIX V4.0B. Support of the HSZ70 Raid controller also requires the KZPSA firmware to be upgraded to at least the version distributed on the Version 5.0 AlphaServer Console Firmware CDrom.

    • Latent support for the HSZ50 and HSZ70 Raid controller on the Fast20 Wide Differential KZPBA-CB adapter in cluster environments under DIGITAL UNIX V4.0B. Support of the HSZ70 Raid controller also requires the KZPBA-CB firmware to be upgraded to at least the version distributed on the Version 5.1 AlphaServer Console Firmware CDrom.

    • Performance regression fix for Qlogic isp1020/isp1040 chips.

    • Provide SCSI target mode fixes for ASE/TCR support on QLogic, primarily for HSZ70 support.

    • All modifications included in this patch are compatible with existing versions of KZPSA and Qlogic firmware.

  • Corrects a raw I/O data corruption problem that occurs when using database applications. The problem is seen when the new-wire-method is active.

  • Provides general support for Version A11 KZPSA firmware.

  • Fixes two kernel memory faults in networking code.

  • Corrects problems with AdvFS performance regression, and two AdvFS race condition situations between multiple routines that can cause panics.

  • Fixes a problem that occurs on an AdvFS file system. The system may panic with the following error message:

    ADVFS INTERNAL ERROR: dealloc_bits_page: can't clear a bit twice

  • Fixes a panic that occurs when the system's message buffer size is increased to beyond the default size of 4096. During the subsequent reboot, the syslogd daemon fails with a "Segmentation fault (core dumped)" message, and creates a core file in the "/" directory.

  • Provides two new procfs ioctls (PIOCUSAGE and PIOCTUSAGE) to collect task and thread wait time statistics.

  • Fixes a problem in which a file-on-file system mount of either an NFS or a /proc file system will panic the system.

Patch 1058.00

continued

  • Fixes an AdvFS problem in which the system may panic with the following error message:

    thread_block: simple lock owned

  • When a zero length message is sent to an invalid SVIPC message queue, kernel memory is corrupted.

  • Fixes a UFS file system problem. The system may panic with the following error message:

    panic spec_badop called

  • Eliminates the display of "Stack overflow: pid..." messages that may occur when running Ladebug.

  • Fixes a potential memory leak problem that occurs when using the KMEM_DEBUG_PROTECT option of the kmem_debug tuneable attribute.

  • This is a mandatory patch. This patch fixes a problem that occurs on programs that are linked with the pthreads library. After a parent process forks a child process, the child's floating point state may become corrupt.

  • Fixes a problem in which core() system call would try to dump from a memory region that has no permission, cause an access violation in core(), and the the core file would be unusable.

    An example of the problem.

      % file core
      core:   core dump, core file is incomplete
     
     % dbx program core
                    .
                    .
                    .
     can't attach to loader: I/O error
     Exiting due to error during startup

  • Fixes a problem of memory corruption. A TCP control structure is illegally accessed after it is released. The corrupted memory buckets are the 256-byte size.

  • Fixes a problem that occurs on AlphaServer 4100 systems. If no devices are attached to the KZPSA disk controller, the system may panic when attempting to perform I/O.

  • Fixes a problem in which the uswitch system call does not work when an application tries to reset the USW_NULLP option.

  • Fixes a problem with the ufs_fsck. ufs_fsck would mishandle certain dir corruptions,recursively asking the user if they want to fix it.

  • Fixes two problems that occur on AdvFS systems:

    • The system may panic with the following error message:

      simple_lock: hierarchy violation

    • A locking problem in the AdvFS log data structures may cause the following problems to occur:

      • System panics

      • Kernel memory faults

      • Memory corruption

Patch 1058.00

continued

  • Fixes a problem with the nfsd daemon. Although the maximum number of threads that nfsd can run is 128, the nfsd daemon will not start when the sum of UDP threads and TCP threads equals 128.

  • Fixes a problem that causes the system to panic with the following error message:

    u_anon_free: page busy

  • Fixes a problem when printing to slow printers using DIGITAL UNIX LAT. The end of a large file fails to print and no error is reported.

  • Provides a set of workarounds for Qlogic firmware bugs. These bugs were encountered when using the HSZ70 Raid Array Controller on the KZPBA-CB wide differential UltraSCSI adapter in a dual-node cluster environment.

  • Improves performance on low-memory (32MB) systems.

  • Fixes a panic in the virtual memory management system. The system displays the following error message:

     trap: invalid memory read access from kernel mode

  • Fixes an AdvFS response time problem that occurred when an application with many random access reads of many files was being slowed down by the resulting number of writes to disk.

  • Fixes a kernel memory fault panic. This patch is mandatory for all multiprocessor machines. The system will crash with the panic string "Kernel Memory Fault".

  • Fixes a rounding problem in the kernel software completion trap handler that slightly reduces the IEEE denormalized multiply and divide accuracy. It has no effect on typical arithmetic operations.

  • Fixes a race condition whereby the pid_block() system call does not properly synchronize with signals. This problem could cause the system call to block and not take a signal when it is supposed to.

  • Fixes a data corruption problem that occurs on systems using Prestoserve. The problem may cause system panics.

    For example, an AdvFS system may panic with:

    "bad v1 frag free list"

    A UFS file system may panic with:

    "ialloc: dup alloc"

  • Fixes a problem with the lpd line printer daemon. When "/sbin/init.d/lpd stop" is followed right away by "/sbin/init.d/lpd start", the new lpd fails to start. The error message from syslog is:

    /usr/spool/lpd.lock: locking failed: Operation would block

  • Fixes an ATM problem. When the ATM subsystem receives a CONNECT message with no signalling information elements (IEs), it corrupts a single byte of kernel memory.

Patch 1058.00

continued

  • Fixes a read/write problem for buffers larger than 4GB. The read/write request would truncate to a maximum of 4GB, but return success, causing data corruption.

  • Fixes a problem in which the system may panic with the following message:

    simple_lock: lock already owned by cpu

  • Fixes a problem with the ufs_fsck program in which filesystem corruption may occur on a running system when the root filesystem is mounted writable.

  • Corrects a problem where the NXM_IEEE_STATE_COPYIN/OUT macros need to save/restore the pcb nofault state. This was not happening.

  • Corrects a synchronization problem by blocking out hardclock before touching the state visible to the clock interrupt routine.

  • Corrects a problem in how the ps command reports its accumulated CPU time of all exited threads.

  • Fixes a hang of an ASE AGENT and problems with the error recovery of the HSZ family of storage arrays.

  • Fixes a problem where the umount of a filesystem will fail with "mount device busy", but no processes are accessing files in the filesystem.

  • Fixes a kernel memory fault panic in purge_fs_locks. This problem is normally only seen on ASE or TruCluster systems.

  • Extend the KMEM_DEBUG_PROTECT option of kmem_debug to the 8192-byte bucket.

  • Fixes a problem that occurs when KZPSA and KZTSA hardware resources needed to do I/O are unavailable causing a large number of events to be logged. The system can become sluggish and sometimes crash. This problem is seen on 8400 and 4100 systems with limited hardware scatter-gather memory resources.

Patch 1058.00

continued

  • Fixes a problem in which the host crashes when a user tries to delete a logical unit using hszterm. The following error message can be displayed:

    trap: invalid memory read access from kernel mode

  • Prevents a "kernel memory fault" in the bread() routine while performing sync operations.

  • Fixes a kernel memory fault in the networking code.

  • Fixed several problems with vfs file locking that could cause a crash including the file lock adjust logic, delete sleep lock logic, dead file lock logic, check/change granted logic, and insert file lock logic.

  • Fixes a problem that produces a core dump when running the quotacheck -a command. The following panic string is displayed:

    Segmentation fault at strcmp

  • Fixes a "mount device busy" problem that occurs when a user cannot overwrite the file "core". This prevents the filesystem from being umounted.

  • Fixes a problem with the vmstat -M command. vmstat -M shows an invalid byte count associated with the FREE malloc type.

  • Corrects a problem where a flag, TF_PSUSP, was not being cleared.

  • Corrects a problem that causes a "pmap_ssm_destroy: wired pages" crash.

  • Corrects a performace problem with POSIX timers.

  • Fixes a problem where the system will panic with "kernel memory fault".

  • Fixes a networking problem that occurs when the kernel variable ipport_userreserved is set to 65535.

  • Fixes a panic where in some instances, a message size of zero passed to msgsnd() can result in a kernel memory fault panic.

  • Avoids a "kernel memory fault" panic from sigsgdisp(). The problem has only been seen when shutting down an Oracle database.

Patch 1058.00

continued

  • Fixes a problem within LMF. The LMF user license list (OSF-BASE or OSF-USR) was not being decremented when a logout occurred.

    This occurs on systems with C2 security enabled and the system setup as a DCE Security server.

  • Corrects a problem that would randomly cause kloadsrv(8) to crash and improperly load/unload modules.

  • Fixes a problem in which the system can panic with "lock already owned by thread" or "kernel memory fault".

  • Fixes a TCP/IP performance problem in the tcp_reass() function.

  • Removes extraneous debug code.

  • Fixes a problem in which the system can panic with the message "kernel memory fault".

  • Fixes a system panic "rtfree 2" on multi-cpu systems.

  • Fixes a problem in which a recursive panic occurs during certain lockmode violations.

  • Fixes a problem that can cause asynchronous I/O to fail.

  • Fixes a problem that was caused by both floating point and integer overflow exceptions setting the si_code member in the siginfo structure to FPE_FLTOVF.

  • Fixes a virtual memory problem that may cause a system to panic with one of the following messages:

    pmap_begin_mutex_region timeout

    or

    simple_lock  timeout

Patch 1058.00

continued

  • Fixes a problem in the kernel that caused dynamically loaded PCI/ISA drivers to crash the system with the following panic:

    kernel memory fault

  • Fixes various problems caused when a set UID/GID program dumped core. The problems included system panics and "mount device busy" errors when trying to umount the filesystem.

  • Fixes a problem when a setuid program is exec'ed, and the error message "privileges disabled because of outstanding IPC access to task" is issued.

  • Fixes a problem when a processor is commanded to stop during a heavy load but does not actually halt.

  • Corrects a potential problem in the handling of a ieee_get_state_at_signal(3) C-library call.

  • Fixes a problem that occurs with applications based on POSIX message queues. During certain high activity periods, processes may hang when trying to access the message queue.

  • Fixes two Kernel Memory Faults in DIGITAL UNIX Path MTU discovery code.

  • Fixes a problem with the CPU auto_action console environment variable. If the auto_action console environment variable is set to BOOT or RESTART, when the CPU is to be stopped, the processor immediately boots and the user can not observe that the CPU had halted.

  • Fixes a system panic caused by a multithreaded process with profiling turned on. The system panics with the following message:

    lock_terminate: lock held

  • Fixes a problem with the way the ps utility collected CPU usage information. One effect of the problem was that processes run with nice values of 18 or greater had contention problems based on the incorrect CPU values.

  • Corrects a problem in memory allocation where a tasks resident count could become inconsistent, causing a panic.

  • Fixes a problem that produced a deadlock betweeen process threads. Typically, the deadlock caused the msfs_getpage routine to wait forever for a lock to be released.

  • Prevents a system panic from m_copym().

  • Fixes a problem in which a a cluster member panics, when the Production Server or Available Server software attempts to relocate a tape service.

  • Fixes a problem with memory being wasted by Mach IPC kernel message routines because they were assigned fixed sizes of memory (large or small, depending on the routine). Now, the memory allocation for the IPC routines has been changed to allocate only the memory each routine requires.

  • Fixes a problem in which a failed KZPSA adapter panics the kernel. It also fixes a problem in which CAM status was returning an incorrect "NO HBA" status for miscellaneous SIMPORT errors, instead of the correct "CAM BUSY" status.

Patch 1058.00

continued

  • Changed the sbcompress_threshold type to unsigned from signed since you could not set the sysconfig value for this flag correctly.

  • Fixes a problem that caused the system to panic with the string "kernel memory fault".

  • Fixes a problem with the "vmstat -M" command. This command displays negative values for memory usage by type and AdvFS buffer usage.

  • Fixes the bufpages calculation so that it takes granularity hints into account.

  • Fixes a problem with NFS conversion of a file's vnode number to a file handle number. The file id was truncated improperly, generating EOVERFLOW errors.

  • Fixes a problem in which savecore incorrectly reports a negative number of dumped bytes. This problem may be seen when doing a full crash dump on a system that has more then 2 gigabytes of memory.

  • Corrects a potential boot panic problem by limiting the size of the bufcache.

  • Fixes the following two problems that occur on an NFS file server using a Network Appliance server:

    • New files may not be listed in directory reads. For example, when the ls command is used not all the files may be listed.

    • When a directory listing is requested from a Network Appliance server, more data than was requested may be returned and the extra data is lost by the DIGITAL UNIX client. The problem can be seen by doing using the ls command; not all the files on the server are listed.

  • Fixes a virtual memory problem in which an uninitialized pointer in u_dev_protect() causes a kernel memory fault to occur.

  • Resolves systems from hanging during boot.

    Disabling CRD interrupts during boot caused PAL to NOT deliver the interrupt to the OS and therefore NOT clear the error, so a infinite recursion interrupt hang results.

    This patch is MANDATORY for all hardware platforms.

  • Fixes a problem in which the sysconfig command produces an error when a subsystem name of 15 characters is used. The following error message is displayed:

    framework error : copying memory to / from kernel

  • Corrects an NFS client problem that results in a kernel memory fault system panic.

  • Corrects a problem that can result in a kernel memory fault during heavy SCSI I/O, particularly on a small-memory system.

  • Fixes a problem with the KZPSA and KZTSA SCSI adapters. The adapters will hang if the SCSI cable is disconnected from them.

  • Fixes a kernel memory fault in cansignal()

  • Fixes the problem in which a DIGITAL UNIX system can randomly panic when more than 255 network interfaces are configured.

  • Corrects a problem seen with DECthreads tests that use fork(2).

Patch 1058.00

continued

  • Corrects a simple lock timeout problem in several vm_page routines.

  • Prevents a kernel malloc leak when changing the protection of a System V shared memory region that uses gh-chunks.

  • Fixes a problem in the AdvFS logging code, The way locking was implemented was causing degraded performance.

  • Fixes a problem with the vmstat -P command, which was incorrectly formatting output.

  • Corrects a problem where process hangs are caused by file references on raw devices accesses not being held.

  • Fixes a "kernel memory fault" system panic caused by AIO not cleaning up test headers when processes exit.

  • Fixes a routing corruption that could been seen as a kernel memory fault or a corruption within the 128 byte kernel memory bucket.

  • Corrects a potential problem in the handling of a write() system call to a routing socket.

  • Fixes a problem with user stack pointers not being saved properly in kernel crash dumps for running threads.

  • Fixes a problem whereby the contiguous memory allocator uses physmem to calculate percentage of memory to reserve. On a system with memory holes, this results in reserving non-existent pages for contiguous memory.

  • Fixes a problem in the AdvFS system. The log file corruption caused panics during recovery and failures displaying one of the following messages:

    ftx_fail: lgr_read failure

    or

    ftx_fail: dirty page not allowed

  • Fixes a problem that occurs on AdvFS systems. The system will panic with the following error message:

    malloc_overflow: guard space corruption

  • Fixes the following problems in AdvFS:

    • An operating system hang condition. The hang condition exists due to processes deadlocking in the AdvFS code.

    • AdvFS does not return an error when a user opens a file in O_SYNC mode and power is lost on the disk drive.

    • A locking error in the AdvFS fs_write() routine.

  • Corrects a small accounting problem where the measured time for a process was an integral rather than mean value.

  • DDR subsystem updated to handle SCSI devices returning a non-standard device type.

  • Fixes two problems with ddr_config. ddr_config previously would sometimes build partial device records. ddr_config on DIGITAL UNIX V4.0 was not compatible with input files created prior to this version.

Patch 1058.00

continued

  • Boot capability for new hardware support requires a new genvmunix. This patch delivers an updated genvmunix for that purpose.

  • Add support for DE500-BA 10/100 Ethernet adapter, and fix machine checks encountered when using the KZPAM-CA or KZPAM-DA controllers.

  • Provides latent support for TZS20.

  • An enhancement to the Ethernet driver for the DE500-XA Fast Ethernet Interface. This patch improves the failover time in an ASE environment when the cluster members use DE500-XA interfaces.

  • Fixes a problem in which the DDR database (/etc/ddr.dbase) limited the maximum block size of "unknown" tape drives to 64 kilobytes. The maximum block size is changed to 16 megabytes.

  • Fixes the following problems that may occur on some DE500 adapters:

    • The hardware setup operation may interrupt a pending ARP packet transmission.

    • If the cable to the adapter is not connected, the hardware setup operation will not execute.

  • Re-fix of the NFS loopback mounted file system hang problem that was fixed two years ago. The tunable parameter ubc_nfsloopback has been removed and the code restructured to eliminate any problems with NFS loopback mounted file systems as well as increase NFS performance.

    This patch also fixes performance and hang/panic problems with the UBC when filling the UBC with a small number of large files. The panic problems usually look like simple lock timeouts which results from a task waiting on the UBC LRU lock while ubc_page_alloc() excessively scans the LRU list for a usable page.

  • Fixes a problem with the ddr_config command, where the -x option would intermittently fail.

  • Fixes a problem with the memory file system (mfs) that caused systems to hang when they attempted to dynamically allocate a cdfs file system.

  • Adds code to save a copy of the requested mode bits in vattr before umask is applied.

  • Fixes a problem that can cause an NFS client application to hang, or causes a "lock already owned by thread" panic when lockmode=4.

  • Fixes a problem in the cam driver. A disk failure can cause the driver to spend too much time retrying interleaved Test Unit Ready and Start Unit commands. As a result, the logging of the hard error caused by the disk failure is delayed.

  • Fixes a problem where a file system is busy when trying to unmount it.

Patch 1058.00

continued

  • Fixes the erroneous "SAR Stats" implementation of CAM statistics. The original CAM stat's macros calculated inappropriate time deltas because they were not measured on a per-io basis, and the times did not account for overlapping i/o.

  • Fixes a problem where NFS does not update mtime and atime for special files and named pipes.

  • Fixes a route problem when you apply different subnet masks to the same Internet Class network address.

  • Fixes a panic that occurs when KZPSA resources aren't available to re-enable a channel or a device after a bus reset. The panic string is listed below:

    panic("(spo_process_rsp) ran out of memory!")

  • Fixes a kernel memory fault system panic that would occur when programs have unusually large stacks and the system needed to reclaim some of the memory through normal paging.

  • Fixes a problem with rpc where heavy traffic (such as mail over NFS) may cause performance problems.

  • Fixes a system hang caused by an infinite loop with out-of-band networking data.

  • Fixes a problem in the kernel where the INIT process hangs.

  • Fixes a problem in which the "vmstat -M" command incorrectly matches bucket numbers and bucket indices.

  • Fixes a kmf problem when the type of SCSI device dynamically changes.

  • Fixes a deadlock that can occur when a thread is in sigwaitprim(), and a second signal in the sigwait set is being delievered. An example stack from of the sigwait thread is:

    simple_lock_time_violation()
    mpsleep()
    sigwaitprim()
    syscall()
    _Xsyscall()

    And the delievering threads stack would be:

    psignal_internal()
    kill()
    syscall()
    _Xsyscall()

  • Fixes a problem when using the mt rewind command on the TZ89 tape drive. The tape subsystem returns an I/O error if there is not a 120 sec delay between the mt offline and the dump command. It also adds support for some new devices.

  • Fixes a problem with poor performance of NFS/UDP over a GigaBit Ethernet network interface (DEGPA).

  • Fixes the cause of the spurious spo_misc_errors errlog entry on 4100 class systems.

Patch 1058.00

continued

  • Corrects a problem where incorrect NFS client locking caused a KFM panic.

  • Fixes a performance problem associated with page coloring for real time applications (rt_preempt_opt=1). There is a new tunable, "vm_page_color_private", which is modified in the "vm" section of the sysconfigtab file. The default value for this variable is "0", so to enable this feature the variable must be set to "1".

  • Fixes a problem where process accounting data was not written to the accounting file when it was on an NFS-mounted file system. This problem occurred on Dataless Management Services (DMS) client systems.

  • Fixes a problem where NFS clients may hang in the uninterruptable state.

  • Corrects a problem in the Qlogic driver that could eventually result in unexpected errors or panics. This patch also corrects the following simple QLogic problems:

    • Fixes "simple_lock: time limit exceeded" panics.

    • Fixes a problem in which adapter errors are reported as disk errors.

    • Fixes a problem in which a processor may appear to hang for long periods of time when doing large, non-aligned, non-block, multiple I/O transfers.

    • Fixes a problem in which random memory corruption problems may occur when a device error is encountered and the device does not have an entry in the DDR database.

  • Fixes a kernel memory fault from ip_forward().

  • Increases the number of Ethernet multicast addresses on older DECchip 21140 sytems for improved audio and video capability.

  • Fixes the problem where in the dump of a forced crash, the trace of the thread that was active at the time of the crash contains incorrect information.

  • This patch fixes several problems in the kernel:

    • A panic with the message:

      vm_unwire: page is not wired

    • A panic with the message:

      kernel_object_bad: bad operation

    • A system hang due to deadlock between the swapin thread and ps both accessing the same task.

  • This patch fixes a panic which has the following error message:

    tb_shoot ack timeout

Patch 1058.00

continued

  • This panic seems to occur only on multi-processor 4100 machines.

  • In multithreaded programs, the fork() system call was failing to preserve the floating point state.

  • This patch fixes a sleeping sickness problem seen in Sitp tests.

  • This patch fixes a problem where the system crashes with the following error message:

    lw_remove: light weight wiring(s) found

  • This corrects a "simple_lock: time limit exceeded" panic.

  • This patch is for AOL systems running Inktomi code. It provides enabling hooks for Inktomi caching server code.

  • This patch fixed a problem where a process hangs due to recursive page faults.

  • This patch fixes a problem in which a system may panic with the following panic string:

    lock_pvh timeout

  • Fixes a problem in the AdvFS system. A domain panic message was not being written to the binary error log file.

    Note: This patch only works with versions of DECEvent 2.6 and higher.

  • Fixes the following problems:

    • A kernel memory fault system panic in routine spec_reclaim.

    • When executing the "file" command against a lat (BSD) special device, the "file" process will hang.

    • On multiCPU systems, hangs can occur in the revoke system call when multiple threads attempt to call "revoke" at the same time.

  • Fixes a problem in AdvFS which could cause thread hangs or a system panic.

  • Fixes a problem where several processes accessing the same AdvFS file can hang in ubc_lookup().

Patch 1058.00

continued

  • Fixes a problem where a system panic will occur when accessing an ISO 9660 format CDROM.

  • Fixes a kernel problem, where proper locking/reference count management was not being performed. This could result in a "lock-terminate: lock held" system panic.

  • Fixes "kernel memory fault" panics from the kernel malloc() routine when System V FIFOs created via STREAMS and fattach() are in use.

  • Fixes a problem that causes the system to panic with a kernel memory fault or "malloc_audit: guard space corruption" with osr_run as an entry in the stack.

  • Prevents delivery of data in subsequent streams messages with one read of a streams pipe. This problem only happens if the read has a message length greater than the length of the first message in the pipe.

  • Fixes a problem that occurs when running STREAMS. The system panics with a kernel memory fault in either osr_run() or osr_reopen().

  • Fixes the problem of a system hang due to corruption of a STREAM synchronization queue's forward pointer. The system hangs in the csq_cleanup() function.

  • Fixes a problem in which the system panics with one of the following error messages:

    simple_lock: uninitialized lock

    simple_lock_terminate: lock busy

  • Fixes a problem in which the system may panic with the following error message:

    kernel memory fault

  • Fixes a panic with the following panic string:

    pgmv: session leader attempted setpgrp

  • Fixes a kernel memory fault caused by a streams SMP race condition.

Patch 1062.00

OSF410-248

Patch: Fix tar To Accept -b Value

State: Supersedes patches OSF410-400258 (152.00), OSF410-400320 (243.00), OSF410-400374 (263.00), OSF410-400457 (514.00), OSF410-405587 (1016.00)

This patch corrects the following:

  • Fix pax's tar and cpio archive handling to allow filesizes greater than 4GB.

  • Fixes a problem with the tar "tv" command in reporting ownership on a file that had no legitimate owner at the time it was archived. Based on the position of the file in the archive, tar returned the owner of a previous file, or the values -973 for userid and -993 for groupid.

  • Fixes problem in which /usr/bin/pax : cpio -pl does not link files when possible, but copies them.

  • Fixes a problem with the tar and pax programs. These programs incorrectly append files to an existing archive and cause the file to become corrupt.

  • Fix tar to accept -b value as the starting point for autosizing.

  • The tar/pax program did not always read the last tape record of an archive. This caused confusion for scripts that were reading a series of archives on the no-rewind device.

Patch 1066.00

OSF410-405549B

Patch: Security (SSRT0588U)

State: Supersedes patches OSF410-400115 (16.00), OSF410-400203 (88.00), OSF410-400203B-1 (675.01)

This patch corrects the following:

  • Under enhanced security, sometimes users (even root) are unable to log in on graphics console, even after using dxdevices or edauth to clear the t_failures count.

  • On systems running enhanced security, user-written applications that call auth_for_terminal() may fail with a segmentation fault.

  • 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.

Patch 1067.00

OSF410-405551B

Patch: setacl Command Correction

State: Supersedes patch OSF410-405407B (890.00)

This patch corrects the following:

  • Corrects the problem with setacl not being able to handle a user ID beginning with a numeral.

  • Fixes a memory leak in retrieve_file_acl.

Patch 1070.00

OSF410-405533B

Patch: TPI Interface Correction

State: Supersedes patches OSF410-400171 (56.00), OSF410-400151 (44.00), OSF410-400196 (85.00), OSF410-400264 (177.00), OSF410-400385 (485.00), OSF410-400405 (547.00), OSF410-400405B (677.00), OSF410-405440B (892.00), OSF410-405522B (1069.00)

This patch corrects the following:

  • Fixes the problem of t_optmgmt() T_NEGOTIATE calls returning T_SUCCESS, but not actually negotiating the socket options. This behavior is a UNIX95 specification standard compliance bug.

  • Fixes a problem that manifests itself by the system hanging or becoming inoperable when a number of XTI connections reaches 500.

  • Resolves a hang in the xticlose() routine and a kernel memory fault in the xti_discon_req() routine.

  • Corrects a problem with the xti/streams interface module which could result in a kernel memory fault panic during use by xti application programs.

  • Fixes a mutex lock problem in TLI. The problem causes multithreaded TLI applications to block forever.

  • Fixes a problem with the implementation of the TPI interface. This problem occurs if you are using DIGITAL's XTI libxti library with a third-party (non-DIGITAL) STREAMS driver.

  • Fixes libtli/libxti to correctly handle a continuation data message still on the stream head.

  • Fixes a streams problem in libxti. The t_getprotaddr() function will cause a memory core dump if either of its second or third argument is NULL.

  • Fixes a problem in which an application using the X/Open Transport Interface (XTI) and the DECnet/OSI transport provider is unable to disconnect a rejected request.

Patch 1073.00

OSF410-253B

Patch: AdvFS Consolidated Patch

State: Supersedes patches OSF410-031 (1.00), OSF410-400105 (69.00), OSF410-400148 (41.00), OSF410-400125 (21.00), OSF410-400176 (70.00), OSF410-400176-1 (70.01), OSF410-400217 (110.00), OSF410-400228 (126.00), OSF410-400239B (160.00), OSF410-400231 (128.00), OSF410-400231-1 (128.01), OSF410-405094 (171.00), OSF410-400259 (153.00), OSF410-400259-1 (231.00), OSF410-400315 (211.00), OSF410-400344 (259.00), OSF410-405107 (279.00), OSF410-405112 (280.00), OSF410-400342 (253.00), OSF410-405120 (405.00), OSF410-092 (215.00), OSF410-118 (415.00), OSF410-400389 (481.00), OSF410-400443 (506.00), OSF410-400445 (507.00), OSF410-400449 (509.00), OSF410-400489 (552.00), OSF410-405241 (577.00), OSF410-400497 (576.00), OSF410-400476 (550.00), OSF410-400482 (537.00), OSF410-400482-1 (537.01), OSF410-126 (686.00), OSF410-163 (573.00), OSF410-405148 (608.00), OSF410-405156 (598.00), OSF410-405170 (589.00), OSF410-405172 (638.00), OSF410-405205 (631.00), OSF410-405214 (622.00), OSF410-405215 (652.00), OSF410-156B (671.00), OSF410-405219 (630.00), OSF410-405226 (628.00), OSF410-405228 (663.00), OSF410-405231 (635.00), OSF410-405232 (639.00), OSF410-405235 (642.00), OSF410-405239 (659.00), OSF410-405240 (641.00), OSF410-405242 (647.00), OSF410-405203 (609.00), OSF410-400482-2 (537.02), OSF410-405253-1 (661.01), OSF410-405249 (704.00), OSF410-405251 (705.00), OSF410-405275 (718.00), OSF410-405280 (723.00), OSF410-405283 (724.00), OSF410-405286 (726.00), OSF410-405298 (733.00), OSF410-405310 (742.00), OSF410-405334 (757.00), OSF410-405344 (765.00), OSF410-405385 (798.00), OSF410-405400 (808.00), OSF410-405427 (821.00), OSF410-405437 (829.00), OSF410-405438 (830.00), OSF410-405444 (834.00), OSF410-405467 (843.00), OSF410-202 (876.00), OSF410-405284 (725.00), OSF410-405323 (750.00), OSF410-405398 (807.00), OSF410-180B (884.00), OSF410-159B (885.00), OSF410-405434B (886.00), OSF410-169B (891.00), OSF410-405461 (928.00), OSF410-405484 (945.00), OSF410-405485 (946.00), OSF410-405487 (947.00), OSF410-405488 (948.00), OSF410-405489 (949.00), OSF410-405494 (954.00), OSF410-405509 (964.00), OSF410-405511 (966.00), OSF410-405534 (980.00), OSF410-405539 (984.00), OSF410-405555 (994.00), OSF410-405565 (1001.00), OSF410-405572 (1007.00), OSF410-405577 (1009.00), OSF410-405588 (1017.00), OSF410-222 (1041.00), OSF410-400437B (896.00), OSF410-243 (1057.00), OSF410-405468B (1068.00), OSF410-239B (1071.00), OSF410-241B, (1072.00)

This patch corrects the following problems:

  • Fixes two problems that occur on AdvFS systems:

    • An AdvFS data corruption problem can occur in user files. This problem will not produce either a core file or return non-zero system codes when accessing the corrupted file.

    • The verify command does not detect corrupted files.

  • Multithreaded applications that call the pthread_mutex_destroy routine may fail when there are no threads referencing the mutex. This is caused by a race condition inside the pthread_mutex_unlock code. The typical symptom will be a return value of EBUSY from pthread_mutex_destroy.

  • Fixes a problem with AdvFS in which the following two panics occur:

    AdvFS Exception  Module = 1, line = 1891
     
    kernel memory fault

Patch 1073.00

continued

  • Systems running with AdvFS and LSM under heavy I/O loads can have sluggish interactive performance. In a DECsafe environment, these systems can encounter unexpected relocation of services.

  • Idle time is reset on broadcast message when AdvFS is the root file system.

  • Fixes an AdvFS hang that could occur while running vdump.

  • Fixes a problem where AdvFS hangs in routine cleanup_closed_list.

  • Fixes a system panic with the message:

    simple_lock: time limit exceeded

  • Fixes an "ADVFS EXCEPTION, Module = 26" panic that occurs after an "advfs I/O error" console message.

  • Corrects a problem with an NFS V3 mounted AdvFS file system where under heavy I/O load, data being written to a file may be lost. Additionally, because file stats are not being saved, the file modification time may revert to a previous value.

  • Fixes a problem where the vrestore program does not report failed exit status appropriately on incomplete or incorrect commands, corrupt or invalid saved sets, or file open failures.

  • Fixes a problem that occurs on AdvFS systems. When a user exceeds the quota limits, an excessive number of user warning messages are sent to the system console if the user terminal is inaccessible.

  • Fixes a problem that occurs on systems running AdvFS. The system panics with the following error message:

            panic (cpu 0): bfs_invalidate: not on free list
            syncing disks...done

Patch 1073.00

continued

  • Fixes a problem that occurs on SMP systems with an AdvFS filesystem in which the system panics with the following message:

    simple_lock: time limit exceeded

  • When a user attempted to restore a vdump, which had been done with the "-D" option and included directories for which Access Control Lists (ACLs) had been declared, the vrestore program was failing to restore ACLs on directory files and issued warning messages. When a user specified the "-t" option, vrestore erroneously attempted to restore proplists on files that had them; issuing warning messages.

  • Fixes problems with the AdvFS filesystem commands "quotacheck -a" and "vquotacheck -a". These commands erroneously set all quotas for users to values derived from the last AdvFS fileset in /etc/fstab, rather than the correct values for each individual fileset.

  • Fixes a panic with the panic string "spec_badop called" that can sometimes occur when an fpathconf system call is issued for a file in an AdvFS filesystem. The panic has following stack trace:

    panic (s = "spec_badop called")
    spec_badop
    fpathconf
    syscall
    _Xsyscall

  • Fixes a problem in which a system hang or core dump occurs when on program inadvertently overwrites the contents of another program.

  • Fixes a problem with the vrestore command. When restoring a multi-volume tape archive, if the tapes that follow the first tape are write-protected, the following error message is displayed:

    vrestore: can't open device file

  • Fixes a problem that occurs on AdvFS systems. The system will panic with an error message similar to the following:

    panic (cpu 0): kernel memory fault

  • Fixes an AdvFS problem in which the "advfsstat -n" command causes a core dump. The system displays the following error message:

    Memory fault(coredump)

  • Fixes a problem that occurs on AdvFS systems. The chfsets function returns incorrect exit values and inappropriate error messages.

  • Fixes a problem that occurs on AdvFS systems. If the "ls -l M1" command is given in a .tags directory, the fileset will become unmountable. If the system is then halted, a panic will occur.

  • Fixes an AdvFS problem in which improper handling of I/O queues cause either a kernel memory fault or the following panics:

    bs_invalidate: cache rundown
     
    rm_or_moveq: ioDesc not on a queue

Patch 1073.00

continued

  • Fixes a problem that occurs on an AdvFS file system. While the symptoms of these AdvFS problems vary, the most common is a panic with the following error message:

    bs_frag_alloc: pinpg faild\n N1 = -1035

    Alternately,

    bs_frag_dealloc: pinpg faild\n N1 = -1035

  • Fixes a system panic when shutting down to single user mode using one of the following commands:

    # shutdown now
    # init s

    when AdvFS is the root or usr filesystem.

  • Fixes the following problems on systems with the AdvFS filesystem:

    • The mcellCount on-disk was not being updated as files were being migrated and this resulted in a panic situation during defragment and migrate operations.

    • A race condition on can result in a system panic with the following error message:

      panic (cpu 0): bs_frag_alloc: pinpg faild

    • During defragment and migrate operations, a lock is not released which hangs the system next time a thread tries to obtain the lock.

    • When executing /sbin/advfs/verify command on an unmounted AdvFS domain, the system will panic with the following panic string:

      panic_string:  0xfffffc00006cad90 = "kernel memory fault"

  • Adds features and corrections to the AdvFS verify utility.

  • Fixes an AdvFS problem that causes the system to panic with the following error message:

    simple_lock: lock already owned by cpu

  • Race conditions occur due to threads seeing out-of -date extent maps.

  • Fixes a problem with in-memory extent map locking that occurs on AdvFS systems. The problem can cause panics due to kernel memory faults or simple lock timeouts.

  • Corrects a problem where the mcellCount on-disk was not being updated as files were being migrated and this resulted in a panic situation.

  • Corrects a kernel read fault panic condition that occurs when the AdvFS verify utility runs. The panic message looks like:

    trap: invalid memory read access from kernel mode
    panic (cpu 0): kernel memory fault

  • Fixes a race condition that occurs on an AdvFS file system. The system panics with the following error message:

    panic (cpu 0): bs_frag_alloc: pinpg faild

Patch 1073.00

continued

  • Fixes a problem that occurs on an AdvFS file system. An AdvFS lock is not released which hangs the system next time a thread tries to obtain the lock.

  • Fixes AdvFS performance problems.

  • Fixes a problem in which vrestore can cause an occasional core dump (Foating Exception).

  • Fixes a problem that occurs on AdvFS file systems. A kernel memory fault occurs on the AdvFS file system when accessing nfs-mounted files.

  • Provides a performance improvement for AdvFS systems.

  • Corrects a situation where a quotacheck can cause a system panic.

  • A system using an AdvFS clone fileset can panic with either a kernel memory fault in bs_real_invalidate_pages(), or with the panic string:

    bs_real_invalidate_pages: buf refd or pinned

  • Corrects a panic and hang situation due to a limit of AdvFS access structures.

  • Fixes a problem caused by the vdump command. When a user entered Ctrl/C to terminate a vdump operation, the command returned an incorrect status and mistakenly updated the /etc/vdumpdates file.

  • Fixes an kernel memory fault panic. The system displays the following error message:

    trap: invalid memory read access from kernel mode

  • Corrects a problem where the mcellCount on-disk was not being updated as files were being migrated and this resulted in a panic situation.

  • Corrects a problem with domain panics that could possibly cause the system to panic. A new AdvFS error number (E_DOMAIN_PANIC) (-1028) was created.

  • Fixes a problem that occurs when the user attempts to fill an AdvFS: The system crashes and displays the following panic:

    lock_write: hierarchy violation

  • Adds features and corrections to the AdvFS verify utility. The verify utility now detects and reports some file system corruption problems it had previously ignored. It also no longer gives seek errors on really large frag files (>2GB); gives detailed warning messages when a frag file is found to be incorrectly terminated, helping the user to know which file's fragments are involved; gives a useful error message when the root_domain is mounted read-only, preventing it from investigating other domains; properly handles domains that have clones; and properly handles SBM fixups (code which was intended to correct corrupted pages in the SBM metadata file fixed the page in memory but then wrote the newly corrected page over the NEXT page in the SBM.) Also increases the amount of memory available to the program so that large memory systems can be worked with.

  • Fixes a problem caused by the vrestore command. The command would fail when restoring multiple savesets from a TZS20 tape drive.

Patch 1073.00

continued

  • Fixes a problem that occurred when an AdvFS panic crashed the customer's system but the visible symptom was a crash due to a kernel memory fault.

  • Fixes a problem in the chvol command. chvol was not recognizing LSM volumes.

  • Prevents a "kernel memory fault" in the msfs_reclaim() routine on systems using AdvFS.

  • Fixes a problem with the chfsets command. When a root user exceeded the fileset quota (which root is allowed to do), the chfsets command reported negative values for the free and available blocks in the fileset.

  • Fixes a kernel memory fault problem that occurs on AdvFS file systems. The system displays the following error message:

    panic: kernel memory fault at spec_reclaim()

  • Fixes an AdvFS problem that occurs when unmounting a domain. An unmount thread was waiting on a variable to be set to zero before continuing, but the routine that was to set the variable to zero never did.

  • Fixes a problem that crashed the system while it was running a "collision" test. The process would hang on a lock, never be woken, and crash the system.

  • Fixes a problem with the AdvFS fs_write routine, which would mishandle partial writes after detecting an error.

  • Corrects a problem where a panic would occur when running rmtrashcan on a clone.

  • Fixes a problem with AdvFS, which caused a system panic with the following message:

    log_flush_sync:  pingpg error

  • The system panic occurred when the AdvFS domain had already issued a domain panic and a user application then attempted to close a file in that domain.

  • Fixes a problem in AdvFS that produced the following system panic:

    bs_logflush_start:  cannot write lsn

  • Fixes a problem with messages in system logs that reported AdvFS user and group quota limits. The messages were unclear; the user could not determine from them which users or groups were reaching the quota limits.

  • Fixes several problems associated with AdvFS tag files and directories, including displays of erroneous data and system panics.

Patch 1073.00

continued

  • Fixes a problem in AdvFS locking code which causes the following panic:

    kernel memory fault

  • Fixes a problem in AdvFS that was causing a memory leak.

  • Fixes a problem with AdvFS that caused a page fault and the following panic:

    panic (cpu 0): kernel memory fault

  • Fixes two AdvFS problems:

    • An error message was misleading when a DIGITAL UNIX Version 4 system attempted to access a file domain created by DIGITAL UNIX Version 5.

    • A state field in an AdvFS data structure was initialized, but not maintained.

  • Fixes a problem where a system hang can occur when creating an AdvFS file system, such as on "/ "or "/usr" partitions, on small memory systems (e.g., 32-64 mb).

  • Fixes a problem where user files or the AdvFS frag file could lose data, if they are updated during an AdvFS migration (that is, during a balance, defragment, migrate, or rmvol of their AdvFS domain).

  • Fixes a problem in AdvFS, which causes a system panic when a truncate operation is performed on a file:

    log half full

  • Fixes a problem with the vrestore command. The command had returned a success status code even though it had restored an incomplete file during the operation.

  • Fixes several problems with the vrestore command, all related to handling and parsing of terminal I/O:

    • Interactive shell's handling of space characters.

    • Displaying of files containing non-printable characters to a terminal during interactive's ls command, -t, -v, or -l options.

    • Interactive mode commands piped from stdin.

    • Prompting and requesting of input from a terminal during ctrl-c signal handling.

  • Fixes three verify command problems:

    • The command was displaying a large volume of meaningless data.

    • When it encountered a nonrecoverable error, the command did not properly exit.

    • The command sent some error messages to stderr, some to stdout.

  • Fixes a problem in the AdvFS system. The log file corruption caused panics during recovery and failures displaying one of the following messages:

    ftx_fail: lgr_read failure

    or

    ftx_fail: dirty page not allowed

Patch 1073.00

continued

  • Fixes a problem that occurs on AdvFS systems. The system will panic with the following error message:

    malloc_overflow: guard space corruption

  • Fixes the following problems in AdvFS:

    • A operating system hang condition. The hang condition exists due to processes deadlocking in the AdvFS code.

    • AdvFS does not return an error when a user opens a file in O_SYNC mode and power is lost on the disk drive.

    • A locking error in the AdvFS fs_write() routine.

  • Fixes an AdvFS problem that occurs when the rmvol command is stopped before the commmand successfully removes a volume from a domain. As a result, the showfdmn and addvol commands interpreted the volume as still in the domain (although with no data available) and a balance operation returned the following AdvFS error message:

    get vol params error EBAD_VDI (-1030)

  • Fixes a problem in which the vquota, vedquota, quota, edquota, dump, csh, and nslookup commands will sometimes display incorrect error messages for non-English locales.

  • Enhances the AdvFS verify utility to detect incorrect "holes" in frags file.

  • Fixes an AdvFS problem, which can allow I/O requests to bypass the ready lazy queue.

  • Fixes the following two problems in the AdvFS system:

    • An error path when the system is running out of vnodes.

    • A system hang due to access structures that should not be on the closed list.

  • Fixes a problem in the AdvFS system. The system hangs due to a deadlock between update daemon sync() syscall processing in AdvFS and the truncation of AdvFS file.

  • Fixes a problem that occurs when vrestore is run from a script. Control c input to vrestore run from a script is not processed correctly.

Patch 1073.00

continued

  • Corrects a problem observed when using the edquota command under the Advanced File System (AdvFS). The edquota command may display an incorrect grace period.

  • Fixes the following problems:

    • A potential system hang when inactivating an AdvFS domain (QAR 65739).

    • A potential problem during AdvFS domain activation that can cause an AdvFS domain to be unmountable (QAR 64945).

  • Provides the following fixes and enhancements to AdvFS:

    • AdvFS volumes were not setting the default I/O byte transfer size to the preferred size reported by the disk drives.

    • AdvFS chvol read and write transfer size range was increased.

    • The read-ahead algorithm was modified to improve performance under certain conditions.

  • This enhancement for the /sbin/advfs/verify utility allows it to detect loops in the list of free frags kept in the frags file.

  • Make vrestore work with QIC-120 and QIC-150 tapes.

  • Fixes a problem in which a system can hang because cleanup_closed_list() can go into a loop.

  • Fixes two problems with the vrestore command. First, the command was slow to complete when a partial restore operation was requested. Second, the command failed to ignore extended attribute records for the files which were not requested for a vrestore operation.

  • Fixes a problem with AdvFS that will cause the system to panic with "kernel memory fault" in audit_rec_build().

  • Fixes a problem where the "statfs" system call was reporting incorrect block usage on AdvFS filesets. As a side effect of this problem, the sendmail utility may sleep needlessly (waiting for space to become available).

  • Fixes a problem on systems using the AdvFS filesystem, where the system can panic with the panic string, "del_clean_mcell_list: no primary xtnt record".

Patch 1073.00

continued

  • Fixes two AdvFS problems:

    • When an AdvFS volume is nearly full, AdvFS files may become corrupt as they are closed. The verify utility can be used to detect this "overlapped frag corruption" problem.

    • The truncation of the fragment bitfile was erroneously being turned off. This feature allows AdvFS to give back disk space periodically.

  • Fixes a problem in which the update daemon can hang.

  • Fixes a problem in the AdvFS system. A domain panic message was not being written to the binary error log file.

    Note: This patch only works with versions of DECEvent 2.6 and higher.

  • Fixes the following problems:

    • A kernel memory fault system panic in routine spec_reclaim.

    • When executing the "file" command against a lat (BSD) special device, the "file" process will hang.

    • On multiCPU systems, hangs can occur in the revoke system call when multiple threads

  • Fixes a problem in AdvFS which could cause thread hangs or a system panic.

  • Fixes a problem where several processes accessing the same AdvFS file can hang in ubc_lookup().

Patch 1074.00

OSF410CDE-009

Patch: Security, (SSRT0431U, SSRT0525U, SSRT0580U)

State: Supersedes patches OSF410CDE-400008 (94.00), OSF410CDE-400015 (526.00), OSF410CDE-405021 (1026.00)

This patch corrects the following:

  • 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.

  • Fixes a problem with the CDE desktop login screen in which logins for users with 8-character login names are rejected.

Patch 1075.00

OSF410X11-405016B

Patch: Motif Toolkit Correction

State: Supersedes patches OSF410X11-400015 (132.00), OSF410X11-400020 (283.00), OSF410X11-405009-1 (669.01), OSF410X11-405010B (902.00)

This patch corrects the following:

  • Fixes a Motif toolkit drag-n-drop operation failure that may cause Motif applications to abort.

  • Fixes the memory leak in the Motif text widget when changing colors using XtVaSetValues().

  • Fixes a small memory leak in the Motif text widget.

  • Fixes the Motif tear off menu core dump problem. The problem is seen when the tear off menu from a pulldown menu is closed/destroyed.

  • Fixes a problem with Motif Drag-and-Drop where if a parent drop site was unregistered before a child drop site, subsequently unregistering the child drop site would cause a segmentation fault.

Patch 1076.00

OSF410-405552B

Patch: Security (SSRT0556U)

State: Supersedes patches OSF410-400331 (219.00), OSF410-400331B (220.00), OSF410-400331B-3 (233.03)

This patch corrects the following:

  • Allows the uusend, uustat, uucpd, and uudecode commands to work correctly when the customer builds a hashed passwd database using a non-default page file block size.

  • A potential security vulnerability has been discovered, where under certain circumstances users may gain unauthorized access. Compaq has corrected this potential vulnerability.

Patch 1077.00

OSF410-217B

Patch: Various AdvFS Corrections

State: Supersedes patches OSF410-405320 (748.00), OSF410-405408 (813.00)

This patch fixes the following problems:

  • Fixes a problem with an unclear AdvFS message. When trying to mount an AdvFS fileset on a system that did not have AdvFS installed, the following message was displayed:

    No such device

    Now, in similar cases, the following AdvFS message is displayed:

    Cannot mount AdvFS fileset, AdvFS not installed

  • Fixes a problem with AdvFS and links in the /etc/fdmns directory. Previously, AdvFS did not ensure that every link in a directory entry pointed to a block device. Now, it does.

  • Fixes a problem with the mount command where it sometimes kills other processes.

Patch 1078.00

OSF410-405575B

Patch: Static Library Fix for LMF

State: New

This patch corrects the following:

  • Segmentation fault in /sbin/loadsrv.

  • In the License Management Facility, incorrect amount of memory is copied, which potentially can cause data corruption.