Technical article 110105

What is SLS OSS497C, the Core OS Supplement for SCO OpenServer Release 5.0.5?

OpenServer 5.0.5

Written · Last revised

Problem

What problems are addressed by Support Level Supplement (SLS) OSS497C, the Core OS Supplement for SCO OpenServer Release 5.0.5?

Solution

SLS OSS497C addresses several known issues with the kernel, networking, and SMP components of SCO OpenServer Release 5.0.5 operating systems.

See the attached cover letter for more information about this SLS, including a list of specific problems addressed and installation instructions.

Dear SCO Customer,

Support Level Supplement (SLS) OSS497C, the Core OS Supplement for SCO OpenServer Release 5.0.5, addresses several known issues with the kernel, networking, and SMP components of SCO OpenServer Release 5.0.5 operating systems.

SLS OSS497C corrects these problems: Note: The following fixes were also included in SLS OSS497A:

1.  'brand -g -a' coredumped if the nodelock file was empty, instead of
    populating it.  Associated SCO Tracking Numbers: SCO-236-1427/
    SCO-236-1421/ 710673
2.  Remote printers sometimes failed to appear in the Printer Manager and
    lpstat.  Associated SCO Tracking Numbers: SCO-236-1425/ SCO-236-1426/
    LTD-245-2812/ 500914/ 710663/ 710664
3.  If the login delay (the t_logdelay field in /etc/auth/system/default)
    was set to zero, the passwd generator would generate passwords of an
    incorrect length.  Associated SCO Tracking Numbers: SCO-236-904/ 710643
4.  The cron utility would get "stuck" waiting for long jobs to complete,
    blocking its ability to accept and run new "at now" jobs promptly.
    Associated SCO Tracking Numbers: LTD-246-1342/ 500904
5.  SCO PPP with dynamic CHAP authentication would fail.  There is now a
    wildcard CHAP secret that can be used.  Associated SCO Tracking Numbers:
    SCO-236-1167/ 710427
6.  Deleting circular routes would cause a kernel panic.  Associated SCO
    Tracking Numbers: SCO-59-9633/ 500854
7.  Running a large number of simultaneous fsck's after an irregular
    shutdown could result in a kernel panic.  Associated SCO Tracking
    Numbers: SCO-236-1397/ 500802
8.  After installing SLS OSS491A, netconfig, scosh, and certain full-screen
    text applications hung.  Associated SCO Tracking Number: SCO-236-1432
9.  hpnptyd ran in an endless loop.  A new pseudo-tty driver was originally
    shipped in SLS OSS491A to address this problem, but caused problems
    with some applications (see above).  A fix to the hpnptyd program now
    addresses this problem.  Associated SCO Tracking Numbers: SCO-247-112/
    500794
10. The Bourne shell(sh) improperly handled window size changes.  Associated
    SCO Tracking Number: SCO-59-9705

11. Certain TLI and XTI connections hung during connection startup. Associated SCO Tracking Numbers: SCO-236-1447/ LTD-246-1321/ 710577/ 710718

12. Some machines panicked at 'G mp_pciinit'.  Associated SCO Tracking
    Numbers: LTD-246-1346/ 500871
13. Tuning the NSTRPAGES kernel parameter to its maximum value did not
    work.  Associated SCO Tracking Numbers: SCO-236-1125/ 710502
14. Systems could panic in the kmem_alloc call.  Associated SCO Tracking
    Numbers: SCO-242-160/ 710657
15. Systems could panic in tcp_linput() or in_pcballoc() called from
    tcp_linput().  Associated SCO Tracking Numbers: SCO-236-1439/ 710699
16. TCP performance needed improvements on systems where the network card
    was dropping packets.  Associated SCO Tracking Numbers: LTD-246-1252/
    500604/ 710669
17. Some systems could get a "too many sptfrees while flushing TLBs"
    message.  Associated SCO Tracking Numbers: SCO-236-1442/ 710712
18. HTFS uses a "synchronous log" file named .slog000 to enhance the
    performance of synchronous writes.  This file was not intended to be
    visible to applications or users, but in some circumstances, could
    become visible, causing backup applications to fail.  Associated SCO
    Tracking Numbers: SCO-236-1446/ 500943

Note: The following fixes were also included in SLS OSS497B:

19. /bin/sh from SLS OSS497A coredumped when adding or removing a scrollbar in a scoterm.

20. lpd did not properly move requests to the local print server queue. Associated SCO Tracking Numbers: SCO-242-117/ 500741

Note: The following fixes are new to SLS OSS497C:

21. /bin/sh from SLS OSS497B introduced a problem in which stty in .profile
    would stop profile execution.  Associated SCO Tracking Numbers:
    SCO-236-1564/ 710978
22. Permissions on lp binaries were incorrect in OSS497B. Various lp
    fixes are included.  Associated SCO Tracking Numbers: SCO-210-171/
    LTD-246-1399/ LTD-245-2829/ LTD-246-1281
23. On multiprocessor systems, assigning an interrupt to a CPU could fail
    with the message, "iattr_add_to_shared_chain failed." Associated SCO
    Tracking Numbers: SCO-236-1469/ 710769
24. Allows disabling of the warning message, "Too many sptfrees while
    flushing TLBs," via kernel/space.c tunable suppress_sptfree_msg
    Associated SCO Tracking Numbers: SCO-59-9912/ 710820
25. When running low on streams memory, all networking activity could
    cease for several minutes.  Associated SCO Tracking Numbers:
    SCO-59-9910/ 710760
26. A panic can occur in "table_grow" when total memory is very
    limited.  Associated SCO Tracking Number: SCO-59-9907

27. The following warning message could occur with certain serial I/O hardware: "kmem_alloc: called at interrupt time without KM_NOSLEEP." Associated SCO Tracking Number: SCO-59-9909

28. TCP applications in which the receiver had stopped reading could result
    in a depletion of streams memory.  Associated SCO Tracking Numbers:
    SCO-236-1467/ 710760
29. A panic could occur in "dlpi_unlink" under conditions in which the
    network card had stopped responding.  Associated SCO Tracking Numbers:
    SCO-242-144/ 710634

30. Certain broadcast packets could lead to depletion of streams memory. Associated SCO Tracking Numbers: SCO-236-1508/ 710865

31. The link kit file "arp/space.c" contained the wrong definition of the data structure "arp_pcb[]", which might lead to a panic.

SLS OSS497C contains these files:

/bin/passwd /bin/sh /etc/brand /etc/conf/pack.d/apic/Driver.o /etc/conf/pack.d/Sdsk/Driver.o /etc/conf/pack.d/ip/Driver.o /etc/conf/pack.d/kernel/os.a (modules page.o, startup.o, sys2.o, valloc.o, dynamic.o) /etc/conf/pack.d/kernel/io.a (modules xmap.o) /etc/conf/pack.d/kernel/space.c /etc/conf/pack.d/str/space.c /etc/conf/pack.d/crllry/Driver.a (modules mppic.o) /etc/conf/pack.d/rte/Driver.o /etc/conf/pack.d/spt/Driver.o /etc/conf/pack.d/str/Driver.o /etc/conf/pack.d/str/space.c /etc/conf/pack.d/arp/space.c /etc/conf/pack.d/tcp/Driver.o /etc/conf/pack.d/ip/Driver.o /etc/conf/pack.d/net?/Driver.o /etc/cron /etc/debrand /etc/pppd /opt/K/SCO/Unix/5.0.5Eb/sa/printer/printerOsa /usr/bin/lpstat (/usr/lpd/local/lpstat if remote printing is configured) /usr/include/sys/netinet/tcp_var.h /usr/lib/hpnp/hpnptyd /usr/lib/lpadmin /usr/lib/lpd /usr/lib/lpsched /usr/lpd/remote/lp /usr/lpd/remote/lpstat /etc/rlpconf

Software Notes and Recommendations
----------------------------------

SLS OSS497C should only be installed on:

SCO OpenServer Enterprise System Release 5.0.5 with Release Supplement 505A SCO OpenServer Host System Release 5.0.5 with Release Supplement 505A SCO OpenServer Desktop System Release 5.0.5 with Release Supplement 505A

This SLS supersedes SLS OSS497A and OSS497B, however it is not necessary to remove these earlier versions prior to installing SLS OSS497C.

It is not necessary that OSS497C be installed prior to installing OSS600A, the Y2K SLS for SCO OpenServer 5.0.5 + RS505A.

Installation Instructions
-------------------------
1. Prepare the media for installation.

Download the OSS497C media image file (oss497c file), place the file in the /tmp directory and rename the file by typing these commands:

mv /tmp/oss497c /tmp/VOL.000.000

2. Run the Software Manager with the command:

# scoadmin software

or double-click on the Software Manager icon in the desktop.

3. Pull down the "Software" menu and select "Install New".

4. When prompted for which host to install from, choose the local machine and then "Continue".

5. When prompted to select the media device, choose "Media Images, then
   "Continue".  When prompted for the "Image Directory", enter "/tmp"
   (or the directory where you placed the VOL file), and then select "OK".

(If you are installing this SLS from diskette media, select the appropriate floppy disk drive and then "Continue". Proceed to step 6.)

6. When prompted to select software to install, ensure that the "OSS497C" entry is highlighted. Choose "Install".

7. Once the installation finishes, quit the Software Manager.  Installation
   of SLS OSS497C is now complete. The changes will take effect the next
   time you reboot the system.

8. Log in as root on tty01, and shut down the system:

# shutdown -g0 -y

After shutting down and rebooting the machine, application of the SLS is complete.

Removal Instructions
--------------------

Notes: Patches must be rolled back in the reverse order in which they were installed on a per-component basis.

1. Log in as root.
2. Execute the command:
# scoadmin software

or double-click on the Software Manager icon in the desktop.

3. Highlight "OSS497C: Core OS Supplement for SCO OpenServer Release 5.0.5".

4. Pull down the "Software" menu and select "Remove Software".

5. Once the removal finishes, quit the Software Manager.

6. As root on tty01, shut down the system:

# shutdown -g0 -y

After shutting down and rebooting the machine, removal of the SLS is complete.

If you have questions regarding this SLS, or the product on which it is installed, please contact your software supplier.

From the Xinuos technical article database, record 110105. Reproduced with permission. The original is at www.sco.com/ta/110105, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.