From owner-freebsd-questions  Fri Jan 24 03:41:47 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id DAA23014
          for questions-outgoing; Fri, 24 Jan 1997 03:41:47 -0800 (PST)
Received: from mail.EUnet.hu (www.eunet.hu [193.225.28.100])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA22992
          for <freebsd-questions@freebsd.org>; Fri, 24 Jan 1997 03:41:38 -0800 (PST)
Received: by mail.EUnet.hu, id MAA04201; Fri, 24 Jan 1997 12:41:33 +0100
Received: (from zgabor@localhost) by CoDe.hu (8.7.5/8.7.3) id LAA00633 for freebsd-questions@freebsd.org; Fri, 24 Jan 1997 11:29:08 +0100 (MET)
From: Zahemszky Gabor <zgabor@CoDe.hu>
Message-Id: <199701241029.LAA00633@CoDe.hu>
Subject: Re: Delete User
To: freebsd-questions@freebsd.org (FreeBSD questions)
Date: Fri, 24 Jan 1997 11:29:07 +0100 (MET)
In-Reply-To: <199701231711.KAA00974@seagull.rtd.com> from Don Yuniskis at "Jan 23, 97 10:11:00 am"
X-Mailer: ELM [version 2.4ME+ PL11 (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

> I think the vipw method is preferable since it does all the file locking 
> for you.
> 
> I recommend *not* removing the entry from /etc/passwd but, rather, filling
> the password field with ``*'' to effectively prohibit the user from using
> the account.  This allows /etc/passwd to serve as an informal record of
> current AND PREVIOUS login id's.  On a small system, it's great.  On

And what about her/his ~/.rhosts file?  So delete this file, or deny the use
of it with rlogind/rshd's -l option in /etc/inetd.conf.  Or deny it at all.

Gabor