test

Solaris Easy Access Server 3.0 Release Notes

Chapter 3 Late-Breaking Runtime Bugs

This chapter covers issues that may occur while you are using Solaris Easy Access Server 3.0 software.

Language Availability on Solaris and SEAS Product CDs

The Solaris operating environment on the Solaris product CD is available for installations in the following languages: English, French, Italian, German, Spanish, and Swedish.

In this release, the Solaris Easy Access components on the SEAS 3.0 product CD are available for installation in the English language only.

Solaris DiskSuite Bug

The known issue with Solaris DiskSuiteTM is listed in the following section.

DiskSuite's Metatool is Still Titled as v4.2-dev (in locale C) [4175002]

The primary metatool window title bar has the wrong message displayed. Instead of saying "DiskSuite Tool v4.2 - Metadevice Editor machine name," the word dev is a suffix to the v4.2.

Solaris Management Console Bugs

The known issues with Solaris Management Console (SMC) are listed in the following sections.

SMC Servlet May Crash Due to Insufficient Swap [4166571]

If the machine on which the SMC Server is running does not have sufficient swap space and the Java garbage collector is not given enough time to release allocated memory, the servlet may run out of memory and cause a segmentation fault.

As a result, all client machines disappear and the initial server remains with a red slash through it, indicating that it is not available.

Workaround: To resume, become superuser and restart the SMC servlet by executing these commands:

/etc/init.d/ehttpd stop

/etc/init.d/ehttpd start

This problem can be avoided by spacing authentication requests far enough apart to allow the Java garbage collector to do its work, adding sufficient swap space, or periodically restarting the servlet or rebooting the machine.

SMC Clients on the Same Server Do Not Update Each Other When Registry Changes [4168704]

If multiple clients are accessing the same SMC server, and one of the clients updates the SMC registry on the server, the others will not be notified of the change. SMC displays only the old registry information in the Applications View and SMC Server View. This out of sync display causes Already exists errors being reported to these older clients when they attempt to manually add the same registry changes.

Workaround: Log out and back in again to refresh the SMC client display.

No Default SMC pam Entry in /etc/pam.conf file [4168726]

SMC uses smc_console as its pam service name when SMC calls pam_start(). The default /etc/pam.conf file does not have an entry for the smcconsole service. This causes pam to correctly use the pam module other in pam.conf, which refers to the pam_unix module.

SMC Applications Can Be Modified by Any User [4169897]

Applications that are registered with Solaris Management Console to be launched with user, root or group 14 permission can be modified or removed by any user.

Workaround: None

Launched Applications May Not Display When Running SMC Client Via Remote xhost [4171154]

When running SMC client on a remote xhost, launched applications may not be displayed.

Workaround: Add each remote server to your X authorization list, for example xhost + .

AnswerBook2 Bugs

The known issue with AnswerBook2 is listed in the following section.

AnswerBook2 Package Size Anomalies Reported by pkgchk [4167646]

The pkgchk -n command reports package size anomalies for AnswerBook2 packages installed from the Document CD. These anomalies result from post-install processing of AnswerBook2 packages. These size anomalies do not affect AnswerBook2 collection integrity and can be ignored.

Workaround: None

Netscape 4.51 Issues

The known issues with OpenWindows Communicator 4.51 are listed in the following section.

Solaris 2.6/OpenWindows Communicator 4.51 Does Not Render Fonts Properly

Solaris 2.6/OpenWindows Communicator 4.51 does not render Type 1 fonts properly.

Workaround: A patch for OpenWindows 3.6 fixes this problem, and is available on the Netscape Communicator 4.51 CD in the following directory structure:

You may also download Solaris OS Patch Clusters directly from Sun.

After you install the patch, exit your window manager (for example, CDE or OpenWindows) , then log in to your window manager again.

Sun WebServer 2.1 Issues

The known issues with Sun WebServer 2.1 are listed in the following section.

Sun WebServer 2.1 Does Not Install Correctly When Installed to a Non-Default Location

When you install the Solaris Management Console to its default directory location, and Sun WebServer 2.1 to a non-default location, Sun WebServer 2.1 does not install correctly.

Workaround:To resolve this issue proceed as indicated below.

To Reinstall Sun WebServer to Its Default Directory Location

  1. Start the Solaris Product Registry from either the Solaris Management Console, or by typing % /bin/prodreg at a system prompt.

  2. Select Sun WebServer and click Full Uninstall to remove Sun WebServer 2.1.

  3. Start SEAS 3.0 Web Start again and install Sun WebServer to its default location.

Wrong Mod Time Error Messages Can Be Ignored

The Sun WebServer installation log under /var/sadm/install/logs contains a lot of warnings saying Wrong mod time. These messages are benign and only occur when you install Sun WebServer 2.1 from the SEAS 3.0 domestic product CD. This problem does not occur when installing Sun WebServer 2.1 from the SEAS 3.0 global product CD.

Help Window Stalls When Selecting Topics

In the Solaris Management Console 1.0 when you choose Contents from the Help menu to open the user help, the Help window may stall if you select the Help topics listed in the right pane of the Help window. This issue only occurs on Solaris 7 systems and it is intermittent.

Workaround: Select the corresponding main chapter headings listed in the left pane of the Help window and then select the Help topic you want.

Java and JDK Issues

The known issues with the Java Development Kit are listed in the following section.

JDK Version on the Asian Language SEAS Product CD

The JDK version on the Asian SEAS 3.0 product CD is version 1.1.7_08.

Coexistence of Java Programs in SEAS 3.0 with Java 2

Release 8/99 of Solaris 7 was the first release to provide JDK 1.1 and JDK 2. The /usr/java link determines the default JDK used on that system. When you manually change the version number from JDK 1.1 to JDK 2, Java programs in SEAS 3.0 will no longer work.

Workaround: SEAS 3.0 should be run with Java 1.1 and not Java 2. If you changed the JDK version number, change it again to point to JDK 1.1.

PC NetLink 1.1 Issues

The known issues with PC NetLink are listed in the following section.

Note -

PC NetLink is also referred to as SunLink Server.

Windows NT 4.0 with Solstice Network Client 3.x Causes A PC NetLink NT Printer Share to Fail

Windows NT 4.0 with Solstice Network Client 3.x causes a PC NetLink NT Printer Share to fail and displays the following error message: Printer driver for Windows NT 4.0 x86 could not be installed. This function is only valid in Windows NT mode.

Workaround: Share PC NetLink printers from an NT 4.0 system that does not have Solstice Network Client 3.x (SNC) installed on it. The SNC 3.x NT systems will be able to see the Printer shares and install the printer locally without difficulty.

To check the presence of SNC 3.x on an NT 4.0 system, open Services in the Network dialog box in the Control panel. If Network Services lists "Solstice NFS Client" and/or "Solstice File Sharing" entries, then SNC 3.x is installed on that system. If necessary, remove SNC 3.x through the Add/Remove Programs() function in the Control Panel.

SunLink Server Manager Will Not Use A Secondary WINS Server if the Primary WINS Server is Still Functioning

Unlike a native Windows NT environment, the SunLink Server program will not use a secondary WINS server if the primary WINS server is still functioning. If a SunLink Server computer is functioning as the primary WINS server, and attempts to locate a resource that does not exist in its WINS database, the SunLink Server NetBIOS will not automatically consult the secondary WINS server for that resource. In this regard, a SunLink Server computer configured as a primary WINS server does not behave in the same way as a native Window NT primary WINS server.

Workaround: This issue will not become a problem for most environments. To preclude this from becoming a problem, either point all servers that need to communicate with each other to the same primary and secondary WINS servers, or replicate all WINS servers.

The passwd2sam -m Used on a BDC Causes Problems

When used on a BDC, the passwd2sam -m option may:

These problems do not occur when the command is used on a PDC.

Workaround: Do not use the passwd2sam -m on a BDC.

Using SunLink Server Software and Microsoft Terminal Server Together Causes Synchronization Problems

If SunLink Server software and Microsoft Terminal Server are used together in a domain, domain synchronization problems will occur. When both these tools are used in a domain, user's Terminal Server configuration parameters will not be synchronized.

Workaround: Install SunLink Server software in a separate "resource" domain that trusts another "account" domain.

Auto-mounted Solaris Home Directories Are Not Always Automatically Available to Windows NT Clients

Note -

The following description and workaround is intended for experienced Solaris system administrators only.

Solaris home directories that are stored remotely are ordinarily mounted automatically when users need to access their accounts. The current release of SunLink Server is not able to provide automatic access from Windows NT clients to Solaris home directories that are not stored on the SunLink Server system. However, home directories that are stored on the same system as the SunLink Server program are available to Windows NT clients.

The reason for this is that the autofs file system monitors all attempts to access directories, and if the file system is not accessed within a default period of five minutes, the file system becomes unmounted. Therefore, if a net share operation is performed on /home and then the share is connected from the client, the access to the home directory will be unmounted. This is because the autofs daemon does not detect that the user is accessing the directory from the Windows client system.

Workaround: Change the auto-mount master map entry for /home from --nobrowse to --browse so that SunLink Server can see the subdirectories of /home.

PC NetLink Must be Installed in English Locale

When installing PC NetLink on a system running the Solaris operating environment in a European language, the graphical interface of PC NetLink will appear in the corresponding language, but none of its functionality will be available.

Workaround: Before using PC Netlink, open a terminal window and set the locale to English. Then start the graphical interface of PC NetLink from the terminal window.

Solstice Adminsuite 3.0 Issues

The known issues with Adminsuite are listed in the following section.

The User Properties List of Rights Is Not Translated

The Rights tab of the User Properties dialog box lists all possible user rights for the domain that you are currently managing. This list is in English because the rights shown are obtained from tables that cannot be translated in this version of the product. To learn more about the rights, refer to the context-sensitive help provided when clicking on each right shown in the Rights tab.

No Multi-Byte Characters Are Accepted in AdminSuite Dialog Boxes

You cannot enter multi-byte characters in any of the AdminSuite dialog boxes, and specifically in the description fields.

Workaround: Click anywhere in the HTML renderer pane in the left side of the dialog box. Then press the Ctrl and Space keys (or whatever control sequence is configured). Note that the pre-edit status windows show up; by default, this is at the bottom of the dialog box. Toggle the control sequence until it is in the input mode that you want, and then click on the field in which you want to enter multi-byte characters. If the pre-edit status window disappears, try the work-around again, starting with clicking anywhere in the HTML renderer pane.

Sun Enterprise Authentication Mechanism 1.0 Issues

The known issue with SEAM 1.0 is listed in the following section.

FTP: Strange Transfer Time is Displayed on get and put Commands

Whenever you use the FTP get and put commands, strange transfer time is displayed. For example:


458 bytes received in 2.7e+154 seconds (2.7e+154 Kbytes/s)458 bytes received in --1.5e-154 seconds (-2 Kbytes/s)

No workaround is available.