Anonymous_User Absent Member.
Absent Member.
1163 views

n65nss5a.exe vs n65nss6b.exe

NW 6.5 SP5 server with n65nss5a.exe patched. Saw the n65nss6b.exe patch
and wonder if it is really needed for me.

nss.nlm v3.24.01 vs v3.24.02

Any comment?

Thanks
Gina

Labels (2)
0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: n65nss5a.exe vs n65nss6b.exe

Yes -- there are new updates there which are good to have:

NSS Issues fixed after the release of N65NSS5A.EXE (new for this
release):

1. Fixed an oplock time out and locking error returns.
2. Added latch code to walk/modify the search map lists.
3. Fixed code to not allow a customer to delete all of their shared
partitions during an installation of NetWare.
4. Fixed a problem activating snapshot pools that were larger than 2
TB.
5. Fixed a display issue in Novell Remote Manager with pool and volume
sizes.
6. Changed the multi-path port to display in hex rather than in
decimal.
7. Fixed a problem with VCU where it would abend when attempting to
copy an NSS volume containing files with Chinese characters in the
file names.
8. Added an NSS set parameter to disable sending "out of disk space"
broadcast messages. (NSS /(No)OutOfSpaceAlertMessages)
9. Fixed a page fault abend in COMN.NSS caused by an initialization
pointer.
10. Fixed a recursive latching problem that caused a deadlock.
11. Fixed a CPU Hog abend if the Upgrade Current Volume Media Format
thread was started twice.
12. Fixed an oplock deadlock when transitioning from exclusive to
breaking_exclusive.
13. Fixed an abend where the compression subsystem was trying to
compress a file that shouldn't be compressed. Console messages are
now displayed for this condition, and a pool rebuild will address
any erroneous file(s) with this condition.
14. Fixed a performance issue introduced in the 5A code where the dirty
flag was being set on a buffer when computing effective access
rights.
15. Fixed a CPU Hog abend with the NSS spinlock seen at load time
specific to memory initialization and release.
16. Fixed a problem where orphaned files were being created.
17. Fixed a problem where the read ahead blocks count was set to 0
rather than the default of 2 at volume creation.
18. Fixed a problem where NSS snapshots were being deleted by the
system when they shouldn't be on a snapshot rename error condition.
19. Fixed a problem where NSSMU would create a partition one cylinder
smaller on a shareable device than a non-shareable device.
20. If a non-initialized device is flagged shareable, it will not be
persistent if the server is rebooted. NSSMU now contains a message
stating this.
21. Made NSSMU more efficient at combining free space partitions for
pool creation.
22. Fixed a -601 error when renaming a cluster enabled pool.

CIFS Issues fixed after the release of N65NSS5A.EXE (new for this
release):

1. Fixed a problem connecting to a CIFS share from an HP scanner.
2. Fixed a CPU Hog abend in CIFS seen when running security scanning
software.
3. Fixed a problem where with DFS enabled on a CIFS box, a Linux
client was unable to see the contents of the CIFS share.
4. Fixed a problem where EDIT.EXE couldn't access/open a file from a
sub-directory depth of 2 or more.
5. Fixed a problem where oplocks didn't work for CIFS if SMB signing
was enabled.
6. Fixed a problem where CIFS users would get an NMAS intruder lockout
when authenticating to a CIFS PDC (NetWare domain).
7. Fixed a problem in CIFS where a rapid reconnect could lead to
problems with memory being freed that wasn't supposed to be.
8. Fixed an abend in CIFS to handle a changing list during a code
loop.
9. Fixed a problem where CIFS logins would fail with "unknown error"
while in the domain pass-through mode.
10. Fixed a CPU Hog abend in NSS caused by CIFS not releasing a
spinlock on an error condition.
11. Fixed a problem where roaming profiles would fail over CIFS.

AFP Issues fixed after the release of N65NSS5A.EXE (new for this
release):

1. Fixed a problem where the creation and modification time stamps of
files were being updated incorrectly (or not at all).
2. Fixed a problem where OS 10.4.x clients couldn't move a file or
folder because of a character conversion issue.
3. Fixed a problem where names that begin with '#' would not copy or be
created sometimes.
4. Fixed an abend in AFPTCP.NLM where a non-NULL pointer was returned
by CLIB and wasn't handled correctly.
5. Fixed a problem with broadcast sends on OS X where the message
screen did not show the entire message.
6. Fixed a problem where all AFP clients would hang their current
session and after disconnecting, could not reconnect to the server.
7. Fixed a deadlock issue with OS 9 short name lookup code where AFP
held an NSS latch and caused the volume to become unaccessible.
8. Fixed an abend in AFPTCP.NLM when trying to copy a file (with a
mangled name) from OS 9 to the server.


--
Barry Schnur
Novell Support Connection Volunteer Sysop
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: n65nss5a.exe vs n65nss6b.exe

Is any risk in the patch no allowing NSS to load? Just wonder what kind of
downtime would it mean on the file server.

Thanks
Gina

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: n65nss5a.exe vs n65nss6b.exe

> Is any risk in the patch no allowing NSS to load? Just wonder what kind of
> downtime would it mean on the file server.


It is a rather quick deployment update -- apply the update, down the
server, bring it back up.

As to risks -- very small indeed.


--
Barry Schnur
Novell Support Connection Volunteer Sysop
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.