|
ExtremeZ-IP 4.1.1 (Released: December 2005)
|
| bet | 49/96 | | Sana | 21.03.2017 | | Hajmi | 275,22 Kb. | | #971 |
ExtremeZ-IP 4.1.1 (Released: December 2005)
ENHANCEMENTS:
* Added warning to administrators that attempt to create volumes that the service does not have full control over. A warning is now given when the volume is created, and each time the volume comes online. The user account under which the service runs (usually SYSTEM) should have full control over the entire volume, but particularly the root of the volume. Creating ExtremeZ-IP volumes without giving the service full control is strongly discouraged, as it can prevent Macintosh file IDs from being persisted across instances of the service. [#4375] [4.1.1x11]
* Added logging of ExtremeZ-IP CPU usage (as opposed to system-wide CPU usage). [#5765] [4.1.1x03]
* Added the ability to time out idle users. See the ExtremeZ-IP help file for more information. [#1674] [4.1.1x01]
BUG FIXES:
* Fixed a problem where replies to the AFPByteRangeLockExt command were not properly formed. [#4582] [4.1.1x09]
* Fixed a problem where users could experience poor performance when using client-side applications (such as Prinergy) that dealt with folders containing large numbers of files (thousands or more). [#5826] [4.1.1x07]
* Fixed a problem where volumes could not be mounted using the Classic Chooser under Mac OS 10.4. [#5773] [4.1.1x06]
* Fixed a problem where clients could fail to reconnect after server failover. [#5788] [4.1.1x05]
* Fixed a problem where ExtremeZ-IP could report stale information about a file if the file was being modified simultaneously from multiple clients. [#5640] [4.1.1x03]
* Fixed a problem where the Administrator would hang when trying to display the Log window when running on Windows 2003, 64-bit Edition. [#5706] [4.1.1x02]
* Fixed a problem where the Administrator could not show paths for open files that the SYSTEM account did not have access to. Under these conditions, the Files window would show “Path not available - SYSTEM does not have access to this file”, and the file could not be closed. [#5442] [4.1.1x01]
|
| |
