From owner-freebsd-hackers  Thu Dec  4 16:29:00 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id QAA18786
          for hackers-outgoing; Thu, 4 Dec 1997 16:29:00 -0800 (PST)
          (envelope-from owner-freebsd-hackers)
Received: from ve7tcp.ampr.org (root@ve7tcp.ampr.org [198.161.92.132])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA18778
          for <freebsd-hackers@freebsd.org>; Thu, 4 Dec 1997 16:28:56 -0800 (PST)
          (envelope-from lyndon@ve7tcp.ampr.org)
Received: from localhost.ampr.org (lyndon@localhost.ampr.org [127.0.0.1])
          by ve7tcp.ampr.org (8.8.5/8.8.4) with SMTP
	  id RAA00374; Thu, 4 Dec 1997 17:28:40 -0700 (MST)
Message-Id: <199712050028.RAA00374@ve7tcp.ampr.org>
X-Authentication-Warning: ve7tcp.ampr.org: lyndon@localhost.ampr.org [127.0.0.1] didn't use HELO protocol
X-Mailer: exmh version 2.0gamma 1/27/96
To: jbryant@unix.tfs.net
cc: freebsd-hackers@freebsd.org
Subject: Re: Anybody heard of fgetwpent() and putpwent()? 
In-reply-to: Your message of "Thu, 04 Dec 1997 17:26:54 CST."
             <199712042326.RAA27270@unix.tfs.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 04 Dec 1997 17:28:40 -0700
From: Lyndon Nerenberg <lyndon@ve7tcp.ampr.org>
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


> >      PUTPWENT(3C)                DYNIX/ptx                PUTPWENT(3C)
> i guess it was for people who cannot read passwd(5)...  

No, it's for *programs* that can't read passwd(5) :-)

What makes it useless is that there's no C API for locking the password
file(s), installing the new password file, etc.

--lyndon