From owner-freebsd-questions@FreeBSD.ORG Tue Apr 29 13:32:05 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D6CA237B401 for ; Tue, 29 Apr 2003 13:32:05 -0700 (PDT) Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2366443FA3 for ; Tue, 29 Apr 2003 13:32:01 -0700 (PDT) (envelope-from freebsd-questions-local@be-well.no-ip.com) Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com[24.147.188.198]) by rwcrmhc53.attbi.com (rwcrmhc53) with ESMTP id <2003042920320005300f74q2e>; Tue, 29 Apr 2003 20:32:00 +0000 Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [24.147.188.198] (may be forged)) by be-well.ilk.org (8.12.9/8.12.7) with ESMTP id h3TKVxPN025173; Tue, 29 Apr 2003 16:31:59 -0400 (EDT) (envelope-from freebsd-questions-local@be-well.no-ip.com) Received: (from lowell@localhost) by be-well.ilk.org (8.12.9/8.12.6/Submit) id h3TKVwZj025170; Tue, 29 Apr 2003 16:31:58 -0400 (EDT) X-Authentication-Warning: be-well.ilk.org: lowell set sender to freebsd-questions-local@be-well.ilk.org using -f Sender: lowell@be-well.no-ip.com To: "Jud" References: <1051552552.73f8f180jud@myrealbox.com> From: Lowell Gilbert Date: 29 Apr 2003 16:31:58 -0400 In-Reply-To: <1051552552.73f8f180jud@myrealbox.com> Message-ID: <4465ox59kx.fsf@be-well.ilk.org> Lines: 9 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-questions@freebsd.org Subject: Re: How to Regain 'Lost' User? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2003 20:32:06 -0000 "Jud" writes: > Was puttering along changing shells from sh to zsh for root and user, using chpass -s. This went off without a hitch for root. Then unaccountably (typo?), when trying the same for user, I received a response that the user was unknown. Sounds like you're running some week-or-so-old -CURRENT. The short-term solution is to rebuild the password database. If you're running -CURRENT, remember to keep up with the mailing list.