- The IRIX 6.5.30 release included the following for Guaranteed-Rate I/O version 2 (GRIOv2):
- An extension to the node-level bandwidth allocation, which now has two options:
- The node receives at most (ceiling) the configured bandwidth (previous behavior)
- The node receives at least (floor) the configured bandwidth (new)
- The following changes for ggd2:
- Clarification that the -m option sets per-volume minimum distributed bandwidth allocator (DBA)
- The new -s option, which sets per-node minimum DBA
- The new -u option, which specifies the DBA update interval
- The mt(1) and hinv(1M) commands were updated to display the correct drive type for STK T1000A tape drives, which are supported with APD release 2.12. Without this update, the drive type for an STK Titanium drive with an mt status command would display as "Async Personality Device" and the hinv command would show the drive type as unknown.
A secure version of Array Services that is built to make use of secure sockets layer (SSL) and secure shell (SSH) is available with IRIX 6.5.30. The "Array Services" chapter of IRIX Admin: Resource Administration has been updated with information about how to install and use Secure Array Services and describes differences between standard Array Services (arraysvcs) and Secure Array Services (sarraysvcs).
- The IRIX 6.5.30 operating system accounts for changes to Daylight Savings Time in accordance with the amendments to the Uniform Time Act. Starting in calendar year 2007, clocks will be set ahead one hour on the second Sunday of March instead of the first Sunday of April. Clocks will be set back one hour on the first Sunday in November rather than the last Sunday of October.
IRIX 6.5.30 also accounts for changes to Australian Daylight Savings time, in which the end of Daylight Savings Time is extended by one week in calendar year 2006 and returns to the last Sunday in March in 2007 and thereafter.
- The nsmount(1M) now accepts the -o argument to control options for nfs(4) protocol used to communicate to nsd(1M). See the nsmount(1M) and nsd(1M) man pages for details.
- For the IRIX 6.5.30 release, the job limits code was modified to improve the accuracy of the measurement of shared memory usage within a job. Within the job limits parameters this is called the physmem (physical memory) limit. The new change will not only count the physical memory usage accurately, but in cases where a job container has multiple processes running which share memory space, the physmem calculation will proportion the shared memory usage across the processes involved.
The IRIX 6.5.30 release included new parameters to xfs_bmapi() and xfs_bunmapi() to have them report the range spanned by modifications to the in-core extent map. The release also included XFS_BUNMAPI() and XFS_SWAP_EXTENTS() macros that call xfs_bunmapi() and xfs_swap_extents() via the ioops vector. All calls that may modify the in-core extent map for the data fork to go through the ioops vector have been changed. This allows a cache of extent map data to be kept in sync.
Share your opinion