dUNIX ASU50ECO2_391 Advanced Server for UNIX V5.0 ECO Summary
TITLE: dUNIX ASU50ECO2_391 Advanced Server for UNIX V5.0 ECO Summary
New Kit Date : 10-MAY-2001
Modification Date: Not Applicable
Modification Type: New Kit
Copyright (c) Compaq Computer Corporation 2001. All rights reserved.
PRODUCT: Advanced Server for UNIX V5.0
Advanced Server for UNIX V5.0 ECO1
OP/SYS: COMPAQ Tru64 UNIX
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: ASU50ECO2_391
ECO Kits Superseded by This ECO Kit: Advanced Server for UNIX V5.0 ECO1
ECO Kit Approximate Size: 63,740 Blocks
Kit Applies To: Compaq Tru64 UNIX V4.0D through V5.1
Advanced Server for UNIX V5.0
Advanced Server for UNIX V5.0 ECO1
Installation Rating: INSTALL_UNKNOWN
Kit Dependencies:
The following remedial kit(s) must be installed BEFORE
installation of this kit:
None
In order to receive all the corrections listed in this
kit, the following remedial kits should also be installed:
None
ECO KIT SUMMARY:
An ECO kit exists for Advanced Server on Tru64 UNIX V4.0D through V5.1.
This kit addresses the following problems:
ASU general problem descriptions and solutions:
----------------------------------------------
Problem Addressed:
o All files and directories created from ASU apply Tru64 UNIX
permission based on the setting of the following FileService
Parameters registry value entries:
UnixDirectoryPerms:REG_DWORD:493
UnixFilePerms:REG_DWORD:420
These settings can be somewhat limiting, especially in university
environments. The ASU server now allows you to set the value of
these registry value entries to 0 (zero) so that files and directories
created in ASU shares inherit the Tru64 UNIX permissions from the parent
directory. These settings also apply to files and directories that are
created in ASU shares that were created for exported network file systems
(nfs). Setting the UnixFilePerms entry to 0 causes newly created files
to inherit the Tru64 UNIX permissions from the parent directory however,
the 'x' execute bit will not be inherited because these files are not
Tru64 UNIX executable files.
The one exception to this are files that are created in read only
directories. Because the ASU server maps the DOS ReadOnly attribute to
the Tru64 UNIX Read permission of the User, files created in these
directories will have read/write Tru64 UNIX permission in the user field
by default.
Setting the UnixDirectoryPerms entry to 0 causes newly created directories
to inherit the Tru64 UNIX permissions from the parent directory. The 'x'
execute bit will be inherited.
Changing the value of the UnixFilePerms and UnixDirectoryPerms registry
entries will take affect when you restart the ASU server and only applies
to newly created files and directories. Renamed files and directories will
retain their original Tru64 UNIX permissions. The UnixDirectoryCheck
registry entry, which can be used to bypass Tru64 UNIX security checking,
will not affect the inheritence of permission.
o The ASU server no longer clears the Creation, Modification, or Last Access
dates when a file is renamed through the Windows 2000 Explorer.
o By default when the ASU server starts, it automatically creates a disk
share for each exported network file systems (NFS) listed in the
/etc/exports file. However, the ASU server does not maintain changes to
access permissions made to an exported NFS and therefore recreates the disk
share for each exported NFS when it starts.
Recreating disk shares causes previous customized disk share permissions
to be lost. To maintain customized disk share permissions for an exported
NFS,create the share for that directory by using net share command or
server manager.
o The acladm command has a new -T option that you can use to trim redundant
access control lists (ACLs) from the ACL database. Enter the following
commands to trim redundant ACLS, then compress the ACL database:
# acladm -Ty
# blobadm -A -q
o The ASU server would report error messages in the event log from the
browser service about the NetBEUI protocol even though the NetBEUI protocol
is disabled.
This problem has been fixed.
o Users in a Tru64 UNIX group could not delete a file that was created by
the ASU server and owned by another user in the group, even if the
Tru64 UNIX directory permissions were set to allow the group to delete the
file.
This problem has been fixed by the use of a new parameter,
overrideunixprotection, in the [ lmxserver ] section of the lanman.ini
file. By default, the value of the overrideunixprotection parameter is
set to no, which means that only the owner of a file can delete it.
Setting the value to yes allows users in the same group to delete each
other's files if the Tru64 UNIX directory permission allows it.
Note: This is an ASU server-wide parameter.
o Windows 2000 clients failed to update roaming profiles in a disk share on
an ASU Version 5.0 ECO1 server that was configured as a PDC and was using
file quotas.
This problem occurred because Windows 2000 clients had set the ReadOnly
attribute to the Recent directory, and Windows 2000 clients treat the
ReadOnly attribute as advisory. Clients can write to directories with the
ReadOnly attribute set.
When the UnixQuotas registry entry is enabled, which it is not by default,
Tru64 UNIX permissions are enforced and the ReadOnly attribute is set on
the Tru64 UNIX directory. Windows 2000 clients are bound by Tru64 UNIX
permissions and are now prohibited from writing into ReadOnly directories.
You can now use a new parameter, readonlydir, in the [ lmxserver ] section
of the lanman.ini file to control whether or not Windows 2000 clients can
write to a Tru64 UNIX directory when the ReadOnly attribute is set. By
default, the value of the readonlydir parameter is set to yes, which
enforces the ReadOnly attribute on Tru64 UNIX directories. Setting the value
to no does not enforce the ReadOnly attribute on Tru64 UNIX directories.
o Under certain conditions, a Windows 2000 system will issue a logon request
without a username. The ASU server was incorrectly logging these requests
as a security event.
This problem has been fixed. The ASU server no longer logs these events.
o The ASU server returned the incorrect error code when a client attempted
to create an existing directory.
This problem has been fixed by assigning new values of 5 or 80 to the
direxists parameter in the [ lmxserver ] section of the lanman.ini file.
The direxists parameter specifies the integer that is assigned to the
access denied error code that the ASU server returns to a client when the
client attempts to create a directory that exists. The default value is 5.
Older applications might require a value of 80.
o The ASU server did not check a Network Information Service (NIS) for the
lanman, lmxadmin, lmxguest, and lmworld user accounts and the DOS and
Other groups, and created them on the local system.
This problem has been fixed. The ASU server now checks NIS for the user
accounts and groups and only creates them on the local system if they are
not located in NIS.
o When configuring a controller for use with the ASU server, NetBIOS over
TCP/IP used the first IP address associated with the controller as the
controller's IP address. On controllers with multiple IP addresses, this
was not always the primary IP address of the controller.
NetBIOS over TCP/IP now uses the primary IP address instead of the first
IP address found.
o It was possible to configure one more controller than was allocated. This
caused memory corruption and system panics.
This problem has been fixed.
o Norton AntiVirus now scans files on ASU shares without updating the time
of the last file status change (st_ctime). This allows files to be scanned
for viruses, but not marked for incremental backup.
------------------------------------------------------------------------
ASU and TruCluster Server Version 5.x problem descriptions and solutions
------------------------------------------------------------------------
o The way in which the ASU server runs when configured in single-instance
mode (CAA) has changed. Prior to ECO 2, the ASU transports ran on all
nodes. The ASU transports will now only run on the node on which the ASU
server is running. As a result of this change, the net commands will only
work on the node on which the ASU server is running.
o Using the joindomain command will stop the ASU server. On an ASU server
that is configured in a single-instance mode (CAA), the joindomain command
also stops the ASU transports, which are needed by the joindomain command.
Use the asusetup command to reconfigure the ASU server that is configured
in single-instance mode (CAA). This problem will be fixed in a future
release.
o Reinstalling the ASU software in a cluster might result in the ASU
transports not stopping properly.
To fix this problem, you must stop the ASU server and transports on all
cluster members before you remove the ASUBASE or ASUTRAN subsets.
Enter the following command on each cluster member to stop the ASU server
and transports:
# /usr/net/servers/lanman/scripts/asuase_stop
o A single ASU server configured in a TruCluster Server environment would
unnecessarily reset timeout values.
This problem has been fixed. The ASU server no longer resets timeout
values when there are no other nodes in the TruCluster Server environment.
o The ASU server sometimes crashes when deleting a file in a TruCluster
Server environment.
This problem has been fixed.
o An ASU server configured in a TruCluster Server environment would go into
a panic state if it did not get the master node IP address. While in the
panic state, the ASU server could not open or close files on any node in
the cluster.
This problem has been fixed. When in a panic state, the ASU server now
waits a second and tries to obtain the IP address again.
o An ASU server configured in a TruCluster Server environment would not
replicate the SAM database after master node failover.
This problem has been fixed.
o The following error message might display when using the asusetup utility
to reconfigure an ASU server PDC from multi-instance mode to
single-instance mode:
ERROR: An account for this machine cannot be created.
Rerun the asusetup utility if this message displays.
INSTALLATION NOTES:
ASU Installation Instructions:
This ECO2 kit is a complete software kit that includes the features and
functionality of previous ASU software releases, and provides fixes for
the problems described in this document.
If you are installing the ASU software for the first time, change to the
directory where the ECO2 software was downloaded, enter the following
command,and follow the instructions on the screen:
# setld -l .
If you have ASU subsets installed, then you can use the asuinstallupdate
command to replace the installed subsets with the subsets in this ECO2
kit.
Alternatively, you can use the Tru64 UNIX setld command.
If you have ASDU or PATHWORKS for DIGITAL UNIX subsets installed, then you
must use the Tru64 UNIX setld command to deinstall PATHWORKS for DIGITAL UNIX
subsets and install the subsets in this ECO2 kit.
The asuinstalludpate and setld commands are described in the following
sections.
The asuinstalludpate Command
----------------------------
You can use the asuinstalludpate command to automatically replace the
installed ASU subsets with a new version and, optionally, install additional
ASU subsets.Your previous ASU configuration, registry, and user and share
databases are unaffected while the subsets are replaced and you do not need
to use the asusetup command to configure the ASU software.
The asuinstallupdate command is located in the directory where the ECO2
software was downloaded. To use the asuinstalludpate command, change to the
directory where the ASU ECO2 software was downloaded, and enter:
# ./asuinstallupdate . [subset ...]
The setld Command
-------------------------
Follow these steps to use the setld command to deinstall PATHWORKS, ASU,
or ASDU subsets and install the ECO2 software:
1. Deinstall the PATHWORKS, ASU, or ASDU subsets. To display the installed
PATHWORKS, ASDU, or ASU subsets, enter one of the following commands
depending on the software installed:
# /usr/sbin/setld -i | grep ASU | grep installed
# /usr/sbin/setld -i | grep PATHWORKS | grep installed
Deinstall the displayed subsets by entering the /usr/sbin/setld -d command
followed by the name of each subset that you want to deinstall. For
example, to deinstall the ASU Version 4.1 base, transport, and reference
page subsets, enter:
# /usr/sbin/setld -d ASUBASE410 ASUTRAN410 ASUMANPAGE410
While subsets are being deinstalled, you are prompted to save
configuration files and the user account and share databases. Save these
files and databases if you want to reuse them with the ASU ECO2 software.
2. Install the ASU ECO2 software by changing to the directory where the
ASU ECO2 software was downloaded, entering the following command, and
following the instructions on the screen:
# setld -l .
All trademarks are the property of their respective owners.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
asuv50eco2_391.README
asuv50eco2_391.CHKSUM
asuv50eco2_391.CVRLET_TXT
asuv50eco2_391.tar
asuv50eco2_391.CVRLET_TXT
|
