Patch Name: PHNE_20324

Patch Description: s700_800 10.26 rpc.statd(1M), rpc.lockd(1M) logging

Creation Date: 99/10/28

Post Date:  99/11/04

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

Products: N/A

Filesets:
	NFS.NFS-CORE NFS.NFS-ENG-A-MAN

Automatic Reboot?: No

Status: General Release

Critical: No

Path Name: /hp-ux_patches/s700_800/10.X/PHNE_20324

Symptoms:
	PHNE_20324:
	warning message in the swagent.log file when installing
	the patch bundle at coldinstall time.

	PHNE_17824:
	rpc.statd(1M) and rpc.lockd(1M) are logging too many
	messages.

Defect Description:
	PHNE_20324:
	Repackaged to allow this patch to be part of a patch bundle.
	No changes made to the binaries.  The changes are only made
	in the installation scripts.

	PHNE_17824:
	rpc.statd(1M) and rpc.lockd(1M) log messages even if -l
	option is not specified. They are logging too many messages,
	which should be logged only with debug turned on.


	Resolution:
	Modify man page to specify that logging is on even without
	-l option.
	Modify the code not to log debug messages.

SR:
	0000000000

Patch Files:
	/usr/sbin/rpc.lockd
	/usr/sbin/rpc.statd
	/usr/share/man/man1m.Z/lockd.1m
	/usr/share/man/man1m.Z/statd.1m

what(1) Output:
	/usr/sbin/rpc.lockd:
		1999/03/23 Hewlett-Packard HP-UX 10.26 TOS [ ic5bo -
			 DAV17 ]
		rpc.lockd:      $Revision: 1.36.110.9 $ $Date: 94/10
			/27 13:12:18 $
		prot_pnlm.c 1.rb5 86/09/24 Copyr 1986 Sun Micro
		prot_msg.c 1.3.rb 86/09/24 Copyr 1984 Sun Micro
		prot_proc.c 1.9.rb 86/09/24 Copyr 1986 Sun Micro
		prot_freeall.c  1.1 88/08/05 NFSSRC4.0 1.3 88/02/07
			Copyr 1984 Sun Micro
		prot_share.c    1.1 88/08/05 NFSSRC4.0 1.4 88/08/04
			Copyr 1984 Sun Micro
		99/03/09 services/NFS/cmds/usr.etc/rpc.lockd/lockd_s
			ec.c, hpux, hpux_10.26, ic5bo Revision 1.5 P
			ATCH_10.26 (PHNE_17824)
		RB2
	/usr/sbin/rpc.statd:
		1999/03/23 Hewlett-Packard HP-UX 10.26 TOS [ ic5bo -
			 DAV17 ]
		rpc.statd:      $Revision: 1.18.110.9 $ $Date: 94/10
			/20 17:31:25 $
		sm_proc.c : $Revision: 1.11.114.3 $ $Date: 96/03/28
			17:25:46 $ PHNE_6444
		99/03/09 services/NFS/cmds/usr.etc/rpc.lockd/lockd_s
			ec.c, hpux, hpux_10.26, ic5bo Revision 1.5 P
			ATCH_10.26 (PHNE_17824)
		RB2
	/usr/share/man/man1m.Z/lockd.1m:
		None
	/usr/share/man/man1m.Z/statd.1m:
		None

cksum(1) Output:
	4133997670 98304 /usr/sbin/rpc.lockd
	1324084412 49152 /usr/sbin/rpc.statd
	453860304 3011 /usr/share/man/man1m.Z/lockd.1m
	2585470998 2268 /usr/share/man/man1m.Z/statd.1m

Patch Conflicts: None

Patch Dependencies: None

Hardware Dependencies: None

Other Dependencies: None

Supersedes:
	PHNE_17824

Equivalent Patches: None

Patch Package Size: 210 KBytes

Installation Instructions:
	Please review all instructions and the Hewlett-Packard
	SupportLine User Guide or your Hewlett-Packard support terms
	and conditions for precautions, scope of license,
	restrictions, and, limitation of liability and warranties,
	before installing this patch.
	------------------------------------------------------------
	1. Back up your system before installing a patch.

	2. Login as root.

	3. Copy the patch to the /tmp directory.

	4. Move to the /tmp directory and unshar the patch:

		cd /tmp
		sh PHNE_20324

	5a. For a standalone system, run swinstall to install the
	    patch:

		swinstall -x autoreboot=true -x match_target=true \
			-s /tmp/PHNE_20324.depot

	By default swinstall will archive the original software in
	/var/adm/sw/patch/PHNE_20324.  If you do not wish to retain a
	copy of the original software, you can create an empty file
	named /var/adm/sw/patch/PATCH_NOSAVE.

	WARNING: If this file exists when a patch is installed, the
	         patch cannot be deinstalled.  Please be careful
		 when using this feature.

	It is recommended that you move the PHNE_20324.text file to
	/var/adm/sw/patch for future reference.

	To put this patch on a magnetic tape and install from the
	tape drive, use the command:

		dd if=/tmp/PHNE_20324.depot of=/dev/rmt/0m bs=2k

Special Installation Instructions:
	The NFS Server and Client will be stopped and restarted
	when installing this patch.  In a busy NFS evironment this
	may not occur properly and the system will need to be
	rebooted to correctly restart NFS.