PHNE_36168 s700_800 11.11 ONC/NFS一般リリース/性能パッチ

パッチ名:   PHNE_36168

パッチ摘要: s700_800 11.11 ONC/NFS一般リリース/性能パッチ

作成日:  07/05/30

公開日:  07/06/08

ハードウェアプラットフォームおよびOSリリース:

	s700: 11.11
	s800: 11.11

現象:

	PHNE_36168:

	1.(SR:8606471489 CR:JAGag26483)
	rpc.lockdが同じロックを2つのブロッキングクライアントに付与するという不
	具合(SR:8606366266)を修正するパッチをインストールすると、rpc.lockdのパ
	フォーマンスが低下することがあります。

	2.(SR:8606474098 CR:JAGag28690)
	automountdの停止後、AutoFS LOFSマウントポイントが残ります。

	3.(SR:8606480160 CR:JAGag34291)
	NFSクライアントがラージファイル(2GB以上)をマウントしようとすると、
	"Permission denied"エラーが起きます。

	4.(SR:8606480402 CR:JAGag34511)
	rpc.yppasswddの問題。

問題点の説明:

	PHNE_36168:

	1.(SR:8606471489 CR:JAGag26483)
	PHNE_31097およびその置換パッチでは、不具合(SR:8606366266)を修正するた
	めに、ロック/ロック解除要求がループバックNFSマウントを使用するクライア
	ントから出されたかどうか調べるようにrpc.lockdのコードを修正しました。
	これは、対応するNFSサーバーのIPアドレスをシステム上に存在する各LANイン
	タフェースと比較することによって行われます。ところが、使用しているバッ
	クエンドがnis、dnsまたはldapで、かつ、高レイテンシが存在すると、
	rpc.lockdのパフォーマンスが低下することがありました。また、使用してい
	るバックエンドがファイルで、かつ、/etc/hostsファイルが大きいと、ホスト
	名が見つかるまでファイルを走査するため、余分なCPUタイムを消費すること
	がありました。システム上に多くのIPアドレスが構成されている場合もパフォ
	ーマンスに影響を与えますが、その度合いはごく僅かです。

	解決方法:
	NFSクライアントが通常のクライアント(つまり、ループバックマウントを使用
	しないクライアント)の場合は、不具合(SR:8606366266)の修正をオプションに
	しました。デフォルトではこの修正は有効です。この修正を無効にするには、
	"LOCKD_PURE_CLIENT=1"という行を/etc/rc.config.d/nfsconfに追加してから
	rpc.lockdとrpc.statdを再起動します。この修正を無効にした後再度有効にす
	るには、/etc/rc.config.d/nfsconfから"LOCKD_PURE_CLIENT=1"という行を削
	除するか、その行を"LOCKD_PURE_CLIENT=0"に変更してからrpc.lockdと
	rpc.statdを再起動します。

	2.(SR:8606474098 CR:JAGag28690)
	automountdを停止するには、nfs.clientスクリプトを使用します。ところが、
	LOFSループバックマウントでAutoFSが使用されていると、それらのマウントポ
	イントがマウントテーブル内に表示されていました。そのため、マウントポイ
	ントにアクセスしようとすると、割り込み可能なハングが起きていました。

	解決方法:
	AutoFSマウントをすべてアンマウントするようにがnfs.clientスクリプトを修
	正しました。

	3.(SR:8606480160 CR:JAGag34291)
	rpc.mountdがラージファイル(2GB以上)のマウント要求を受け付けなかったた
	め、(たとえば、"mount <server>:/bigfile/clntfile"を使って)ラージファイ
	ルをマウントすることができませんでした。

	解決方法:
	ラージファイルのマウント要求を受け付けるようにrpc.mountdを修正しました。

	4.(SR:8606480402 CR:JAGag34511)
	rpc.yppasswddのコードに欠陥がありました。

	解決方法:
	rpc.yppasswddのコードを修正しました。

-----------------------------------------------------------------------------
Patch Name: PHNE_36168

Patch Description: s700_800 11.11 ONC/NFS General Release/Performance Patch

Creation Date: 07/05/30

Post Date: 07/06/08

Hardware Platforms - OS Releases: 
	s700: 11.11
	s800: 11.11

Products: N/A

Filesets: 
	NFS.KEY-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
	NFS.NFS-64ALIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
	NFS.NFS-64SLIB,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
	NFS.NFS-CLIENT,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
	NFS.NFS-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
	NFS.NFS-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
	NFS.NFS-PRG,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
	NFS.NFS-SERVER,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
	NFS.NFS-SHLIBS,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
	NFS.NIS-CLIENT,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
	NFS.NIS-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
	NFS.NIS-SERVER,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
	NFS.NISPLUS-CORE,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
	OS-Core.CORE-ENG-A-MAN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
	NFS.NFS-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP
	NFS.NFS-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP

Automatic Reboot?: Yes

Status: General Release

Critical: 
	Yes
	PHNE_36168: HANG
	PHNE_35418: ABORT
	PHNE_34938: PANIC ABORT
	PHNE_34662: HANG ABORT CORRUPTION
	PHNE_34293: ABORT PANIC
	PHNE_33971: ABORT HANG PANIC
	PHNE_33315: HANG ABORT MEMORY_LEAK
	PHNE_32811: CORRUPTION ABORT
	PHNE_32477: ABORT HANG PANIC MEMORY_LEAK
	PHNE_31097: HANG ABORT PANIC
	PHNE_30661: ABORT HANG PANIC
	PHNE_30380: ABORT
	PHNE_30378: HANG ABORT
	PHNE_29883: ABORT PANIC
	PHNE_29303: PANIC HANG
	PHNE_28983: ABORT PANIC MEMORY_LEAK HANG
	PHNE_28137: ABORT PANIC CORRUPTION MEMORY_LEAK HANG
	PHNE_28103: HANG
	PHNE_27218: PANIC MEMORY_LEAK CORRUPTION HANG
	PHNE_26388: PANIC
	PHNE_25627: ABORT PANIC MEMORY_LEAK HANG
	PHNE_25625: ABORT
	PHNE_24910: ABORT PANIC CORRUPTION HANG
	PHNE_24035: ABORT CORRUPTION HANG
	PHNE_23502: ABORT PANIC HANG
	PHNE_22878: PANIC HANG

Category Tags: 
	defect_repair enhancement general_release critical panic
	halts_system corruption memory_leak manual_dependencies

Path Name: /hp-ux_patches/s700_800/11.X/PHNE_36168

Symptoms: 
	PHNE_36168:
	( SR:8606471489 CR:JAGag26483 )
	The fix for rpc.lockd granting the same lock to two blocking
	clients (SR:8606366266) can affect rpc.lockd performance.

	( SR:8606474098 CR:JAGag28690 )
	AutoFS LOFS mount points remain after stopping automountd.

	( SR:8606480160 CR:JAGag34291 )
	If an NFS client attempts to mount a large file (2 GB or
	larger), the mount fails with a "Permission denied" error.

	( SR:8606480402 CR:JAGag34511 )
	Problem with rpc.yppasswdd.

	PHNE_35871:
	( SR:8606440810 CR:JAGaf98610 )
	Incorrect permissions for logfiles.

	( SR:8606456591 CR:JAGag12989 )
	The acregmin, acregmax, acdirmin, and acdirmax values are
	not set properly for NFS mounts.

	( SR:8606461972 CR:JAGag17899 )
	Some daemons cannot create a logfile if the file name length
	exceeds 64 characters.

	( SR:8606466173 CR:JAGag21697 )
	Problem with chkey, newkey, and udpublickey.

	( SR:8606467933 CR:JAGag23289 )
	A non-root file owner cannot modify the file size if the
	file does not have write permission.

	( SR:8606467952 CR:JAGag23306 )
	The umount command fails with a "Device busy" error.

	( SR:8606472898 CR:JAGag27667 )
	Typos in the rpc.mountd logfile.

	PHNE_35418:
	( SR:8606266428 CR:JAGae30676 )
	The "automount -t <sec>" command does not work for mounted
	direct map mounts.

	( SR:8606335443 CR:JAGae96518 )
	NFS fails to read the last block of files that are within
	one block of the maximum supported file size.

	( SR:8606410496 CR:JAGaf70378 )
	If multiple threads and processes create and delete a lot of
	files over NFS, CPU utilization increases.

	( SR:8606437373 CR:JAGaf95562 )
	If NFS clients perform a lot of asynchronous read and write
	requests, CPU utilization increases.

	( SR:8606441116 CR:JAGaf98873 )
	Incorrect permissions for logfiles.

	( SR:8606445462 CR:JAGag02920 )
	If the NFS server is disabled and enabled (or restarted)
	through SAM, the TCP nfsd does not get killed the next time
	the NFS server is stopped.

	( SR:8606450912 CR:JAGag07918 )
	The "revnetgroup -u" command dumps core while processing an
	/etc/netgroup file with large records.

	( SR:8606460011 CR:JAGag16103 )
	The nsquery command returns the wrong group name and group
	id for group names beginning with a numeral.

	( SR:8606394173 CR:JAGaf54209 )
	When an NFS TCP client accesses a filesystem across a
	network that supports a maximum transmission unit (MTU) of
	greater than 2048 bytes, RPC limits the packet size to 2048
	bytes per segment.

	PHNE_34938:
	( SR:8606427857 CR:JAGaf87338 )
	An NFS client panics with the panic string "Data page fault"
	while performing an nfsreaddirplus operation. A sample panic
	string is:

	rtablehash+0x18
	rfind+0x18
	make_rnode+0x24
	makenfs3node+0x34
	nfs3readdirplus+0x2d0
	do_nfs3readdir+0x7c
	nfs_async_readdir+0x70
	nfs3_readdir2+0x5ec
	getdents+0xc8
	syscall+0x768
	syscallinit+0x55c

	( SR:8606429925 CR:JAGaf89391 )
	After executing "/usr/lib/nis/nisclient -r" on a system that
	had NIS+ configured, the nis_cachemgr process is left
	running on the system.

	( SR:8606438393 CR:JAGaf96478 )
	There is a performance degradation when an application
	performs sequential read, write, and lseek operations on an
	NFS mounted file if biod processes are running on the
	client.

	( SR:8606440308 CR:JAGaf98199 )
	The rpc.lockd process dumps core when a client is unable to
	reclaim a lock after a server crash.

	( SR:8606441512 CR:JAGaf99242 )
	If Enhanced AutoFS is installed on a system and a second
	instance of automountd is invoked, a core dump results and
	the original instance of automountd is unaffected.

	( SR:8606446862 CR:JAGag04211 )
	If the NFS server is stopped and restarted with the
	/sbin/init.d/nfs.server script on a multi-processor system,
	some nfsd processes exit unexpectedly.

	PHNE_34662:
	( SR:8606172586 CR:JAGad41846 )
	1. After disabling and restarting an NFS client through the
	SAM interface, there is only one nfsd process running on the
	system.
	2. Stopping an NFS client in a highly-available NFS
	environment results in the exported file systems being
	unexported.

	( SR:8606391790 CR:JAGaf51922 )
	It is difficult to accurately configure IPFilter and other
	firewalls for NFS.

	( SR:8606431961 CR:JAGaf91403 )
	The TCP nfsd daemon enters an infinite loop, and therefore
	cannot process a new TCP connection. This new connection can
	be a new NFS mount attempt or a new connection started on an
	existing NFS mount. The existing connections remain active.

	( SR:8606432689 CR:JAGaf92128 )
	An application dumps core with the error message "nfs3write:
	server wrote 32768, requested was 16384" due to a duplicate
	transaction identifier (XID).  Having duplicate XIDs could
	result in data corruption, though this has not been reported
	by customers.

	PHNE_34293:
	( SR:8606383205 CR:JAGaf43399 )
	The Local Locking feature is not available on NFS.

	( SR:8606392946 CR:JAGaf53027 )
	The system panics during I/O on an NFS mounted file. The
	panic string is "crfree: freeing free credential struct".
	The panic may also occur in crhold(). An example stack trace
	is:
	panic+0x6c
	crfree+0xc0
	kthread_shared_objects_update+0x2c
	syscall+0x810
	syscallinit+0x55c

	( SR:8606394934 CR:JAGaf54948 )
	There are "xdrrec_create: out of memory" errors in the
	syslog.log file and rpcbind dumps core.

	( SR:8606421959 CR:JAGaf81784 )
	The mount command fails with a "Permission denied" error on
	an NFS client after re-exporting a directory on an NFS
	server.

	( SR:8606425181 CR:JAGaf84701 )
	The /etc/xtab file is cleared when an "exportfs -u" command
	is executed if the /var file system is full.

	PHNE_33971:
	( SR:8606379232 CR:JAGaf39481 )
	The rstat(3N) man page incorrectly defines the size of
	stats.cp_time, statswtch.cp_time, and statstime.cp_time.

	( SR:8606390486 CR:JAGaf50632 )
	An NFS client panics when control messages from the TCP
	transport are received in the wrong sequence. An example
	panic stack trace is:
	panic+0x6c
	report_trap_or_int_and_panic+0x94
	trap+0xef4
	nokgdb+0x8
	xdrmblk_init+0x2c
	clnt_cots_kcallit+0x848
	rfscall+0x27c
	rfs3call+0x78
	nfs3write+0x234
	nfs3_do_bio+0x1f0
	nfs_strategy+0x724
	nfs3_strategy+0x1c
	bwrite+0xe8
	bawrite+0x1c
	rw3vp+0x980
	nfs3_write+0x184
	nfs3_rdwr+0x50
	vno_rw+0x80
	write+0x108
	syscall+0x62c

	( SR:8606394075 CR:JAGaf54115 )
	This product update is a member of a set needed to enable
	the optional HP-UX Enhanced Key Components feature. Upon
	installation, the HP-UX Enhanced Key Components bundle
	(ENHKEY) will install the full set of product updates
	(including this one) to enable the HP-UX Enhanced Key
	Components feature. If the HP-UX Enhanced Key Components
	product is not installed, this product update will have no
	impact on your system.

	( SR:8606401733 CR:JAGaf61670 )
	The rpc.lockd process dumps core on a server with more than
	2048 client connections. Similarly, rpc.statd may dump core
	during file lock recovery when there are more than 2048
	host entries in /var/statmon/sm.

	( SR:8606410663 CR:JAGaf70545 )
	An NFS client thread hangs while trying to bind to a
	reserved port.

	( SR:8606412876 CR:JAGaf72738 )
	An NFS client panics with the panic string "Data page
	fault". An example panic stack trace is:
	panic+0x6c
	report_trap_or_int_and_panic+0x94
	trap+0xeec
	thandler+0xd20
	spinlock+0x14
	spin_mutex_enter+0x14
	mir_wput_other+0x14c
	mir_wput+0x3c
	rmm_wput+0x1c
	putnext+0xcc
	str_async_ioctl+0x224
	hpstreams_ioctl_int+0x11c
	streams_ioctl+0x34
	t_kbind+0xec
	tcp_bindresvport+0x114
	connmgr_get+0x318
	clnt_cots_kcallit+0x144
	rfscall+0x268
	rfs3call+0x78
	nfs3write+0x234
	nfs3_do_bio+0x1f0
	async_daemon+0x4ec
	coerce_scall_args+0xe0
	syscall+0x204
	syscallinit+0x55c

	( SR:8606414935 CR:JAGaf74793 )
	The yppasswd command changes the permissions of the
	/etc/passwd file.

	( SR:8606412878 CR:JAGaf72740 )
	A thread hangs while attempting to close a connection.

	PHNE_33498:
	( SR:8606167807 CR:JAGad37090 )
	The ypinit(1m) man page contains references to obsolete vhe
	functions.

	( SR:8606406594 CR:JAGaf66500 )
	Attempts to access a file system mounted with a soft NFS
	mount fail with the error message "RPC: Unable to receive".

	( SR:8606413268 CR:JAGaf73129 )
	CacheFS unmounts are slow.

	( SR:8606413731 CR:JAGaf73591 )
	The file handle cache is not purged when an error is
	returned from rfs3call().

	PHNE_33315:
	( SR:8606385895 CR:JAGaf46049 )
	NFS write performance slows when writing files larger than
	2 GB.

	( SR:8606394445 CR:JAGaf54468 )
	When an AutoFS file system is unmounted, and the IP Address
	of the server that was AutoFS mounted is changed, AutoFS
	uses the old IP address if the file system is remounted.

	( SR:8606399902 CR:JAGaf59858 )
	RPC applications consume a lot of CPU resources.

	( SR:8606400085 CR:JAGaf60041 )
	The man page describing the rpc_broadcast_exp function has
	one of the parameters listed out of order.

	( SR:8606401738 CR:JAGaf61675 )
	The rpc.lockd and rpc.statd processes hang if logging is
	enabled and disabled many times.

	( SR:8606402519 CR:JAGaf62454 )
	The rpc.lockd and rpc.statd processes dump core when trying
	to log an I/O error with logging disabled.

	( SR:8606405252 CR:JAGaf65172 )
	The rpc.rquotad process increases in size and may dump core.

	PHNE_32811:
	( SR:8606345889 CR:JAGaf06735 )
	The server's rpc.lockd grants reclaim requests to clients
	after the grace period expires.

	( SR:8606377207 CR:JAGaf37485 )
	rpc.lockd terminates when it receives a SIGALRM signal. If
	rpc.lockd logging is enabled, the message "signal handler:
	signal = 14" appears in the /var/adm/rpc.lockd.log file.

	( SR:8606389345 CR:JAGaf49493 )
	The mount_nfs(1M) man page states that the default value of
	the 'retrans' option is 5. However, if an NFS client sends a
	request with no reply from the server, only 4
	retransmissions are attempted before giving up in the case
	of a soft mount. The documentation of the default retrans
	value is also inconsistent.

	( SR:8606393839 CR:JAGaf53894 )
	The rename() system call returns a "Not Owner" error when
	renaming a directory in a cachefs-mounted file system to a
	name which is an existing directory.

	( SR:8606394223 CR:JAGaf54255 )
	The "ypwhich -m" command returns the error message:
	"ypwhich: can't get the list of maps: RPC: Unable to
	receive; buffer not large enough".

	PHNE_32477:
	( SR:8606386532 CR:JAGaf46686 )
	An application using clnt_tli_create() dumps core when
	called with large send/receive buffers for connection-
	oriented transports.

	( SR:8606387765 CR:JAGaf47918 )
	If a write() system call to an NFS file is interrupted by a
	signal (e.g. by sending SIGINT to the process) before the
	data is written to the server, the call succeeds. This
	occurs only on files configured to do synchronous I/O
	(opened with the O_DSYNC flag set).

	( SR:8606387807 CR:JAGaf47960 )
	An NFS server panics with the panic string "kalloc: out of
	kernel virtual space". The panic stack trace is:
	panic+0x6c
	kalloc_4K+0x270
	kalloc_from_superpage+0x488
	kalloc+0x14
	alloc_mem+0x44
	get_kmem+0x8c
	kmem_arena_xlarge_alloc+0x74
	kmalloc+0x1e4
	nfs_kmem_alloc+0x18
	rfs3_read+0x310
	rfsexp_dispatch+0x5f0
	svc_getreq+0x1ec
	svc_run+0x6e8
	nfsexp_svc+0x1f8
	nfs_stub_svc+0xa4
	coerce_scall_args+0xe0
	syscall+0x204
	syscallinit+0x55c

	( SR:8606389142 CR:JAGaf49290 )
	rpc.lockd dumps core with SIGBUS.

	( SR:8606389255 CR:JAGaf49403 )
	A multi-threaded process hangs and cannot be killed. The
	system needs to be rebooted to clear the situation.

	( SR:8606348790 CR:JAGaf09611 )
	Difficulties in correctly configuring automounts with direct
	maps using the automount(1m) man page.

	( SR:8606381800 CR:JAGaf42012 )
	There is a fix for an AutoFS 1.2 defect which is not needed
	if the Enhanced AutoFS product is installed.

	( SR:8606393701 CR:JAGaf53756 )
	AutoFS mounts and unmounts fail with the "clnt_dg_create:
	out of memory" message in the syslog.log file.

	PHNE_31929:
	( SR:8606373075 CR:JAGaf33480 )
	The mlock call is succeeding after truncation of a memory
	mapped file over NFS.

	( SR:8606375121 CR:JAGaf35426 )
	The on command fails with the error message "Unable to
	mount" when executed from an AutoFS mount point.

	( SR:8606379022 CR:JAGaf39271 )
	Provide the tunable support to adjust the delay time
	variable in response to an NFS3ERR_JUKEBOX error from an NFS
	server.

	PHNE_31097:
	( SR:8606345966 CR:JAGaf06811 )
	The message "/net -hosts -nosuid,soft" appears in the
	/etc/rc.log file and on stderr.

	( SR:8606347603 CR:JAGaf08425 )
	Enhancement: RPC applications using UDP transport can now
	identify the end-point pair.

	( SR:8606354067 CR:JAGaf14861 )
	Previously running UDP nfsd's are unregistered after nfsd's
	are restarted.

	( SR:8606359725 CR:JAGaf20421 )
	The automountd process dumps core.

	( SR:8606360695 CR:JAGaf21402 )
	An NFS TCP client hangs even though its TCP connection to
	the server appears to be good, or panics reporting "kalloc:
	out of kernel virtual space" as the panic string.

	( SR:8606364296 CR:JAGaf24937 )
	The function netdir_getbyname() returns the message
	"successful completion" when it should return the error
	"service name not found".

	( SR:8606364383 CR:JAGaf25022 )
	If an NFS server is not available, processes accessing NFS
	filesystems hang and cannot be killed.

	( SR:8606365866 CR:JAGaf26496 )
	An NFS client crashes in the read path when an NFS server
	returns more data than requested.

	( SR:8606369177 CR:JAGaf29721 )
	rpcbind(1M) core dumps with SIGBUS or SIGSEGV.

	( SR:8606366266 CR:JAGaf26870 )
	The same lock is granted to two blocking clients, when one
	of the locks is obtained by a loopback mount (LOFS).

	( SR:8606379191 CR:JAGaf39440 )
	Support for largefiles with rpc.rquotad.

	( SR:8606379708 CR:JAGaf39957 )
	When a "tcp_discon" is issued via ndd against the local TCP
	end-point for NFS/TCP client requests to a specific NFS
	server, the NFS/TCP client will attempt to re-connect to the
	NFS server using the same local port.

	PHNE_30661:
	( SR:8606354850 CR:JAGaf15606 )
	NIS slave server configuration fails with the error message:
	"ypxfr:  can't dbm close temp map".

	( SR:8606355618 CR:JAGaf16332 )
	A client's rpc.lockd dumps core after a server failover.

	( SR:8606357066 CR:JAGaf17766 )
	The exportfs command fails with the error message "exportfs
	error: /etc/xtab in use. Please try again." when /etc/xtab
	is not in use.

	( SR:8606357361 CR:JAGaf18061 )
	The CacheFS mount command dumps core.

	( SR:8606358606 CR:JAGaf19305 )
	A connectionless NFS server hangs with the following
	messages in syslog.log:
	xdr_bytes: bad size FAILED
	NOTICE: nfs_server: bad sendreply; proc=6

	( SR:8606363276 CR:JAGaf23938 )
	There is no documentation for the nfs_portmon variable.

	( SR:8606329363 CR:JAGae90487 )
	The system panics with the panic string "Data page fault".
	The panic stack trace is:
	bwrite+0xd4
	rw3vp+0x8d8
	nfs3_write+0x184
	nfs3_rdwr+0x50
	vno_rw+0x80
	write+0x108
	syscall+0x750
	syscallinit+0x554

	PHNE_30380:
	( SR:8606382150 CR:JAGaf42361 )
	An RPC application using TCP dumps core with SIGBUS when
	started with inetd.

	PHNE_30378:
	( SR:8606319551 CR:JAGae82039 )
	The rpc_soc man page is missing a description about using
	sockets in an application.

	( SR:8606339927 CR:JAGaf00848 )
	The automount daemon hangs during startup and the
	/etc/mnttab file contains inconsistent entries.

	( SR:8606344107 CR:JAGaf04959 )
	A locking application hangs and the rpc.lockd daemon aborts.
	If logging is enabled for rpc.lockd, the message "ABORT in
	add_reclock" is logged in the /var/adm/rpc.lockd.log file.

	( SR:8606345310 CR:JAGaf06160 )
	When there are multiple subdomains configured, the
	rpc.nispasswdd daemon may fail to start and the nisstat
	command may return with the following error message:
	"nisstat: Error talking to host <NIS+ master>: Error in RPC
	subsystem".

	( SR:8606346094 CR:JAGaf06921 )
	The setoncenv command accepts NFS_TCP as a valid
	configurable environment variable.

	( SR:8606346132 CR:JAGaf06959 )
	Incorrect NFS version information is being passed to the
	kernel profiling code.

	( SR:8606347226 CR:JAGaf08050 )
	Commands operating on an NFS file system mounted as a soft
	mount over UDP transport protocol fail with the error
	message: "RPC: Unable to receive".

	( SR:8606347264 CR:JAGaf08087 )
	The error message "No such file or directory" results from
	the /usr/bin/pwd command with AutoFS direct maps.

	( SR:8606351701 CR:JAGaf12506 )
	The mount_nfs man page states that quota checking on NFS
	file systems is enforced by default.

	( SR:8606355273 CR:JAGaf16027 )
	Netselect and Netdir output some error messages incorrectly.

	( SR:8606356288 CR:JAGaf16994 )
	A hang occurs during an NFS write operation.

	PHNE_30086:
	( SR:8606324736 CR:JAGae87042 )
	An NFS client operating on filesystems mounted over TCP from
	an NFS server is unable to contact the server and fails with
	repeated messages such as "NFS server <xxx> not responding
	still trying" or "NFS getattr failed for server <xxx> : RPC:
	(unknown error code)". The client's TCP connection state
	shows that the connection is in the CLOSE_WAIT state. The
	connection persists in this state until you reboot the
	client or reset the connection with ndd.

	( SR:8606336931 CR:JAGae97978 )
	An NFS-TCP client running processes over an NFS-TCP hard
	mount fails to reconnect with the NFS server after a network
	outage has been restored. The client fails with repeated
	messages such as "NFS server <xxx> not responding still
	trying" or "NFS getattr failed for server <xxx> : RPC:
	(unknown error code)". The client's TCP connection state
	shows that an established connection to the server exists.
	This failure persists for about six minutes until the
	server times out and closes the existing TCP connection.

	PHNE_29883:
	( SR:8606312940 CR:JAGae75747 )
	An NFS PV3 client panics while reading the path name of a
	long symbolic link.

	( SR:8606320583 CR:JAGae83065 )
	The system panics while AutoFS is unmounting the file
	systems that are being managed by AutoFS.

	( SR:8606330100 CR:JAGae91223 )
	The error message "rpcbind cannot accept connection: bad
	call sequence number (current state 4)" appears in the
	syslog.log file.

	( SR:8606333242 CR:JAGae94337 )
	There is a problem with nested AutoFS maps.

	( SR:8606334605 CR:JAGae95685 )
	A core dump occurs when an application uses 64-bit
	xdr_char() and xdr_u_char() routines.

	( SR:8606336578 CR:JAGae97630 )
	It is not clear how to choose the number of nfsd's to be run
	when configuring an HP-UX NFS server.

	PHNE_29783:
	( SR:8606347801 CR:JAGaf08623 )
	Problem with rpc.ypupdated.

	PHNE_29303:
	( SR:8606286517 CR:JAGae50456 )
	AutoFS mount points do not get mounted under heavy load.

	This product update is a member of a set needed to enable
	the optional HP-UX Enhanced AutoFS feature. Upon
	installation, the HP-UX Enhanced AutoFS bundle (Enhanced
	AutoFS) will install the full set of product updates
	(including this one) to enable the HP-UX Enhanced AutoFS
	feature. If the HP-UX Enhanced AutoFS product is not
	installed, this product update will have no impact on your
	system.

	( SR:8606302457 CR:JAGae65816 )
	Applications that issue lock requests from an HP-UX client
	to an EMC Server sometimes hang.

	( SR:8606304146 CR:JAGae67490 )
	In an NIS+ trusted environment, if a non-root user executes
	a password change on an NIS+ client, logins to other hosts
	will fail because the pwchanger field of the trusted table
	is not updated.

	( SR:8606306059 CR:JAGae69107 )
	A non-root NIS+ user will hang when issuing a rexec command
	to another NIS+ client.

	( SR:8606306319 CR:JAGae69367 )
	The NIS+ client authentication fails when the /var
	filesystem is full.

	( SR:8606312085 CR:JAGae74904 )
	When an NFS client tries to create a symbolic link to a file
	or directory with a large path name, the NFS server panics
	with a data page fault.

	( SR:8606313428 CR:JAGae76226 )
	Unexpected RPC error messages such as "Program not
	registered", "Miscellaneous tli error", and "Program
	unavailable" result from the showmount and other commands.

	( SR:8606322456 CR:JAGae84924 )
	The NFS mount command mounts with NFS V2 instead of failing
	when NFS V3 is requested and is not available on the server.

	( SR:8606335982 CR:JAGae97035 )
	This product update is a member of a set needed to enable
	the optional HP-UX Enhanced AutoFS feature. Upon
	installation, the HP-UX Enhanced AutoFS bundle (Enhanced
	AutoFS) will install the full set of product updates
	(including this one) to enable the HP-UX Enhanced AutoFS
	feature. If the HP-UX Enhanced AutoFS product is not
	installed, this product update will have no impact on your
	system.

	( SR:8606332784 CR:JAGae93899 )
	The system panics with the panic string "Data page fault".
	The panic stack trace is:
	rtablehash+0x18
	rfind+0x18
	make_rnode+0x24
	makenfs3node+0x34
	nfs3readdirplus+0x280
	do_nfs3readdir+0x68
	nfs3_readdir2+0xc0
	getdents+0x1b0
	syscall+0x28c
	syscallinit+0x54c

	PHNE_29211:
	( SR:8606317529 CR:JAGae80090 )
	The performance level of connection-oriented RPC transports
	is being reduced by network delays.

	( SR:8606320560 CR:JAGae83042 )
	The rpc.mountd code returns an incorrect error message.

	( SR:8606317535 CR:JAGae80096 )
	The performance level of connection-oriented RPC servers is
	being reduced by network delays.

	( SR:8606337943 CR:JAGae98946 )
	NIS+ commands and applications fail with the error message
	"Error in RPC subsystem".

	PHNE_28983:
	( SR:8606220736 CR:JAGad89872 )
	When a new NIS+ user changes the password to log in for the
	first time, the login fails with the error message "Password
	information update failed".

	( SR:8606278781 CR:JAGae42837 )
	AutoFS mounted directories do not get unmounted, even if
	not accessed during the timeout period. These mounts are
	unmounted only after a reboot.

	( SR:8606294191 CR:JAGae57931 )
	Directories that are mounted with AutoFS are not getting
	unmounted by AutoFS.

	( SR:8606294387 CR:JAGae58084 )
	Under heavy load, AutoFS-mounted file systems never get
	unmounted.

	( SR:8606294761 CR:JAGae58456 )
	A large /etc/exports file causes the system to boot very
	slowly.

	( SR:8606295723 CR:JAGae59388 )
	Unable to mount an NFS file system from a PC.

	( SR:8606296110 CR:JAGae59732 )
	The defaults listed in the /etc/nsswitch.hp_defaults file do
	not match the nsswitch.conf man page.

	( SR:8606296698 CR:JAGae60267 )
	An NFS Server hangs and the error message "NFS Server not
	responding" is seen when accessing NFS loopback mounts.

	( SR:8606296789 CR:JAGae60355 )
	A 64-bit system panics when executing an "ls" command on an
	NFS PV3 mounted file system.

	( SR:8606297163 CR:JAGae60682 )
	When open() is called with O_EXCL via NFS, the date,
	timestamp, and privileges of the file are not updated
	properly.

	( SR:8606297688 CR:JAGae61190 )
	AutoFS directories are not getting remounted after a manual
	unmount.

	( SR:8606297816 CR:JAGae61318 )
	The data segment of the rpc.lockd process grows larger with
	time, and response time increases. The process may
	ultimately crash because of a lack of memory.

	( SR:8606300458 CR:JAGae63927 )
	Poor performance while remounting an AutoFS hierarchical
	mount.

	( SR:8606301831 CR:JAGae65194 )
	The /etc/services file is cleared when the machine is booted
	with /usr as a dead mount point.

	( SR:8606302828 CR:JAGae66186 )
	Stale AutoFS directories remain when a mount attempt to a
	non-existent file system fails.

	( SR:8606303150 CR:JAGae66506 )
	An NFS Server hangs and the error message "NFS Server not
	responding" is seen when accessing NFS loopback mounts.

	( SR:8606308183 CR:JAGae71218 )
	The nfsd.1m and setoncenv.1m man pages contain references to
	NFS_TCP which is not relevant in this HP-UX release.

	( SR:8606308342 CR:JAGae71377 )
	A non-root user is not able to unmount an NFS mounted
	directory.

	( SR:8606309647 CR:JAGae72522 )
	NIS+ man pages do not mention that the HP-UX 11.23 release
	will be the last release on which NIS+ is supported.

	PHNE_28930:
	( SR:8606306693 CR:JAGae69727 )
	Some of the XDR routines do not function properly.

	PHNE_28568:
	( SR:8606308270 CR:JAGae71305 )
	The "nfsstat -m" command does not display NFS PV3
	information.

	PHNE_28137:
	( SR:8606284507 CR:JAGae48453 )
	NFS client calls close() and write() timeout on hard NFS
	mounts.

	( SR:8606279504 CR:JAGae43557 )
	The result of executing a binary linked with a shared
	library from a CacheFS mount point differs from the result
	of executing the same binary from a native file system.

	( SR:8606274703 CR:JAGae38780 )
	NFS pathconf(_PC_CHOWN_RESTRICTED) and fpathconf
	(_PC_CHOWN_RESTRICTED) return 0 when chown is not restricted
	instead of -1, the POSIX compliant result.

	( SR:8606272309 CR:JAGae36449 )
	Using loopback NFS mounts, the server may hang due to a
	deadlock condition.

	( SR:8606284964 CR:JAGae48906 )
	Data corruption while using XDR function xdrmblk_getlong()
	with a 64-bit kernel.

	( SR:8606275551 CR:JAGae39627 )
	If an NFS server listed in the /etc/mnttab file is down or
	there are network problems, the "nfsstat -m" call hangs.

	( SR:8606284885 CR:JAGae48827 )
	The number of file locks (nflocks) grows over a long period
	of time, eventually causing NFS to lock up. The only
	workaround is to restart NFS.

	( SR:8606274519 CR:JAGae38596 )
	After unmounting all the AutoFS mount points through the
	script "nfs.client stop", the system panics if it tries to
	access an unmounted directory.

	( SR:8606256016 CR:JAGae20331 )
	Threads accessing an NFS directory hang for a long time with
	"bindresvport: loop-twice port assigned ..." messages other
	than port 512 logged in syslog.log.

	( SR:8606271824 CR:JAGae36003 )
	The system reports "vmunix: bindresvport: loop_twice port
	assigned 512" messages.

	( SR:8606269865 CR:JAGae34105 )
	When Intergraph's DiskShare NFS server returns zero bytes
	for the preferred and/or maximum transfer size of the
	READ/WRITE operation, the HP-UX NFS client panics.

	( SR:8606267227 CR:JAGae31470 )
	The system panics after a read/write NFS exported file
	system is unmounted and then re-mounted as read-only without
	re-exporting the file system.

	( SR:8606276756 CR:JAGae40831 )
	An NFS server sometimes panics if pathconf() is called with
	a file in an NFS mounted directory.

	( SR:8606267508 CR:JAGae31750 )
	A process is able to write into a read-only automounted file
	system.

	( SR:8606267320 CR:JAGae31562 )
	Poor NFS PV3 performance on a 64-bit client system.

	( SR:8606287136 CR:JAGae51075 )
	The contents of a directory mounted with AutoFS become
	unavailable, and the directory cannot be used, mounted, or
	unmounted.

	( SR:8606278982 CR:JAGae43038 )
	An AutoFS mounted file system using the "-hosts" map can
	take a long time to mount when the environment contains dead
	NFS servers.

	( SR:8606288334 CR:JAGae52265 )
	The NFS mount command does not update the /etc/mnttab file
	with protocol information when the UDP protocol is used.

	( SR:8606282498 CR:JAGae46451 )
	Memory/file-descriptor leak in RPC multi-threaded server
	programs, if the client tries to connect using a version
	number that is unsupported by the server. The memory leak
	may result in the server dumping core and terminating. This
	can also cause the server to quickly run out of file
	descriptors.

	( SR:8606288821 CR:JAGae52752 )
	Calls to netdir_getbyname() from a multithreaded process may
	hang or terminate with SIGSEGV or SIGBUS.

	( SR:8606282662 CR:JAGae46615 )
	The message "NFS server xxxx not responding still trying" is
	seen on a client while attempting to establish an NFS TCP
	connection, and the connection is in the LISTEN state.

	( SR:8606291642 CR:JAGae55409 )
	Memory based XDR stream implementations do not function
	properly.

	PHNE_28103:
	( SR:8606276016 CR:JAGae40093 )
	The rpc.yppasswdd process dies.

	( SR:8606274502 CR:JAGae38579 )
	RPC does not function properly.

	( SR:8606288394 CR:JAGae52325 )
	Incorrect permissions for the log file.

	( SR:8606281883 CR:JAGae45826 )
	The netdir_getbyname() routine using NIS can hang under
	certain circumstances.

	( SR:8606276334 CR:JAGae40412 )
	Problem with ypxfrd.

	( SR:8606286563 CR:JAGae50502 )
	Incorrect configuration for AutoFS.

	( SR:8606274555 CR:JAGae38632 )
	Showmount dumps the core with SIGSEGV.

	PHNE_27218:
	( SR:8606249576 CR:JAGae15966 )
	A client's attempt to acquire a lock may result in a delay
	or a hang.

	( SR:8606249559 CR:JAGae15949 )
	The '-p' option for rpc.mountd described in the man page
	does not function as described.

	( SR:8606180770 CR:JAGad49991 )
	Blocked lock requests on a client system hang.

	( SR:8606233931 CR:JAGae03154 )
	After the AutoFS client unmount timer expires, if the
	unmount of the parent file system fails and the remount of
	hierarchical mount points fails, then zero entries are found
	while accessing the hierarchical mount points under the
	parent file system. Once this condition occurs the failed
	hierarchical mounts will not retry mounting.

	( SR:8606234034 CR:JAGae03255 )
	The nfsconfcol script is not removing the target data files
	before writing to them.

	( SR:8606256845 CR:JAGae21158 )
	The /var/adm/automount.log file is shipped incorrectly.

	( SR:8606256846 CR:JAGae21159 )
	The /var/spool/rexd directory is shipped incorrectly.

	( SR:8606259831 CR:JAGae24149 )
	A client system hangs when trying to lock a file.

	( SR:8606255006 CR:JAGae19335 )
	Exported directories cannot be mounted.

	( SR:8606277106 CR:JAGae41178 )
	Under heavy load, file systems mounted with AutoFS never get
	unmounted, even after the system load has decreased.

	( SR:8606257688 CR:JAGae21991 )
	Client hangs when trying to lock a remote file.

	( SR:8606260873 CR:JAGae25195 )
	Large files become corrupt when writing across NFS mounts.

	( SR:8606242021 CR:JAGae09276 )
	1. Many "dup_remove_pending: WARNING: duplicate request
	cache size (210) > XID_CACHE_SIZE (200), continuing"
	messages in syslog.log and automount.log.
	2. Many "Rmdir: err=247, mnt='<mount-point-dir>'" messages
	in automount.log.

	( SR:8606226778 CR:JAGad95840 )
	If an AutoFS mounted filesystem using a simple direct map is
	manually unmounted, a panic may result if that filesystem is
	referenced simultaneously (e.g. by two or more ls commands).
	The panic string is:
	  "Data page fault".
	The panic stack trace is:
	  panic+0x14
	  report_trap_or_int_and_panic+0x80
	  trap+0xdb8
	  nokgdb+0x8
	  nfs3_root+0x68
	  hpauto_trigger_mount+0x20c
	  auto_access+0x30
	  chdirec_seg+0x5c
	  chdirec+0x14
	  chdir+0x34
	  syscall+0x29c
	  $syscallrtn+0x0

	( SR:8606248269 CR:JAGae14669 )
	If a client's /var/statmon/sm directory contents are
	destroyed, future lock requests hang.

	( SR:8606245329 CR:JAGae11799 )
	A system hangs or panics when issuing a "ln" command.

	( SR:8606264317 CR:JAGae28647 )
	This product update is a member of a set needed to enable
	the optional HP-UX Device IDs feature. Upon installation,
	the HP-UX Device IDs bundle (DevIDs11i) will install the
	full set of product updates (including this one) necessary
	to enable the Device IDs feature.

	If the HP-UX Device IDs product (DeviceIDs11i) is not
	installed, this product update to HP-UX will have no
	impact on your system.

	( SR:8606265228 CR:JAGae29556 )
	Spinlock deadlock panic due to a lock being held too long.

	( SR:8606259713 CR:JAGae24031 )
	AutoFS problem.

	( SR:8606234968 CR:JAGae04152 )
	When automountd gets a stale NFS file handle error for a
	direct mount point, it removes the corresponding AutoFS
	direct map entry for that mount point from the file
	/etc/mnttab. Automountd needs to be stopped and restarted to
	get back the direct AutoFS mount point.

	( SR:8606235172 CR:JAGae04352 )
	The NFS mount operation returns an incorrect error message
	when all ports are in use. The error message is:
	nfs mount: bindresvport: t_errno = 8
	nfs mount: get_fh: Couldn't bind to a reserved port.
	return = -1

	( SR:8606245876 CR:JAGae12335 )
	System panics when the mount of an exported file system that
	contains an extraneous or missing "/" fails. The panic
	string is: rm_autonode: No entry for <address>

	( SR:8606257219 CR:JAGae21525 )
	Accessing a TCP AutoFS mount point causes the system to
	hang.

	( SR:8606244127 CR:JAGae10618 )
	If rpc.lockd and rpc.statd are restarted and the
	/var/statmon/sm directory is destroyed on the server, the
	client's rpc.lockd takes 35 minutes to recover.

	( SR:8606264087 CR:JAGae28412 )
	When a 64-bit RPC application uses UNIX authentication
	flavor, the RPC server does not properly decode the client
	credentials.

	( SR:8606271227 CR:JAGae35462 )
	The "ls" command will hang when users try to access a dead
	server after some systems with mounted directories are shut
	down.

	( SR:8606147221 CR:JAGad16564 )
	Problem with privileged groups.

	( SR:8606248870 CR:JAGae15267 )
	The "cd" command to an AutoFS direct offset mount directory
	hangs, and automountd cannot be killed by pressing CTRL-C to
	stop the "cd" command.

	( SR:8606232532 CR:JAGae01767 )
	AutoFS mounted directories are empty.

	( SR:8606254087 CR:JAGae18419 )
	The rpcbind process increases in size and stops responding
	to client requests. This requires rpcbind needs to be killed
	and restarted.

	PHNE_26388:
	( SR:8606248624 CR:JAGae15022 )
	AutoFS causes a system panic with the panic string
	"rm_autonode: No entry for <<address>>".

	PHNE_25627:
	( SR:8606230660 CR:JAGad99710 )
	A server stub generated by rpcgen logs error messages to
	/dev/console.

	( SR:8606188628 CR:JAGad57842 )
	The man page for nsswitch.conf does not reflect ldap as an
	additional database source for nss backends.

	( SR:8606228306 CR:JAGad97363 )
	A file has an unusual timestamp when created with open(2)
	using O_EXCL flag.

	( SR:8606224657 CR:JAGad93745 )
	File lock recovery fails when the server reboots if the
	server has multiple network interfaces and the client has
	mounted the file system with an interface name different
	than the server's hostname.

	( SR:8606218377 CR:JAGad87526 )
	A multi-threaded server leaks file descriptors under heavy
	load if clients are running on the same box.

	( SR:8606186978 CR:JAGad56188 )
	Partially cached large binaries are removed at unmount time
	by CacheFS.

	( SR:8606225370 CR:JAGad94457 )
	The system panics due to a data page fault on the NFS server
	when processing a TCP client mount request.

	( SR:8606230685 CR:JAGad99735 )
	Excessive warning messages being logged:
	WARNING: filegrp_destroy_metadata:
	fileno 61 slot 7-5 fgp 41f2c1d0 not allocated.

	( SR:8606219527 CR:JAGad88667 )
	On a client system, the old automounter is trying to access
	a non-existent entry in the NIS map and that is generating
	an excessive number of packets over the network which causes
	slow response time.

	( SR:8606226735 CR:JAGad95797 )
	The inetd is unable to resolve services.

	( SR:8606237277 CR:JAGae06322 )
	NFS PV2 client does not properly show the quota exceeded
	error.

	( SR:8606221217 CR:JAGad90351 )
	The "ll" command hangs in the case of an automounted file
	system if the server is down.

	( SR:8606221909 CR:JAGad91027 )
	System panic occurs while autofs is unmounting the idle
	autofs mount points. The panic string is "spinlocks held
	with M_WAITOK".

	( SR:8606221102 CR:JAGad90236 )
	Reactivating a user account that has been disabled on a
	trusted NIS+ clients fails.

	( SR:8606172908 CR:JAGad42168 )
	When an HANFS package is manually failed over back-and-forth
	between two different cluster server nodes within a period
	of time shorter than five minutes, then on any NFS client
	which have the HANFS package filesystem mounted over TCP,
	NFS access to that filesystem can appear hung for a
	relatively long period of time - usually more than four
	minutes, with no apparent response from the server. Also
	the NFS client issues the error message "NFS server XXXXXXX
	not responding still trying", about every 30 seconds.

	( SR:8606226170 CR:JAGad95241 )
	A "umount" of an NFS mounted file system using CacheFS
	causes an RPC error.

	( SR:8606229377 CR:JAGad98430 )
	AutoFS mounted file systems never get unmounted.

	( SR:8606204999 CR:JAGad74175 )
	The ttsyncd process loops, occupying much of the CPU usage
	and causing the system to slow down.

	( SR:8606225120 CR:JAGad94209 )
	rpc.rusersd core dumps if more than 180 users have logged
	in.

	PHNE_25625:
	( SR:8606245747 CR:JAGae12206 )
	rpc.lockd core dumps with a SIGBUS error during heavy NFS
	file locking.

	PHNE_24910:
	( SR:8606184366 CR:JAGad53575 )
	Instruction page fault where the instruction address being
	accessed is 0.

	( SR:8606201620 CR:JAGad70794 )
	On SUN's NIS clients, it is possible to specify a list of
	available NIS servers for a given domain. HP's NIS clients
	do not provide this functionality.

	( SR:8606147778 CR:JAGad17120 )
	RPC client call rejection from an RPC server because of
	unsupported RPC protocol version can result in an error
	incorrectly indicating a non-response from the RPC server.
	For example, an NFS operation results in "NFS server
	<server name> not responding still trying" error.

	( SR:8606216548 CR:JAGad85717 )
	A password expires unexpectedly in an NIS+ environment.

	( SR:8606205779 CR:JAGad74954 )
	The automountd (AUTOFS) hangs/cores while attempting to
	automount exported FS and reports 100% CPU utilization.

	( SR:8606205013 CR:JAGad74189 )
	The mount option 'grpid' does not return the correct 'gid'
	value on NFS PV2 and PV3.

	( SR:8606212242 CR:JAGad81430 )
	When a customer specifies a user name with leading blank
	characters as an argument to nispasswd and passwd(1),
	nispasswd modifies the username to include those leading
	blanks in the NIS+ passwd table and trusted table.

	( SR:8606187776 CR:JAGad56985 )
	An NFS/TCP client panics while under heavy NFS load. Problem
	has been seen most often while client performed 100 NFS/TCP
	mounts in succession.

	( SR:8606220062 CR:JAGad89203 )
	The ovcmsgrd process aborts and produces a core file when
	the Network Node Manager managed processes are started with
	"ovstart opc".

	( SR:8606219558 CR:JAGad88698 )
	During the login process, NIS+/trusted clients force NIS+
	users to modify their password when their password is
	expired but fail to un-expire the password when their
	password is changed. Users will always be forced to modify
	their password as soon as it has expired.

	( SR:8606213087 CR:JAGad82274 )
	NFS PV3 allows the file to be opened with mandatory lock
	(02760) permission, while NFS only supports advisory lock.

	( SR:8606199444 CR:JAGad68631 )
	The yppasswd command updates fields other than the user
	password field in an NIS map.

	( SR:8606198866 CR:JAGad68055 )
	Can not cache large files (> 2GB) with cachefs mount.

	( SR:8606169485 CR:JAGad38760 )
	NFS/TCP client does not handle out-of-order streams messages
	correctly while attempting to connect to the server and can
	result in a client panic.

	PHNE_24035:
	( SR:8606196567 CR:JAGad65770 )
	AutoFS cannot unmount a cachefs type file system.

	( SR:8606208446 CR:JAGad77633 )
	NFS file lock recovery fails because rpc.statd matches the
	wrong hostname.

	( SR:8606207461 CR:JAGad76637 )
	rpcbind crashes with signal 10, Bus error (SIGBUS).

	( SR:8606164133 CR:JAGad33433 )
	The ypxfr command fails with the error message:
	"ypxfr: bind_to_server clntudp_create error: RPC unknown
	host".

	( SR:8606184904 CR:JAGad54106 )
	rpc.lockd can cause a user process to hang, if a loopback
	mount is specified with an alias hostname.

	( SR:8606207826 CR:JAGad77003 )
	The nisplus.server script does not kill the rpc.nispasswdd
	process when performing the "/sbin/init.d/nisplus.server
	stop" command.

	( SR:8606181688 CR:JAGad50904 )
	On a system with active lofs mounts managed by AutoFS, the
	"/sbin/shutdown" command may hang when the file systems are
	unmounted.

	( SR:8606160777 CR:JAGad30096 )
	AutoFS can not unmount hfs or cdrom file system types.

	( SR:8606168123 CR:JAGad37405 )
	An NFS/TCP client operation receives "NFS server not
	responding still trying" messages while attempting to access
	the server, even though the server system is up. In this
	case, NFS/TCP on the server shows many TCP connections for
	local address port 2049 in a CLOSE_WAIT state when
	performing a "netstat -an" command.

	( SR:8606203242 CR:JAGad72416 )
	A process sequentially reading a large file across an NFS
	mount runs extremely slow if, at the same time, there is
	another process sequentially writing a large file to an
	NFS mounted directory, and one or more biods are running on
	the system.

	( SR:8606152534 CR:JAGad21864 )
	AutoFS can mishandle unmounts when a server is down, which
	may appear as bdf command anomalies.

	( SR:8606202370 CR:JAGad71544 )
	NFS locks remain when killing NFS loopback mounted client
	applications.

	( SR:8606204523 CR:JAGad73705 )
	There is no support for cachefs.

	( SR:8606176017 CR:JAGad45257 )
	AutoFS directories are empty under heavy NFS load.

	( SR:8606193515 CR:JAGad62727 )
	Duplicate entries for direct AutoFS mounts show up in the
	/etc/mnttab file.

	( SR:8606186548 CR:JAGad55752 )
	An RPC server running in TCP multithreaded mode develops a
	file descriptor leak when clients are on the same machine as
	the server. Eventually the server fails to process the
	clients' requests when the process limit is attained.

	( SR:8606146332 CR:JAGad15675 )
	The I/O throughput on a locked file is low compared to the
	throughput on an unlocked file.

	PHNE_23502:
	( SR:8606183171 CR:JAGad52387 )
	UDP packets sent by remote users can cause RPC applications
	to abort.

	( SR:8606160596 CR:JAGad29916 )
	The /var/adm/automount.log file fills up the /var file
	system.

	( SR:8606178618 CR:JAGad47845 )
	The rename() system call always fails when trying to rename
	a directory in a cachefs-mounted file system, if the target
	directory name exists. 'errno' gets set to EPERM ("Not
	Owner").

	( SR:8606128739 CR:JAGac86286 )
	File corruption over NFS when NFS file server is TOC'ed.

	( SR:8606140609 CR:JAGad09968 )
	Core dump occurs when user belongs to more than 16 groups.

	( SR:8606159451 CR:JAGad28779 )
	A multithreaded process can hang when performing NFS file
	operations and concurrently writing core, forking, using a
	debugger, or undergoing job control. A similar situation
	arises in any process where a user can issue a CTRL-Z, send
	a SIGSTOP, or use a debugger. These hung processes also
	carry the potential of hanging the system.

	( SR:8606180764 CR:JAGad49985 )
	rpc.lockd causes user process to hang.

	( SR:8606180765 CR:JAGad49986 )
	rpc.lockd causes user process to hang.

	( SR:8606175862 CR:JAGad45102 )
	Mount points of automounter directories are not visible when
	executing the "ls" command.

	( SR:8606175781 CR:JAGad45021 )
	The "du" output is eight times higher over NFS with an HP
	server / Sun Client configuration when compared to an HP
	server / HP Client configuration.

	( SR:8606172747 CR:JAGad42007 )
	Changing an NIS+ user's password with nispasswd() or
	passwd() while the system is in trusted mode without
	specifying the dot "." notation (non fully qualified domain)
	results in an incorrect sub-domain being created.

	( SR:8606165859 CR:JAGad35150 )
	Data page fault panic while copying a file using NFS V3
	between an HP-UX client and an NT InterDrive server where
	the target filesystem is full.

	( SR:8606199460 CR:JAGaa35208 )
	The libnsl library uses a large amount of BSS and DATA
	memory.

	( SR:8606174017 CR:JAGad43270 )
	rpc.lockd drops the lock request from the same process for a
	different file.

	( SR:8606185238 CR:JAGad54440 )
	Partial record unlocking in NFS does not work properly.

	( SR:8606173363 CR:JAGad42623 )
	The "man nfsstat" command does not display all of the
	statistical data fields.

	( SR:8606178998 CR:JAGad48223 )
	Unnecessary NFS read before write is causing severe
	decreases in write performance.

	( SR:8606176384 CR:JAGad45622 )
	The boot process of a Linux client fails due to rpc.mountd
	not allowing AUTH_NULL authentication.

	( SR:1653311530 CR:JAGab46804 )
	Unable to use fsirand() on JFS file system.

	( SR:8606169796 CR:JAGad39062 )
	Data page fault panic due to bad machine name length in NFS
	request.

	( SR:8606171662 CR:JAGad40926 )
	exportfs sometimes does not work correctly when invalid host
	names are present in a host list in the /etc/exports file.

	( SR:8606179200 CR:JAGad48424 )
	rpc.lockd core dumps when the user process is interrupted
	with CTRL-C.

	( SR:8606169011 CR:JAGad38290 )
	The automount process hangs, making automounter mount points
	inaccessible.

	( SR:8606179951 CR:JAGad49173 )
	getservbyname() using NIS returns NULL when trying to
	resolve service aliases.

	( SR:8606167053 CR:JAGad36339 )
	An NFS/TCP client operation receives "NFS server not
	responding still trying" messages while attempting to access
	the server, even though the server system is up. The server
	displays "vmunix: WARNING: tcpd_thread_create: thread_create
	failed: 11" messages in /var/adm/syslog/syslog.log.

	PHNE_23248:
	( SR:8606188447 CR:JAGad57655 )
	autofs does not appear to remove inactive mounts from
	/etc/mnttab.

	PHNE_22878:
	( SR:8606127276 CR:JAGac68822 )
	A failing mount request may return a wrong error code.

	( SR:8606168603 CR:JAGad37881 )
	Loading binary via CacheFS is slower than via NFS.

	( SR:8606166823 CR:JAGad36110 )
	NFS client panics when the server is down.

	( SR:8606168604 CR:JAGad37882 )
	Periodically the CacheFS umount command hangs.

	( SR:8606135856 CR:JAGad04988 )
	Panic occurs when trying to umount a ufs filesystem which is
	still in the process of mounting.

	( SR:8606160808 CR:JAGad30127 )
	When mounting an NFS directory with the quota option, the
	quota does not get enforced.

	( SR:8606168606 CR:JAGad37884 )
	No visible increase in performance while reloading an
	application binary.

	( SR:8606166314 CR:JAGad35601 )
	The 'kill' and 'stop' NFS processes on a client do not work.

	( SR:8606145476 CR:JAGad14812 )
	Remote locking of a file occasionally leads to a system
	hang.

	( SR:8606155843 CR:JAGad25155 )
	NIS fails to return all groups for id/group command when
	concurrent access is allowed to maps.

	( SR:8606146885 CR:JAGad16228 )
	The "rpcinfo -u" command fails when the nfsd unregisters
	a running nfsd process on startup.

	( SR:8606159736 CR:JAGad29062 )
	Unexpected delay in unmounting of Autofs mounts.

	( SR:8606158230 CR:JAGad27560 )
	Occasionally umount may cause panic within
	nfs3_close/nfs_close.

	( SR:8606145517 CR:JAGad14853 )
	If NFS is stopped and restarted, the nfsd processes do not
	get re-registered with rpcbind, and rpcinfo commands fail.

	( SR:8606169239 CR:JAGad38515 )
	Cachefsstat is not returning the correct statistics.

	( SR:8606157592 CR:JAGad26923 )
	Newkey does not recognize the root password of the remote
	machine and returns an error, "ERROR, passwd differs from
	login passwd".

Defect Description: 
	PHNE_36168:
	( SR:8606471489 CR:JAGag26483 )
	PHNE_31097 and superseding patches include a fix for which
	rpc.lockd needs to determine if lock and unlock requests are
	done over a loopback NFS mount. This is done by comparing
	the IP address of the corresponding NFS server to the IP
	address of each LAN interface present on the system. If the
	backend used is nis, dns, or ldap and there is a high
	latency, rpc.lockd may have a performance degradation. If
	the backend used is files and the /etc/hosts file is large,
	there might be extra CPU consumption from scanning the file
	until the hostname is found. The number of IP addresses
	configured on the system may also affect performance, but to
	a much smaller degree.

	Resolution:
	If the NFS client is a pure client (i.e. it does not use
	loopback mounts), the fix for SR:8606366266 is now optional.
	The fix for SR:8606366266 is still enabled by default. The
	fix can be disabled by adding the line "LOCKD_PURE_CLIENT=1"
	to /etc/rc.config.d/nfsconf and restarting rpc.lockd and
	rpc.statd. If you disable the fix for SR:8606366266, you can
	re-enable the fix by either removing the
	"LOCKD_PURE_CLIENT=1" line from /etc/rc.config.d/nfsconf or
	by changing it to "LOCKD_PURE_CLIENT=0", and then restarting
	rpc.lockd and rpc.statd.

	( SR:8606474098 CR:JAGag28690 )
	The nfs.client script is used to stop automountd. If AutoFS
	is used with LOFS loopback mounts, these mount points still
	show up in the mount table and attempts to access the
	mount point result in an interruptible hang.

	Resolution:
	Modified the nfs.client script to unmount possible remaining
	AutoFS mounts.

	( SR:8606480160 CR:JAGag34291 )
	Attempts to mount a large file (e.g. mount <server>:/bigfile
	/clntfile) fail because rpc.mountd does not allow mounts on
	files with a size of 2 GB or larger.

	Resolution:
	Modified rpc.mountd to allow mounts on large files.

	( SR:8606480402 CR:JAGag34511 )
	The rpc.yppasswdd code does not function properly.

	Resolution:
	Modified the rpc.yppasswdd code to fix the problem.

	PHNE_35871:
	( SR:8606440810 CR:JAGaf98610 )
	The logfiles created by the rpc.mountd, rpc.rexd,
	rpc.rstatd, rpc.rusersd, rpc.rwalld, rpc.sprayd, rpcbind,
	ypbind, rpc.yppasswdd, and ypserv daemons allow all
	users to write to the file.

	Resolution:
	Only allow the file owner to have write permission.

	( SR:8606456591 CR:JAGag12989 )
	If an NFS mount command is run with mount options
	acregmin=0,acregmax=0 the values are set to
	acregmin=3600,acregmax=36000. If an NFS mount command is run
	with the mount options acdirmin=0,acdirmax=0 the values are
	set to acdirmin=3600,acregmax=36000. The values should all
	be set to zero as specified in the mount command.

	Resolution:
	Set the acregmin, acregmax, acdirmin, and acdirmax mount
	option values properly.

	( SR:8606461972 CR:JAGag17899 )
	Buffer overflow occurs in the rpc.mountd, rpc.lockd,
	rpc.statd, rpc.rexd, rpc.rstatd, rpc.rusersd, rpc.rwalld,
	rpc.sprayd, ypbind, rpc.yppasswdd, and ypserv daemons when
	the length of the logfile name exceeds 64 characters. This
	causes the creation of the logfile to fail.

	Resolution:
	Increased the size of the array that holds the logfile name
	to the maximum path length. If the file name length exceeds
	1023 characters, then the logfile name is truncated to 1023
	characters.

	( SR:8606466173 CR:JAGag21697 )
	The chkey, newkey, and udpublickey code does not function
	properly.

	Resolution:
	Modified the chkey, newkey, and udpublickey code to fix the
	problem.

	( SR:8606467933 CR:JAGag23289 )
	Access checking in the NFS server only allows modification
	to the file if the file has write permission. This prevents
	the file owner from modifying the file size.

	Resolution:
	Allow the file owner to modify the file size even if the
	file does not have write permission.

	( SR:8606467952 CR:JAGag23306 )
	A file system which has been locally mounted and exported
	cannot be unmounted if one of its files has been locked and
	unlocked by rpc.lockd. When rpc.lockd releases the file lock
	it does not release the vnode for that file.

	Resolution:
	Modified rpc.lockd to release the vnode for a file when it
	releases the last corresponding file lock.

	( SR:8606472898 CR:JAGag27667 )
	There are periods added to some rpc.mountd logging messages.
	These are inconsistent and possibly confusing, especially
	when there are pathnames involved.

	Resolution:
	Removed the unnecessary periods from the logging messages.

	PHNE_35418:
	( SR:8606266428 CR:JAGae30676 )
	The man page text for the automount -t command option needs
	a clearer description of its behavior.

	Resolution:
	Added text to the automount.1m man page to better describe
	the operation of the -t option.

	( SR:8606335443 CR:JAGae96518 )
	The logic for adding the current file offset to the number
	of bytes to be read, and comparing it with the file size, is
	inaccurate for large files.

	Resolution:
	An NFS client returns the error EOVERFLOW only when the file
	offset exceeds the maximum supported file size.

	( SR:8606410496 CR:JAGaf70378 )
	If multiple threads and processes try to access an NFS
	mounted directory simultaneously by creating and unlinking
	files, the unlink operations are serialized by the rnode
	lock of the NFS directory. One thread performs its unlink
	operation while the remaining threads sleep, waiting for the
	rnode lock. When the unlink operation completes, all of the
	threads are woken up and they compete for the rnode lock.
	One thread obtains the lock and the others sleep again. This
	sleep, wakeup, sleep, etc. context switching overhead causes
	the CPU utilization to increase.

	Resolution:
	Instead of waking up all threads waiting for the same rnode
	lock when the lock becomes available, wakeup one thread at a
	time. This fix is disabled by default. To enable the fix,
	set the kernel parameter nfs_wakeup_one to 1 by patching the
	vmunix file and rebooting. To patch the vmunix file
	(survives a reboot) use the following command:

	echo 'nfs_wakeup_one?W 0x1' |
	 adb -w -k /stand/vmunix /dev/kmem

	and then reboot your system. This command will have no
	effect until the system is rebooted. A kernel regeneration
	will require this step to be done again. Note that depending
	on the system configuration and applications being used,
	this tunable may result in increased or decreased
	performance. Customers need to analyze their applications
	and test to see if enabling this tunable provides better
	performance in their environment. Note that enabling this
	fix also enables the fix for waking up one biod at a time
	(SR:8606437373). This fix may also be enabled by setting the
	kernel parameter to 2 for compatibility with HP-UX 11i v2.
	For HP-UX 11i v2, this fix is enabled by setting the value
	to 1 or 2.

	( SR:8606437373 CR:JAGaf95562 )
	When an asynchronous read or write request is made, all of
	the biod daemons are woken up, but only one processes the
	request. This sleep, wakeup, sleep, etc. context switching
	overhead causes the CPU utilization to increase.

	Resolution:
	Instead of waking up all of the biod daemons when an
	asynchronous read or write request arrives, only wakeup one
	biod daemon. This fix is disabled by default. To enable the
	fix, set the kernel parameter nfs_wakeup_one to 1 by
	patching the vmunix file and rebooting. To patch the vmunix
	file (survives a reboot) use the following command:

	echo 'nfs_wakeup_one?W 0x1' |
	 adb -w -k /stand/vmunix /dev/kmem

	and then reboot your system. This command will have no
	effect until the system is rebooted. A kernel regeneration
	will require this step to be done again. Note that enabling
	this fix will also enable the fix for waking up only one
	thread which is sleeping on the same rnode lock
	(SR:8606410496). This fix may also be enabled by setting the
	kernel parameter to 2 for compatibility with HP-UX 11i v2.
	For HP-UX 11i v2, this fix is only enabled by setting the
	value to 2.

	( SR:8606441116 CR:JAGaf98873 )
	The logfiles created by the rpc.lockd and rpc.statd daemons
	allow all users to write to the file.

	Resolution:
	Only allow the file owner to have write permission.

	( SR:8606445462 CR:JAGag02920 )
	When the NFS server is disabled and enabled (or restarted)
	through SAM, SAM masks SIGTERM. Since the TCP nfsd ignores
	SIGTERM, it does not get killed when the NFS server is
	stopped. When the NFS server is started again, the other
	nfsd's are not started.

	Resolution:
	Modified the TCP nfsd to handle SIGTERM like the UDP nfsd
	does.

	( SR:8606450912 CR:JAGag07918 )
	The read buffer for the revnetgroup command is limited to
	1024 characters. If a netgroup record contains more than
	1024 characters this can cause revnetgroup to dump core.

	Resolution:
	Modified revnetgroup to discard any characters exceeding the
	read buffer length.

	( SR:8606460011 CR:JAGag16103 )
	The nsquery command cannot interpret a group name or user
	name which begins with a numeral. This results in the
	nsquery command returning incorrect information for these
	entries in the /etc/group and /etc/passwd files.

	Resolution:
	Modified nsquery to interpret group names and user names
	that begin with a numeral.

	( SR:8606394173 CR:JAGaf54209 )
	The XDR routine used by Kernel RPC to encode and serialize
	file content allocates buffers with a maximum size of 2048
	bytes. Thus, NFS operations are not able to utilize the
	jumbo frame capability of a network interface.

	Resolution:
	Modified the XDR routine used by Kernel RPC to allocate
	larger buffers.

	PHNE_34938:
	( SR:8606427857 CR:JAGaf87338 )
	There is a race condition in the RPC subsystem which can
	result in an incorrect return status when the NFS client
	makes the RPC call. This causes the client to panic.

	Resolution:
	Added protection to the data structures in the RPC subsystem
	to prevent the race condition.

	( SR:8606429925 CR:JAGaf89391 )
	The nisclient script truncates the process name to eight
	characters before obtaining the process ID. Since the
	nis_cachemgr process name is 12 characters long it was not
	terminated.

	Resolution:
	Modified the nisclient script to expand the process name to
	12 characters.

	( SR:8606438393 CR:JAGaf96478 )
	The sequential read, write, and lseek operations are not
	efficiently coordinated. Cached data is purged unnecessarily
	so more over-the-wire calls are needed. This affects
	performance.

	Resolution:
	Added a new kernel parameter nfs3_adaptive_cache_validate,
	which, when enabled, provides a weak cache consistency check
	when a write operation is followed by a read. It also
	invalidates the cache if a read operation is followed by a
	write. This fix is disabled by default. To enable the fix,
	set the kernel parameter nfs3_adaptive_cache_validate
	to 1 by patching the vmunix file and rebooting. To patch the
	vmunix file (survives a reboot) use the following command:

	echo 'nfs3_adaptive_cache_validate?W 0x1' |
	 adb -w -k /stand/vmunix /dev/kmem

	and then reboot your system. This command will have no
	effect until the system is rebooted. A kernel regeneration
	will require this step to be done again. Note that depending
	on the system configuration and applications being used,
	this parameter may result in increased or decreased
	performance. Customers need to analyze their applications
	and test to see if enabling this parameter provides better
	performance in their environment.

	( SR:8606440308 CR:JAGaf98199 )
	The rpc.lockd process manages an internal queue to keep
	track of all requests. In case of failed reclaim request, an
	internal queue has to be cleaned. The queue is only
	partially cleaned and may get corrupted, which causes
	rpc.lockd to dump core intermittently.

	Resolution:
	Properly cleanup the internal queue so that it does not get
	corrupted.

	( SR:8606441512 CR:JAGaf99242 )
	When a second instance of automountd is invoked, the daemon
	references an uninitialized variable. This causes a core
	dump.

	Resolution:
	Corrected the logic so that the uninitialized variable is
	not referenced in this case.

	( SR:8606446862 CR:JAGag04211 )
	When the NFS server is stopped, there is a variable which is
	decremented as nfsd processes are stopped. When this
	variable becomes zero, the nfsd transport table is cleaned
	up. On a multi-processor system, the variable may not
	reflect the actual value due to inadequate protection. This
	causes defunct nfsd processes when the NFS server is
	restarted.

	Resolution:
	Protect the variable which keeps track of the number of
	nfsd processes with a lock.

	PHNE_34662:
	( SR:8606172586 CR:JAGad41846 )
	1. When the NFS client is stopped, it stops and restarts the
	NFS server. Stopping the NFS server involves stopping the
	nfsd processes. However, when the NFS client script stops
	the NFS server, one TCP nfsd process remains running. When
	the NFS server is restarted, it checks to see if there are
	any nfsd processes running. Since there is an nfsd process
	running, the other nfsd processes are not started.
	2. When "/sbin/init.d/nfs.client stop" is run in a highly-
	available NFS environment, the corresponding "nfs.server
	stop" unexports the file systems.

	Resolution:
	Removed the "/sbin/init.d/nfs.server stop" and
	"/sbin/init.d/nfs.server start" calls from the
	/sbin/init.d/nfs.client script.

	( SR:8606391790 CR:JAGaf51922 )
	The rpc.lockd, rpc.statd, and rpc.mountd daemons use random
	ports for transport connections. This makes it difficult to
	configure firewalls which require specific port numbers to
	be used.

	Resolution:
	An interface is provided for assigning port numbers for the
	rpc.lockd, rpc.statd, and rpc.mountd daemons. To assign port
	numbers, add the following variables to the end of the
	/etc/rc.config.d/nfsconf file:
	LOCKD_PORT=<port number>
	STATD_PORT=<port number>
	MOUNTD_PORT=<port number>

	The port number can be any value from 1 to 65536. For
	example:
	LOCKD_PORT=1234
	STATD_PORT=5678
	MOUNTD_PORT=9101

	The daemons need to be restarted for the change to take
	effect. To revert back to random port numbers, delete the
	variables and restart the daemons.

	NOTE: The LOCKD_PORT variable will be obsolete in the HP-UX
	11i v3 release, since the 11i v3 rpc.lockd uses port 4045.
	HP recommends that you use port 4045 for the LOCKD_PORT
	value. The STATD_PORT and MOUNTD_PORT variables will be
	supported in 11i v3, although the configuration file will be
	/etc/default/nfs instead of /etc/rc.config.d/nfsconf.

	( SR:8606431961 CR:JAGaf91403 )
	The TCP nfsd uses a circular linked list to manage the TCP
	connections. This list management was broken and resulted in
	an endless loop.

	Resolution:
	Modified the list management logic to eliminate the endless
	loop.

	( SR:8606432689 CR:JAGaf92128 )
	The algorithm used to calculate the initial value of the
	transaction identifier (XID) does not provide a mechanism
	for a highly granular value. This can cause XIDs to be
	re-used. The possibility of XIDs being re-used increases if
	the NFS clients are rebooted frequently or if the NFS server
	has a large duplicate cache. Having duplicate XIDs could
	result in data corruption.

	Resolution:
	Increased the granularity of the initial XID from 1 in
	990000 to 1 in 4294967295. This greatly reduces the chance
	of duplicate XIDs.

	PHNE_34293:
	( SR:8606383205 CR:JAGaf43399 )
	The Local Locking feature is not available on NFS. Enabling
	this feature can improve NFS performance by avoiding RPC
	calls.

	Resolution:
	Implemented the Local Locking feature on NFS. This feature
	is enabled by using the "llock" mount option. If the file
	system is mounted using this option, the Network Lock
	Manager is bypassed when locking files over NFS.

	( SR:8606392946 CR:JAGaf53027 )
	NFS was using a released credential for I/O. When the stale
	credential was referenced the system panicked.

	Resolution:
	The credential is now held before I/O so that the credential
	is not released during NFS I/O.

	( SR:8606394934 CR:JAGaf54948 )
	Memory allocation failures are not handled in certain areas
	of the RPC libnsl library. This causes rpcbind to dump core
	when the system runs out of memory.

	Resolution:
	Instead of dumping core on a memory allocation failure,
	return the error code to the calling function.

	( SR:8606421959 CR:JAGaf81784 )
	A directory on an NFS server is mounted on a logical volume,
	exported, and mounted by an NFS client. Then the directory
	is unmounted by the client, unexported by the server,
	unmounted from the logical volume, and re-exported (this
	time as a sub-directory of a directory that was already
	exported). Data cached by rpc.mountd still points to the
	file system mounted on the logical volume, and this causes
	the mount command to fail.

	Resolution:
	Added a check to see if the directory that was already
	exported and the directory being exported are in the same
	file system so that the mount command does not use stale
	cached data and does not fail in this scenario.

	( SR:8606425181 CR:JAGaf84701 )
	There is no error checking done when exportfs writes to a
	temporary file in the /var/tmp directory. When the temporary
	file is copied to /etc/xtab, the /etc/xtab file is
	overwritten with a blank file.

	Resolution:
	If the /var file system is full, exportfs handles this
	error condition and does not overwrite the /etc/xtab file.

	PHNE_33971:
	( SR:8606379232 CR:JAGaf39481 )
	The rstat(3N) man page is inconsistent with the code. This
	can cause compilations using the cp_time field to fail.

	Resolution:
	Modified the rstat(3N) man page to correct the size of
	stats.cp_time, statswtch.cp_time, and statstime.cp_time.

	( SR:8606390486 CR:JAGaf50632 )
	An NFS client thread sends a connect request to the server
	and receives what it assumes is the reply message from the
	server. However, the TCP transport is in the wrong state, so
	the reply message that is received is out of order and the
	client misinterprets this message causing a panic.

	Resolution:
	The client verifies that the underlying TCP transport is in
	the bound state before sending a connect request to the
	server.

	( SR:8606394075 CR:JAGaf54115 )
	This product update contains minor enhancements required to
	enable the HP-UX Enhanced Key Components feature.

	Resolution:
	Modified the key components to execute in enhanced mode in
	the presence of the HP-UX Enhanced Key Components product.
	Modified the man pages for the key components to include
	information for using HP-UX Enhanced Key Components.

	( SR:8606401733 CR:JAGaf61670 )
	The structure which stores the client file descriptors can
	only handle 2048 file descriptors. If more than 2048 clients
	connect to the server, the rpc.lockd process dumps core when
	it tries to cache the file descriptor data and the rpc.statd
	process may dump core during file lock recovery.

	Resolution:
	Increased the cache size for the client file descriptor data
	in rpc.lockd and rpc.statd.

	( SR:8606410663 CR:JAGaf70545 )
	When an NFS client thread sends a bind request to the
	underlying TCP transport for a particular reserved port, and
	the port is not in the proper state, TCP returns an error
	message. Instead of routing the error message to the stream
	head where the thread is waiting for the bind response, the
	message is consumed by the RPC layer. This causes the thread
	to hang, waiting for a response which it never receives.

	Resolution:
	Instead of routing all transport messages to the RPC layer,
	only route a specific set. Transport messages such as
	responses to bind requests are now routed to the stream
	head.

	( SR:8606412876 CR:JAGaf72738 )
	A TCP connection can be accessed by multiple NFS client
	threads. If one thread tries to access a connection after
	another thread has destroyed it, stale pointers are accessed
	by Kernel RPC. This corrupts other data structures and
	causes a panic.

	Resolution:
	Data structures pertaining to a dead TCP connection are
	adequately protected when other threads remain dependent on
	them.

	( SR:8606414935 CR:JAGaf74793 )
	When a password change is requested, rpc.yppasswdd creates a
	new temporary file, changes the password for the user, and
	then renames this temporary file as /etc/passwd. The
	temporary file is opened with 0644 permissions so when a
	rename is done the permissions of /etc/passwd become 0644.

	Resolution:
	Modified rpc.yppasswdd to maintain the permissions of the
	/etc/passwd file when a password is changed.

	( SR:8606412878 CR:JAGaf72740 )
	A Kernel RPC thread that is sleeping and waiting for a
	resource should be woken up when the resource is available.
	A window existed between the time the thread released the
	lock and the time it was placed in the sleep queue. This
	caused a situation where the thread would not be woken up
	when the resource became available which caused the thread
	to hang.

	Resolution:
	Eliminated the timing window by waiting until after the
	thread is added to the sleep queue to release the lock.

	PHNE_33498:
	( SR:8606167807 CR:JAGad37090 )
	Some references to vhe functions were not removed when the
	functions were obsoleted.

	Resolution:
	Removed all references to the vhe functions from the
	ypinit(1m) man page.

	( SR:8606406594 CR:JAGaf66500 )
	Non-RPC UDP messages containing non-zero-length data can be
	inserted into the STREAMS read queue. These messages exhaust
	the number of allowed receive retries before any valid RPC
	data is received. This causes commands such as "ls" which
	attempt to access a file system with a soft NFS mount over
	the UDP transport to fail.

	Resolution:
	The invalid RPC UDP messages are received and ignored
	without affecting the retry counter.

	( SR:8606413268 CR:JAGaf73129 )
	CacheFS uses a linear search to release buffers allocated by
	vnodes for a mount point. If the buffer cache is large,
	which can occur with a single "ll" command on a large
	directory, the unmount can take anywhere from 30 seconds to
	over five minutes to complete.

	Resolution:
	A new mechanism is used to release the buffers associated
	with a mount point when the mount point is unmounted. This
	fix requires PHKL_33367 to be installed.

	( SR:8606413731 CR:JAGaf73591 )
	VFS requires NFS to purge the file handle cache if an error
	is returned from rfs3call(). If the cache is not purged, a
	hang occurs.

	Resolution:
	Purge the file handle cache if an error is returned from
	rfs3call().

	PHNE_33315:
	( SR:8606385895 CR:JAGaf46049 )
	When writing over an NFS mount point, there are unnecessary
	read-before-write calls done after 2 GB of data has been
	written to the file. This occurs because the calculation of
	the file offset using the block number and block size
	results in an overflow condition. This causes read
	avoidance logic to fail and affects performance.

	Resolution:
	Modified the file offset calculation to avoid an overflow
	condition.

	( SR:8606394445 CR:JAGaf54468 )
	RPC maintains a server address cache that is used by AutoFS.
	The server addresses remain in cache until they are flushed
	out, and there is no timeout mechanism for the cache. If one
	of the IP addresses is modified, AutoFS could use the old IP
	address.

	Resolution:
	A timeout mechanism has been implemented for the RPC server
	address cache so that AutoFS uses the correct IP address.
	The cache expires after 180 seconds.

	( SR:8606399902 CR:JAGaf59858 )
	Network congestion results in sending EAGAIN or TFLOW
	(flow control) messages to the server, which is in
	non-blocking I/O mode. The server continues to send data to
	the client, resulting in more EAGAIN and TFLOW messages.
	This causes high CPU utilization.

	Resolution:
	The server now waits for the transport to be ready to accept
	data before trying to re-send data to the client.

	( SR:8606400085 CR:JAGaf60041 )
	The rpc_clnt_calls(3N) man page lists the parameter
	"eachresult" for the rpc_broadcast_exp function as the tenth
	parameter. It should be listed as the eighth parameter.

	Resolution:
	Corrected the order of the parameters for the
	rpc_broadcast_exp function in the rpc_clnt_calls(3N) man
	page.

	( SR:8606401738 CR:JAGaf61675 )
	The rpc.lockd and rpc.statd processes do not close the file
	descriptor when logging is disabled with SIGUSR2. If all of
	file descriptors are used this causes the process to hang.

	Resolution:
	The logging routines now close the file descriptor when
	logging is disabled.

	( SR:8606402519 CR:JAGaf62454 )
	The rpc.lockd and rpc.statd processes attempt to log I/O
	errors without checking whether logging is enabled or not.
	If logging is not enabled then an attempt is made to write
	to a null file descriptor. If libc patch PHCO_24942 (or a
	superseding patch) is installed this causes a core dump,
	otherwise an EBADF error is returned. This problem occurs
	when the processes are started without using the "-l"
	option.

	Resolution:
	The logging procedures now check whether or not logging is
	enabled before attempting to log I/O errors.

	( SR:8606405252 CR:JAGaf65172 )
	Memory allocated for arguments in rpc.rquotad is not freed.
	This results in a memory leak which can lead to a core dump.

	Resolution:
	The memory allocated for arguments in rpc.rquotad is now
	freed before returning from the function.

	PHNE_32811:
	( SR:8606345889 CR:JAGaf06735 )
	After a server's rpc.lockd is restarted, the clients attempt
	to reclaim their locks. The server waits for a grace period
	for all client rpc.lockd reclaim requests. When the grace
	period expires, granting reclaim requests can cause data
	corruption. The server's rpc.lockd does not check whether
	the lock request is a new request or a reclaim request after
	the grace period expires.

	Resolution:
	The server's rpc.lockd was modified to deny reclaim requests
	after the grace period expires.

	( SR:8606377207 CR:JAGaf37485 )
	If rpc.lockd is performing a re-transmission and it receives
	a SIGALRM signal, the rpc.lockd process exits.

	Resolution:
	Ignore the SIGALRM signal while performing the
	re-transmission.

	( SR:8606389345 CR:JAGaf49493 )
	With a soft NFS mount, the number of retransmissions that
	actually occur is one less than the value specified in the
	retrans option (or the default) for the NFS mount command.
	Also, there exists an inconsistency in the documentation of
	the default retrans value between the mount_nfs man page
	and the NFS Services Administrator's Guide.

	Resolution:
	Corrected the inconsistency in the retrans value displayed
	by nfsstat when used with -c and -m. Corrected the
	inconsistency in the documentation of the default retrans
	value by updating the NFS Services Administrator's Guide
	to correct the default retrans value to 5.

	( SR:8606393839 CR:JAGaf53894 )
	The rename() system call behaves incorrectly when renaming
	a directory in a CacheFS-mounted file system using NFSv2,
	if the target name is an existing directory. The incorrect
	behavior is due to the reference count for a directory
	getting incremented to more than 1 (due to CacheFS and NFS).
	This causes "unlink-open-file" logic to be executed, which
	is only applicable to regular files and not directories.
	As a result a "Not Owner" error returned. If the target name
	is an empty directory, the rename() call should succeed. If
	the target name is a non-empty directory, a "File exists"
	error should be returned.

	Resolution:
	An additional check for the file type is added before the
	"unlink-open-file" logic is executed.

	( SR:8606394223 CR:JAGaf54255 )
	The "ypwhich -m" command fails when the client is bound to
	a Solaris NIS server. This is because the receiving buffer
	is not large enough to handle the message returned by the
	server if there is a large number of NIS domains.

	Resolution:
	Increased the size of the client's receiving buffer. Also
	increased the size of the message returned by the server.

	PHNE_32477:
	( SR:8606386532 CR:JAGaf46686 )
	When clnt_tli_create() is called with large send/receive
	buffers, certain error checking is not done which results in
	the application dumping core.

	Resolution:
	Additional error checking is done when calling
	clnt_tli_create() with large send/receive buffers.

	( SR:8606387765 CR:JAGaf47918 )
	If a write() system call is interrupted by a signal before
	it writes any data to the NFS server (this could happen if
	the server is down), it should return -1 and have errno set
	to EINTR. Instead, the return value of write() is
	inconsistent. It can return success and have errno set to
	0, or it can return -1 and have errno set to EINTR. This is
	because NFS does a "read before write" if the write length
	is smaller than the block size - it reads one block,
	modifies it, and writes it back. If "read before write" is
	used, the signal interrupts the read path and the behavior
	is as expected (returns -1). If no "read before write" is
	used (the file is being created, the buffer has already been
	read because of a previous write, or the write is one block
	long) the signal interrupts the write path and the behavior
	is faulty and returns success. This occurs because the value
	returned by bwrite() is ignored for synchronous writes.

	Resolution:
	The value returned by bwrite() for synchronous writes is now
	checked and returned to the application.

	( SR:8606387807 CR:JAGaf47960 )
	If an NFS client sends a read request with an invalid read
	size, the server crashes while allocating memory.

	Resolution:
	Reject read requests greater than the maximum allowable
	transfer size for PV2. Allocate memory for the maximum
	allowable transfer size for read requests greater than the
	maximum allowable transfer size for PV3.

	( SR:8606389142 CR:JAGaf49290 )
	A TCP transport handle is passed to a UDP routine because a
	flag is not set correctly in some rpc.lockd procedures. This
	causes rpc.lockd to dump core.

	Resolution:
	The rpc.lockd procedures now check whether the transport
	handle is TCP or UDP and set the flag correctly.

	( SR:8606389255 CR:JAGaf49403 )
	A deadlock situation occurs between three NFS threads in a
	single process. Thread A sleeps non-interruptibly in the
	following code path:

	_swtch+0xc4
	_sleep_one+0x1a8
	ksleep_one+0x2f4
	hp_cv_wait+0x60
	nfs_purge_rddir_cache+0x6c
	nfs3create+0x258
	nfs3_create+0xc4
	vns_create+0xa4
	vn_create+0xd4
	vn_open+0x19c
	copen+0xa8
	open+0x38
	syscall+0x768
	syscallinit+0x55c

	Thread A waits for a resource owned by thread B (in this
	case it waits for thread B to finish accessing directory
	data that is being updating) but thread B sleeps
	interruptibly in the following code path:

	_swtch+0xc4
	thread_process_suspend+0x20c
	issig+0x338
	_sleep_one+0x2e0
	ksleep_one+0x2f4
	hp_cv_wait_sig+0x64
	nfs3_readdir2+0x1f4
	getdents+0xc8
	syscall+0x768
	syscallinit+0x55c

	Thread C calls vfork() which sends SIGSTOP to all the
	threads in the process, suspending thread B. Thread C is in
	the following code path:

	_sleep+0x218
	thread_suspend_wait+0x2e8
	for_specific_threads+0xc0
	process_wide_suspend_wait+0x28
	newproc+0x1f8
	fork1+0x220
	vfork+0x14
	syscall+0x768
	syscallinit+0x55c

	Thread A is still waiting for the resource to be
	freed by thread B, and thread C waits for thread A to
	process SIGSTOP, which causes the hang.

	Resolution:
	When an NFS thread does an interruptible sleep, block
	SIGSTOP so that the thread does not become suspended.

	( SR:8606348790 CR:JAGaf09611 )
	The master map syntax for specifying a direct map is not
	described in the automount(1m) man page.

	Resolution:
	Added a description on how to use direct maps.

	( SR:8606381800 CR:JAGaf42012 )
	The Enhanced AutoFS product implementation has obsoleted the
	need for the JAGad50904 fix. This fix prevented a possible
	hang during system shutdown.

	Resolution:
	Added logic to the nfs.client script so that the fix for
	JAGad50904 is only exercised if the Enhanced AutoFS product
	is not installed.

	( SR:8606393701 CR:JAGaf53756 )
	There is a small memory leak in libnsl which occurs every
	time an automountd thread is created.

	Resolution:
	Modified the libnsl code to eliminate the memory leak.

	PHNE_31929:
	( SR:8606373075 CR:JAGaf33480 )
	Memory mappings are not removed while truncating memory
	mapped files over NFS.

	Resolution:
	Modified the NFS truncate path to completely remove the
	memory mappings.

	( SR:8606375121 CR:JAGaf35426 )
	For an AutoFS loopback mount (LOFS), the filesystem name is
	not passed correctly from the on command. This causes a
	mount failure and thus the on command also fails.

	Resolution:
	Modified the on command to mount the correct filesystem for
	loopback mounts (LOFS).

	( SR:8606379022 CR:JAGaf39271 )
	If an NFSv3 client attempts to access a remote NFS server
	and the requested file is not currently available, the
	server returns an NFS3ERR_JUKEBOX error to the client. Upon
	receiving this error, the client re-issues the request 10
	seconds later. This delay time affects NFS performance.

	Resolution:
	Made the delay time variable global so that it can be
	adjusted by adb. The default delay time is still 10 seconds.
	To modify the delay time, set the kernel variable
	nfs3_jukebox_delay by patching the vmunix file and
	rebooting, or by patching the kernel image in memory. To
	patch the vmunix file (survives a reboot), use the
	following command:

	echo 'nfs3_jukebox_delay?W 0d300' |
	 adb -w /stand/vmunix /dev/kmem

	The above example sets the delay time to 3 seconds.
	The unit of the delay time variable nfs3_jukebox_delay is
	the number of clock ticks (number of seconds * 100).

	To patch the in-memory kernel (does not survive a reboot),
	use the command (for a delay time of 3 seconds):

	echo 'nfs3_jukebox_delay/W 0d300' |
	 adb -w /stand/vmunix /dev/kmem

	A kernel regeneration will require these steps to be done
	again.

	PHNE_31097:
	( SR:8606345966 CR:JAGaf06811 )
	If AUTO_MASTER is set to "" in the /etc/rc.config.d/nfsconf
	file, and AutoFS is started with the
	"/sbin/init.d/nfs.client start" command, the
	/etc/auto_master file is not created. The text that should
	be in the /etc/auto_master file is echoed to a null variable
	and appears in the /etc/rc.log file and also on stderr.

	Resolution:
	The nfs.client script was modified to create the
	/etc/auto_master map with the default entry if the
	AUTO_MASTER variable in /etc/rc.config.d/nfsconf is set to
	"".

	( SR:8606347603 CR:JAGaf08425 )
	Currently libnsl does not have any provision to identify
	the end-point pair for UDP based RPC applications.

	Resolution:
	Modified libnsl to add functionality to identify the
	end-point pair for UDP based RPC applications.

	( SR:8606354067 CR:JAGaf14861 )
	If nfsd's need to be restarted, then previously running
	nfsd's must be stopped first. This is not documented in the
	nfsd man page.

	Resolution:
	The nfsd man page has been updated to mention that nfsd's
	must be stopped before new nfsd's are started.

	( SR:8606359725 CR:JAGaf20421 )
	The automountd process may dump core during an RPC unmount
	call. This occurs if automountd is started with the "-v"
	option and if an error occurs in the RPC umount call. This
	is because a client handle is passed to a function after it
	has been destroyed.

	Resolution:
	Relocated the function calls which destroy the client
	handle.

	( SR:8606360695 CR:JAGaf21402 )
	An NFS TCP client continuously adds data that is received
	from the NFS server to an RPC message fragment while trying
	to assemble an RPC reply message from the server when the
	fragment size specified in the record-marking header for a
	fragment sent from the server is wrong.

	Resolution:
	The NFS TCP client is modified to disconnect if the size of
	an RPC message fragment received goes beyond a specified
	limit.

	( SR:8606364296 CR:JAGaf24937 )
	The error number is not set prior to returning from the
	netdir_getbyname() function.

	Resolution:
	Modified the netdir_getbyname() function to set the error
	number before returning.

	( SR:8606364383 CR:JAGaf25022 )
	Threads that are waiting for an NFS rnode lock cannot be
	interrupted. As a result they will sleep until the NFS
	server becomes available or until the lock gets released,
	which causes applications to hang.

	Resolution:
	Created a kernel variable that allows toggling between the
	existing behavior of non-interruptible threads and allowing
	the threads that are waiting for the rnode lock to be
	interrupted. This fix is disabled by default. To enable the
	fix, set the kernel parameter nfs_new_rnode_lock_code to 1
	by patching the vmunix file and rebooting, or by patching
	the kernel image in memory. To patch the vmunix file
	(survives a reboot), use this command:
	echo 'nfs_new_rnode_lock_code?W 0d1' |
	 adb -w -k /stand/vmunix /dev/kmem
	To patch the in-memory kernel (does not survive a reboot),
	use this command:
	echo 'nfs_new_rnode_lock_code/W 0d1' |
	 adb -w -k /stand/vmunix /dev/kmem
	A kernel regeneration will require these steps to be done
	again.

	( SR:8606365866 CR:JAGaf26496 )
	An NFS client does not check whether the byte count returned
	by the server exceeds the requested number of bytes. If
	additional data is returned by the server, the client
	crashes while attempting to copy the extra data.

	Resolution:
	Modified the NFS client to have read requests fail with the
	error EIO if the server returns more data than requested.

	( SR:8606369177 CR:JAGaf29721 )
	Under heavy load, memory in an internal linked list is
	overwritten causing rpcbind(1M) to core dump.

	Resolution:
	Modified the buffer allocation in rpcbind to avoid memory
	corruption.

	( SR:8606366266 CR:JAGaf26870 )
	The server's rpc.lockd grants the same lock to two blocking
	clients. One client is the server with a loopback mount
	using a server name other than the name returned by the
	hostname command.

	Resolution:
	The server name for locking requests is changed to the name
	returned by the gethostname function for loopback mounts if
	using a name other than that returned by the hostname
	command.

	( SR:8606379191 CR:JAGaf39440 )
	There is a restriction that limits establishing quotas to
	user ID's less than 67,000,000. The rpc.rquotad does not
	currently support largefiles. Largefiles must be supported
	to establish quotas for user ID's greater than or equal to
	67,000,000.

	Resolution:
	Modified rpc.rquotad to support largefiles. This change, in
	conjunction with the fix for JAGaf21431, eliminates the
	restriction of only being able to establish quotas for user
	ID's less than 67,000,000.

	( SR:8606379708 CR:JAGaf39957 )
	Kernel RPC performs re-connects to an NFS/TCP server on
	behalf of an NFS/TCP client using the same local TCP
	end-point which was originally connected. It does not create
	a new local TCP end-point bound to a different port.

	Resolution:
	The kernel RPC/TCP client is modified to create a new local
	TCP end-point for connection to a remote TCP end-point
	whenever a disconnect is received for an existing local-
	remote TCP connection tuple.

	PHNE_30661:
	( SR:8606354850 CR:JAGaf15606 )
	The ypxfr failure is caused by improper use of the
	dbmclose() API.

	Resolution:
	Modified the ypxfr code was to call dbmclose() as specified
	in its prototype definition.

	( SR:8606355618 CR:JAGaf16332 )
	The client's rpc.lockd sends a re-claim lock request for
	pending unlock, cancel, and test locks. It should only send
	re-claim lock requests for granted locks. If the server is
	performing rpc.lockd crash recovery, the client's rpc.lockd
	dumps core after sending a re-claim lock request for a
	pending lock.

	Resolution:
	Modified rpc.lockd so that the client only sends re-claim
	requests for granted locks.

	( SR:8606357066 CR:JAGaf17766 )
	The error message "exportfs error: /etc/xtab in use. Please
	try again." is not accurate. The global file lock table
	maintained in the kernel is full.

	Resolution:
	The exportfs command is modified to print the error message
	"Cannot open or lock /etc/xtab. Please try again." Note that
	if you are using HP Serviceguard NFS Toolkit, it is
	recommended to install version A.11.11.05 since this fix may
	affect package startup and shutdown.

	( SR:8606357361 CR:JAGaf18061 )
	The CacheFS mount command dumps core if the name of the
	directory being mounted contains more than 126 characters.

	Resolution:
	Modified the CacheFS mount code to return the error "cacheid
	too long" if the total number of characters in the name of
	the directory being mounted exceeds the limit.

	( SR:8606358606 CR:JAGaf19305 )
	Memory allocated for a message block is not being freed when
	an XDR failure occurs while replying to an NFS/UDP client.

	Resolution:
	Memory allocated for a message block in the NFS server is
	now freed after an XDR failure while replying to an NFS/UDP
	client.

	( SR:8606363276 CR:JAGaf23938 )
	The nfs_portmon variable determines whether or not an NFS
	server only processes requests from privileged ports. This
	functionality is not documented.

	Resolution:
	Documented the tunable parameter nfs_portmon in the nfsd man
	page.

	( SR:8606329363 CR:JAGae90487 )
	There is a race condition between the lock and write threads
	which causes the panic. An uncached temporary buffer is used
	for buffered I/O.

	Resolution:
	Temporary buffers are released after I/O completes. This
	prevents the temporary buffer from taking the buffered I/O
	path.

	PHNE_30380:
	( SR:8606382150 CR:JAGaf42361 )
	When an RPC application is started by inetd, a connection is
	established. The transport interface state for the
	connection is not checked, which causes libnsl to write to
	an incorrect memory location. This can lead to the
	application terminating unexpectedly and dumping core. This
	occurs only with applications that use TCP and call
	svctcp_create() or svc_tli_create(). Applications that call
	svc_tli_create() with a null netconfig parameter (the second
	parameter) are not affected.

	Resolution:
	Modified libnsl to check for the transport interface state
	to avoid writing to an incorrect memory location.

	PHNE_30378:
	( SR:8606319551 CR:JAGae82039 )
	The rpc_soc man page does not mention the RPC socket library
	(-lrpcsoc).

	Resolution:
	The rpc_soc man page was modified to include information
	about the RPC socket library (-lrpcsoc).

	( SR:8606339927 CR:JAGaf00848 )
	If the automount process is killed with SIGTERM, there are
	entries left in the /etc/mnttab file which cause automount
	to hang when it is re-started. This is caused by a
	synchronization problem between the signal handler and the
	mount module.

	Resolution:
	Fixed the synchronization problem between the signal handler
	and the mount module.

	( SR:8606344107 CR:JAGaf04959 )
	The problem occurs when packets are delivered out of order
	and some of the packets are dropped due to the network
	environment being stressed. The response to the unlock
	request arrives later than the response to the blocked lock
	request. The client's rpc.lockd discards the reply from the
	server for the blocked lock request, since the lock in
	question is still held by another process on the client
	machine, and it removes the blocked lock request from the
	wait queue. If the reply to the cancel request arrives when
	there is no entry for this lock in the wait queue, the
	client's rpc.lockd daemon tries to add this lock to the
	granted lock queue whose pre_fe field is null, which causes
	the core dump.

	Resolution:
	When the client's rpc.lockd receives the granted lock for
	the blocked lock request, it removes the lock from the
	wait queue only if the lock is successfully added to the
	granted lock queue.

	( SR:8606345310 CR:JAGaf06160 )
	Insufficient buffer size allocated to store NIS+ subdomain
	information.

	Resolution:
	The buffer size has been increased to the maximum buffer
	size supported by xdr_string().

	( SR:8606346094 CR:JAGaf06921 )
	The NFS_TCP configurable environment variable is valid only
	for the 11.00 release of HP-UX. The setoncenv command was
	not modified to remove it from subsequent HP-UX releases.

	Resolution:
	Modified the setoncenv command so that NFS_TCP is not a
	configurable variable.

	( SR:8606346132 CR:JAGaf06959 )
	The NFS version information being passed to the kernel
	profiling code is not being interpreted correctly on 64-bit
	systems.

	Resolution:
	The code passing NFS version information to the kernel
	profiling code has been modified with the correct variable
	type.

	( SR:8606347226 CR:JAGaf08050 )
	Non-RPC UDP messages containing zero-length data can be
	inserted onto the STREAM read queue and exhaust the number
	of allowed receive retries before any valid RPC data is
	received.

	Resolution:
	Modified the code to discard invalid zero-length data
	packets without affecting the received retry counter while
	receiving these invalid packets.

	( SR:8606347264 CR:JAGaf08087 )
	AutoFS does not handle direct maps properly when looking up
	the current and parent directories.

	Resolution:
	Modified AutoFS to work properly when looking up the current
	and parent directories with direct maps.

	( SR:8606351701 CR:JAGaf12506 )
	NFS enforces quotas only when the mount option "quota" is
	used.

	Resolution:
	Modified the mount_nfs man page to remove the statement that
	quota checking is done by default.

	( SR:8606355273 CR:JAGaf16027 )
	Netselect's nc_perror() outputs the error message for
	NC_BADLINE incorrectly. Netdir's netdir_perror() outputs an
	additional newline for all its errors.

	Resolution:
	Modified the affected error messages so the output is
	correct.

	( SR:8606356288 CR:JAGaf16994 )
	UDP only supports up to 32K for the transfer size. Some
	servers permit a 64K transfer size, which causes the client
	to hang during a write operation to an NFS mounted
	directory.

	Resolution:
	Set the default transfer size for NFS clients to 32K.

	PHNE_30086:
	( SR:8606324736 CR:JAGae87042 )
	The RPC client, loaded such that it is operating under
	memory pressure, may fail to allocate a STREAMS message
	block to request the TCP transport layer to complete an
	orderly connection close. This failure puts the RPC client
	into a state in which it is unable to reset or finish
	closing the connection and causes the connection to remain
	in the CLOSE_WAIT state.

	Resolution:
	RPC client TCP connection management is modified to ensure
	that a STREAMS message block to request TCP transport to
	initiate or complete an orderly TCP connection close will
	always be available.

	( SR:8606336931 CR:JAGae97978 )
	A race condition occurs between the RPC client TCP
	connection timeout and the TCP transport layer connection
	timeout. During a TCP connection attempt the RPC client may
	miss the indication from the TCP transport layer when a
	connection has been established.

	Resolution:
	The TCP connection timeout used by the RPC client is
	modified to match the default TCP connection timeout,
	instead of using the RPC call wait time.

	PHNE_29883:
	( SR:8606312940 CR:JAGae75747 )
	When the length of a symbolic link name exceeds 1024
	characters, the string that is passed from the function
	reading the symbolic link to the strlen function contains a
	-1. This causes the NFS client to crash.

	Resolution:
	Dependency on PHKL_30398.
	The length of the symbolic link name is checked to see if it
	exceeds 1024 characters. If it does, an error is returned.

	( SR:8606320583 CR:JAGae83065 )
	While AutoFS is unmounting a file system that is being
	managed by AutoFS, it is not able to recognize whether the
	file system was manually unmounted or not. This is because
	of improper synchronization in AutoFS.

	Resolution:
	AutoFS has been modified to provide the proper
	synchronization when the file systems are unmounted.

	( SR:8606330100 CR:JAGae91223 )
	An error message is returned while the rpcbind server is
	processing a disconnection message for a connection that has
	not yet been accepted. This error is not handled correctly.

	Resolution:
	The error returned while accepting a disconnected connection
	is now handled properly. The syslog.log message is no longer
	logged for that error.

	( SR:8606333242 CR:JAGae94337 )
	There is a problem with nested AutoFS maps.

	Resolution:
	The behavior of nested AutoFS maps has been modified.

	( SR:8606334605 CR:JAGae95685 )
	The 64-bit xdr_char() and xdr_u_char() routines do not check
	for encoding/decoding the XDR stream failures, and do not
	return an error. This may cause an application to core dump.

	Resolution:
	FALSE is now returned upon failure of encoding/decoding in
	the xdr_char() and xdr_u_char() routines.

	( SR:8606336578 CR:JAGae97630 )
	Inconsistent recommendations, coming from multiple
	references about the number of nfsd's configured to be run
	on an HP-UX NFS server, have caused confusion.

	Resolution:
	The default number of nfsd's configured to be run on an
	HP-UX NFS server has been modified in
	/usr/newconfig/etc/rc.config.d/nfsconf. The nfsd man page
	has also been modified to give a clearer description about
	choosing the number of nfsd's to be run on an HP-UX NFS
	server.

	PHNE_29783:
	( SR:8606347801 CR:JAGaf08623 )
	The rpc.ypupdated code does not function properly.

	Resolution:
	The rpc.ypupdated code has been modified to fix the problem.

	PHNE_29303:
	( SR:8606286517 CR:JAGae50456 )
	This product update contains minor enhancements required to
	enable the HP-UX Enhanced AutoFS product.

	Under heavy load, automountd may treat a duplicate mount
	request as a new mount request causing it to retry an NFS
	mount even though the file system was mounted earlier. This
	leads to a case where AutoFS mount points cannot be mounted.

	Resolution:
	Developed a new and improved duplicate request cache in
	libnsl (which the automountd in the HP-UX Enhanced AutoFS
	product uses) to eliminate existing problems.

	( SR:8606302457 CR:JAGae65816 )
	The client's rpc.lockd routine sends an initial request,
	then waits for a reply from the server. If no reply is
	received the client will begin retransmitting the request.
	The retransmissions are controlled by a timer, sending a
	request every other timer cycle. However, the first
	retransmission occurs at the beginning of the first timer
	cycle. The server treats this first retransmission as a new
	lock request because of the short time interval between the
	initial request and the first retransmission, which causes
	the client to hang.

	Resolution:
	Modified the rpc.lockd code to send the first retransmission
	request at the beginning of the second timer cycle.

	( SR:8606304146 CR:JAGae67490 )
	The pwchanger field of the trusted table is not cleared when
	the password is changed. This is due to the restriction
	imposed on the size of the XDR memory stream buffer. This
	problem only occurs when the admin group has more than 312
	members.

	Resolution:
	Increased the size of the XDR memory stream buffer.

	( SR:8606306059 CR:JAGae69107 )
	When an NIS+ user's keys are changed in the NIS+ tables, the
	keys are not updated in the NIS+ clients' keyserv daemon. As
	a result, there is a mismatch between the NIS+ credential
	tables, causing the NIS+ user to not be authenticated, and
	the NIS+ client to hang.

	Resolution:
	The NIS+ user is authenticated as "nobody" on the NIS+
	client, and an authentication failure is logged in the
	syslog.log file. This is documented in the newkey(1m) man
	page.

	( SR:8606306319 CR:JAGae69367 )
	When the /var filesystem becomes full, the
	/var/nis/NIS_COLD_START file is overwritten with a zero-byte
	file. This causes the NIS+ client authentication to fail.

	Resolution:
	The /var/nis/NIS_COLD_START file is no longer overwritten
	when there is no space left in the /var filesystem.

	( SR:8606312085 CR:JAGae74904 )
	When a symbolic link is attempted from a Linux NFS client to
	a file or directory that has a full path name length of more
	than 1024 characters, the NFS server receives a -1 in the
	name field. When passed to strlen this results in a system
	crash.

	Resolution:
	Added a test to see if the length of the symbolic link's
	name exceeds 1024 characters. If it does, an error is
	returned.

	( SR:8606313428 CR:JAGae76226 )
	If the /etc/hosts file has entries with IP addresses which
	are not in the proper dot notation format, some ONC commands
	give incorrect results.

	Resolution:
	Recognize incorrect IP addresses and return an appropriate
	error condition value.

	( SR:8606322456 CR:JAGae84924 )
	If the vers=<version number> option of the NFS mount command
	is specified, then the mount command is expected to mount
	the requested version. If this version is not supported by
	the NFS server, then the mount command should fail. If the
	user does not provide a version number with the NFS mount
	command, a mount is attempted with the highest available
	version. If the highest version is not available it will
	attempt to perform a mount with a lower version. Currently,
	the NFS mount command uses this approach, even when a
	version number is specified.

	Resolution:
	Avoid negotiations with the NFS server for lower mount
	versions when the mount command specifies the
	vers=<version number> option, and return a failure if the
	specified version is not available.

	( SR:8606335982 CR:JAGae97035 )
	This product update contains minor enhancements required to
	enable the HP-UX Enhanced AutoFS product.

	Resolution:
	AutoFS has been modified to operate in enhanced mode when
	the HP-UX Enhanced AutoFS product is installed. In addition,
	the nfs.client script has been modified to work with HP-UX
	Enhanced AutoFS. The AutoFS man pages have been modified to
	include information for using HP-UX Enhanced AutoFS.

	( SR:8606332784 CR:JAGae93899 )
	The panic occurs because the nfs3readdirplus() routine does
	not check for unaligned buffers. This causes an incorrect
	type value to be passed to the makenfs3node() routine, which
	crashes the system.

	Resolution:
	Modified the nfs3readdirplus() and xdr_getdirpluslist()
	routines to align the XDR buffer.

	PHNE_29211:
	( SR:8606317529 CR:JAGae80090 )
	Connection-oriented RPC packets are not being decoded
	effectively during network delays.

	Resolution:
	The non-blocking I/O feature is being provided to improve
	the performance of connection-oriented RPC transports during
	network delays.

	( SR:8606320560 CR:JAGae83042 )
	The rpc.mountd code returns an incorrect error message.

	Resolution:
	The rpc.mountd code has been modified to fix the error
	message.

	( SR:8606317535 CR:JAGae80096 )
	Connection-oriented RPC packets are not being decoded
	effectively during network delays.

	Resolution:
	The non-blocking I/O feature is being provided to improve
	the performance of connection-oriented RPC servers during
	network delays.

	( SR:8606337943 CR:JAGae98946 )
	If "Error in RPC subsystem" messages are displayed or logged
	for NIS+ related commands or applications that use NIS+
	API's, a possible cause is that the default maximum RPC
	record size for NIS+ (9000 bytes) is too small. Examples of
	NIS+ commands that could be affected are nistbladm,
	nisgrpadm, and nisaddent. NIS+ API's that could be affected
	include nis_add() and nis_modify().

	Resolution:
	Added the rpc.nisd -z option to set the maximum record size
	needed by the application. Some experimentation may be
	required to determine the optimal value for a particular
	application. The NIS+ server needs to be restarted after
	changing this value for it to take effect. Please see the
	rpc.nisd man page for details on using the -z option.

	PHNE_28983:
	( SR:8606220736 CR:JAGad89872 )
	After an NIS+ user is deleted, its user ID is reused for a
	different user. The shadow field for each user is set to age
	the password such that the password must be changed at the
	first login, which failed. This occurs due to internal
	caching within the rpc.nispasswdd daemon. The cache contains
	credential information for the deleted user.

	Resolution:
	Added functionality to determine if the cache is obsolete,
	and if so, remove the obsolete cache entry.

	( SR:8606278781 CR:JAGae42837 )
	The automount daemon is getting saturated with mount
	requests, and is not able to handle duplicate requests
	properly. The daemon is considering each duplicate request
	as a new request, and this new request creates a mount point
	without a proper state which allows it to be unmounted.

	Resolution:
	Modified the automount daemon to properly handle duplicate
	mount requests.

	( SR:8606294191 CR:JAGae57931 )
	When a mount request for a directory is issued, AutoFS
	increments a reference count. The reference count must be
	decremented when a mount request fails, but AutoFS is not
	doing so. When a mount request for the same directory
	succeeds, AutoFS is unable to unmount those directories
	after the unmount timer expires. So directories mounted with
	AutoFS will remain mounted and will never be unmounted by
	AutoFS.

	Resolution:
	Fixed AutoFS to maintain a correct reference count, even
	when a mount request fails, so that directories will always
	be unmounted properly.

	( SR:8606294387 CR:JAGae58084 )
	Under heavy load, automountd is not removing stale entries
	when the unmount request list runs out of memory.
	Automountd is not able to process unmount requests and
	AutoFS mounted file systems never get unmounted.

	Resolution:
	Modified automountd to correctly remove stale entries from
	the unmount request list.

	( SR:8606294761 CR:JAGae58456 )
	Re-exporting a large number of entries in the /etc/exports
	file takes almost twice as much time as the original export.

	Resolution:
	Modified the exportfs code so that the re-exporting time is
	now approximately the same as the original export.

	( SR:8606295723 CR:JAGae59388 )
	Due to a Makefile problem, pcnfsd is only allowing NFS
	access for PC users with a default shell ending with "sh".

	Resolution:
	Modified the Makefile to verify NFS access from a PC by
	checking the /etc/shells file.

	( SR:8606296110 CR:JAGae59732 )
	The nsswitch.conf man page implies that the values in the
	/etc/nsswitch.hp_defaults file are the default values.
	However, this file is only for 10.20 compatibility and does
	not contain the default values.

	Resolution:
	Updated the nsswitch.conf man page with the correct default
	values.

	( SR:8606296698 CR:JAGae60267 )
	The NFS Server hangs due to a deadlock condition between the
	NFS Client and the buffer cache with NFS loopback mounts.
	This occurs while flushing buffers containing removed NFS
	files. The NFS Server attempts to hold a semaphore lock that
	is already being held, resulting in the deadlock.

	Resolution:
	Buffers containing removed NFS files are flushed whenever a
	file is removed or its last reference is closed.

	( SR:8606296789 CR:JAGae60355 )
	The panic from the ls command occurs because
	nfs3readdirplus() does not check for unaligned buffers on
	64-bit systems. This causes an incorrect type value to be
	passed to makenfs3node(), which crashes the system.

	Resolution:
	Modified nfs3readdirplus() to handle alignment on 64-bit
	systems. Also modified makenfs3node() to verify that the
	type value is in the proper range.

	( SR:8606297163 CR:JAGae60682 )
	While trying to open a file in an NFSv3 mounted file system
	from a Solaris NFS server with O_EXCL and the setgid bit of
	the parent directory set, the last access time and last
	modified time attributes are not updated properly and
	changing the group ownership fails. This leaves a file with
	no access permissions on the server.

	Resolution:
	Update the last access time and the last modified time
	attributes with one SETATTR call, and update the group ID
	with a separate SETATTR call.

	( SR:8606297688 CR:JAGae61190 )
	All file systems being managed by AutoFS are not ge