From owner-freebsd-questions  Wed Apr  2 02:08:12 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA20343
          for questions-outgoing; Wed, 2 Apr 1997 02:08:12 -0800 (PST)
Received: from caliban.dihelix.com (caliban.mrtc.org [199.4.33.251])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA20293;
          Wed, 2 Apr 1997 02:07:59 -0800 (PST)
Received: (from langfod@localhost) by caliban.dihelix.com (8.8.5/8.8.3) id AAA23069; Wed, 2 Apr 1997 00:07:57 -1000 (HST)
Message-Id: <199704021007.AAA23069@caliban.dihelix.com>
Subject: why does passwd(1) et al remake /etc/passwd?
To: questions@freebsd.org
Date: Wed, 2 Apr 1997 00:07:57 -1000 (HST)
Cc: isp@freebsd.org
From: "David Langford" <langfod@dihelix.com>
X-blank-line: This space intentionaly left blank.
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



Since pwd_mkdb requires a flag to rebuild the V7 passwd file
I was surprized to find that the passwd(1) program creates
the /etc/passwd file after I so carefully deleted it.

Just noticed that vipw does this also. 

I dont supposed we could hide a system flag somewhere that say
"DONT create a V7 passwd file unless I say so twice"?

Off to source code land and crontab rm'ing.

P.s. if you are wondering we have this problem of users grabbing
     the passwd list for spamming purposes.

Thanks,

-David Langford
 langfod@dihelix.com