topic Re: PWGRD Process. in Operating System - HP-UX

PWGRD Process.

brian_31 — Thu, 28 Mar 2002 17:18:16 GMT

Hi Team:

Are there any known issues running pwgrd process. Is it recommended to turn it off?? Environment 11.0, nis

Thanks
Brian.

Re: PWGRD Process.

S.K. Chan — Thu, 28 Mar 2002 17:23:33 GMT

I got mine turn off because occasionally it eats up my CPU resources.. until I have time to patch it I can live without it for the time being.

# /sbin/init.d/pwgr stop

Edit /etc/rc.config.d/pwgr
PWGR=0

BTW the patch you need is PHCO_24586, it might be superseeded already.

Re: PWGRD Process.

brian_31 — Thu, 28 Mar 2002 17:31:16 GMT

Hi:

Here i do not have pwgrd process occupying the cpu. But i was wondering what could be the other issues with it related to X-Motif apps published thru the pc thru x emulation in NIS Environment?

Thanks
Brian.

Re: PWGRD Process.

A. Clay Stephenson — Thu, 28 Mar 2002 17:31:48 GMT

Hi Brian:

I run it with NIS with no problems. You do need to make sure that PHCO_24586 and PHCO_25527 are installed. The only time I I have any problem was in a thread where /var/tmp filled up (not pwgrd's fault) and group lookups started failing. The cause was far from obvious but cleaning up /var/tmp and stop/start pwgrd fixed it. Surprising the user lookup's were fine only the group lookups failed.

Re: PWGRD Process.

Giri Sekar. — Thu, 28 Mar 2002 17:42:13 GMT

Hi:

The group names must be restricted to 8 characters when using pwgrd. Also follow Clay's Patches.

Thanks
Giri Sekar.

Re: PWGRD Process.

S.K. Chan — Thu, 28 Mar 2002 17:46:40 GMT

Apart from what Clay's has mentioned and /var/spool/sockets/pwgr filling up (more housekeeping work), I do not know of any other issues related to X.

Re: PWGRD Process.

Jeffrey S. Sims — Thu, 28 Mar 2002 18:37:36 GMT

Brian,

The only thing I could find was a document on building a bastion host with hpux 11.0 a paragraph read

pwgrd is a password and group caching daemon. Since we have a very small password and group file it is unnecessary. Also, a little detective work with lsof and tusc (Trace Unix System Calls) [10] shows us that it listens on a Unix domain socket for client requests, and we don't want to allow command channels like that to processes running as root, so we have additional incentive to disable it:

Hope that sheds a little light on your question. If not, well it gave me something else to do for 20 minutes. Good luck.