The OpenAFS Gatekeepers announce the availability of the second release
candidate for OpenAFS version 1.4.3.
Source files and available binaries can be accessed via the web at:
http://www.openafs.org/release/openafs-1.4.3rc2.html
or via AFS at:
UNIX: /afs/grand.central.org/software/openafs/candidate/1.4.3rc2/
UNC: \\afs\grand.central.org\software\openafs\candidate\1.4.3rc2\
Linux:
------
* Build system fixes (since 1.4.3rc1)
* PAGs are now registered as a single large group when possible.
* Configure tests for the Linux kernel try harder to notice errors.
* The cred pool has been removed to avoid a deadlock.
* The s390x system call table can now be hooked.
* system call table hooking now uses improved range checking.
Solaris:
--------
* Locking is now tracked by thread in the client.
* New interfaces in Solaris 10 are used when possible.
MacOS X:
--------
* The AFS mount entry shows more synthetic free disk space.
All platforms:
--------------
* A unix domain socket for fileserver-volserver communication is
optionally available at configure time (since 1.4.3rc1).
* Lock tracking has been fixed (introduced in 1.4.3rc1).
* Server fake IP address support has been fixed.
* A server crash when AFS 3.4 jumbograms are received is fixed.
* Dead (expired) token handling in the client has been improved.
* pts chown and rename crashes have been fixed.
* asetkey builds with Heimdal.
* afsdb support in the client has been made more robust across address
change.
* A bug in 1.4.2 vos release which can leave unused files around is fixed.
* The vldb_check tool can now do repairs.
* The fileserver's handling of expired tokens has been improved.
* A crash in butc has been fixed.
Microsoft Windows:
------------------
The 1.4 series is no longer recommended for Microsoft Windows users.
Instead Microsoft Windows users are encouraged to migrate to the 1.5
series. The 1.4 series including 1.4.3-rc2 has a number of known issues
that are addressed in the current recommended release, 1.5.15:
* No support for Windows Vista or 64-bit Windows platforms
* Data Corruption on Writes. If the network connectivity to the
file server is lost while background write operations have been
queued, the writes will not succeed and that data will not be
written to the file server. This leaves a hole in the file filled
with NULs.
* Directories with large numbers of files or subdirectories will
results in very high CPU utilization when searched
* Application file lock requests are granted without obtaining a
lock from the file server. This can lead to data corruption if
two applications are writing to the same file at the same time.
All users are recommended to upgrade to 1.5.15 in order to avoid these
issues.
Please visit http://www.openafs.org/windows.html for up to date
information on the status of the OpenAFS for Windows client.
Please assist the gatekeepers by deploying this release and providing
positive or negative feedback. Bug reports should be filed to
[EMAIL PROTECTED] . Reports of success should be sent to
[email protected] .
Derrick Brashear
for the OpenAFS Gatekeepers
_______________________________________________
OpenAFS-announce mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-announce
