Internet Express for Tru64 UNIX Version 6.8 Release Notes (14235)

8 Restrictions and Use of the SLP Software
The SLP software kit described is included with Internet Express and contains the library, daemon,
and examples that enable a system administrator to evaluate and implement the use of SLP on
a Tru64 UNIX Version 5.1A or later operating system.
Asynchronous operation is not supported in this release.
The language-specific handle is ignored. If you register a service with a language-specific handle,
when requesting services with a specified language handle you will receive all language handles.
9 PostgreSQL Server May Fail To Shut Down With Internet Monitor Running
The PostgreSQL shutdown routine /sbin/init.d/postgres stop may timeout and fail to
shutdown the PostgreSQL server when the Internet Monitor is running. If the stop procedure
outputs the message pg_ctl: postmaster does not shut down and there are still
PostgreSQL connections to the dcs or dcsconfig database, then you must stop the Internet Monitor
to allow the PostgreSQL server to finish shutting down.
To determine if there are connections to the dcs or dcsconfig databases, run the following
command:
# ps -U postgres | grep dcs
Look for commands similar to postgres: dcs dcs or postgres: dcs dcsconfig.
See the Internet Monitor Administrator's Guide for more information on how to shut down this
service.
10 PHP Session Issue With TruClusters
PHP session information is stored by default in the /tmp directory which, on a Tru64 UNIX
cluster, is a CDSL path. Also, since the Secure Web Server is a multinode application, PHP sessions
may appear to be dropped or session information may not be retrieved consistently between
requests. Both IMP Webmail (IAEIMP subset), and User Self-Administration (IAEADM subset),
use PHP session support. To eliminate this problem, set the session.save_path variable in
the /usr/internet/httpd/conf/php.ini configuration file to a non-CDSL directory (one
that is shared by all nodes of the cluster). After editing this file, you must restart the Secure Web
Server by running /sbin/init.d/httpd_public cluster-restart.
11 Tomcat Default Context
If an existing Tomcat installation is updated, and Tomcat is configured to be a standalone server,
it is likely that the Tomcat server will not have a default root context configured. If a default root
context is not present, then Web browser request will return a HTTP status 500 - No Context
configured to process this request. To correct this problem, modify the server.xml configuration
file adding a default root context.
12 Tomcat and Squid Default to the Same Network Port
The Tomcat Java Servlet Engine configured as a standalone server and the Squid Proxy both
have an default port of 8080 during installation. If both packages are to be installed, then care
must be taken that both servers are not configured to use the same port.
13 Security of Tomcat Administration and Management Applications
The version of Tomcat shipped with this release contains Web-based applications for administering
the Tomcat deployment and for managing the lifecycle of Web applications running within the
Tomcat container. Links to these management applications can be found on the Tomcat
management page within the Secure Web Server Administration utility. Links to the applications
can also be found on the Tomcat start page that is installed by default at /tomcat beneath any
8 Restrictions and Use of the SLP Software 5