survivor: Known Compatibility Problems
Scheduler (`ss`) Solaris 8 Patches Hardware Modules (`mod`) LDAP Check Module Debugging vsnprintf
Scheduler (`ss`)
### Solaris 8 Patches To run under Solaris 8, patch 108991-05 or later (and dependent patches) is required. This fixes a problem where checks run by the scheduler do not exit correctly. Other patches may be required. The development host had the following patches installed:
     108528-05 108985-01 109137-01 109729-01 109783-01 108974-08 108985-02
     109277-01 109279-06 110283-01 110662-01 108989-02 108975-03 108974-02
     109041-02 109181-02 109472-04 109874-02 109898-02 108727-05 108991-05
     109888-02 108977-01 108968-02 108827-01 109326-01 108827-05 109322-02
     109461-02 110383-01 110453-01 110700-01 109667-02 109320-01 108987-02
### Hardware A bad disk may manifest itself as unexpected scheduler behavior. For example, `lastalert()` may fail to read a file that clearly exists, and thus generate false (or incorrectly scheduled) alerts. Replacing the disk containing the survivor state filesystem may alleviate this behavior.
Modules (`mod`)
### LDAP Check Module As of v0.8.3, the LDAP Check Module uses the `Net::LDAP` Perl module. Due to a problem in that module, an error message like the following may appear:
     Received unexpected response: /^(\\.|[^\\*]*)*\*/:
     regexp *+ operand could be empty at /opt/perl/lib/site_perl/Net/LDAP/Filter.pm line 120.
This problem may appear under older versions of Perl, including 5.004. To fix, try upgrading to a newer version of `Net::LDAP` or, if possible, Perl. If upgrading does not work, please file a bug report. Additionally, `Net::LDAP` may have problems using older versions of `IO::Socket`, reporting that a server is OK with the message
     IO::Socket::INET: Connection refused at /opt/ACISperl5004/lib/site_perl/Net/LDAP.pm line 126
(Clearly, the server is not running, which is not OK.) To fix, try upgrading `IO::Socket` to a newer version. `IO::Socket` v1.24, part of the `IO` v1.20 distribution, is known to work.
Debugging
### vsnprintf Solaris versions prior to 9 do not have a threadsafe version of `vsnprintf`, which the debugging and warning library makes extensive use of. A workaround is implemented, but is theoretically subject to buffer overrun problems. Where possible, Solaris 9 should be used. Paranoid sites that cannot run Solaris 9 should disable all debugging in the `scheduler`. $Date: 2006/11/20 02:56:55 $ $Revision: 0.8 $ | keywords