From owner-freebsd-current@freebsd.org Sat Jul 21 23:49:43 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D4573103045F for ; Sat, 21 Jul 2018 23:49:43 +0000 (UTC) (envelope-from herbert@gojira.at) Received: from mail.bsd4all.net (mail.bsd4all.net [144.76.30.122]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.bsd4all.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 69ACC7CB25 for ; Sat, 21 Jul 2018 23:49:43 +0000 (UTC) (envelope-from herbert@gojira.at) Date: Sun, 22 Jul 2018 01:49:41 +0200 From: "Herbert J. Skuhra" To: freebsd-current@freebsd.org Subject: Re: ntpd as ntpd user question Message-ID: <20180721234941.2ojf76kxxqfhnys7@mail.bsd4all.net> References: <5b90c49f-4616-9ef7-28a1-6445137245ef@nomadlogic.org> <1532191655.1344.80.camel@freebsd.org> <4b7acbd2-0230-345c-4370-24a72d0b492a@nomadlogic.org> <1532193285.1344.83.camel@freebsd.org> <20180721174722.GA40167@www.zefox.net> <1532196850.1344.87.camel@freebsd.org> <20180721220925.GA40238@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180721220925.GA40238@www.zefox.net> User-Agent: NeoMutt/20180716 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jul 2018 23:49:44 -0000 On Sat, Jul 21, 2018 at 03:09:26PM -0700, bob prohaska wrote: > On Sat, Jul 21, 2018 at 12:14:10PM -0600, Ian Lepore wrote: > > > > I can't see any way that installkernel would lead to the complaint > > about the ntpd user not existing; that check is tied to the > > installworld target. > > > My mistake. I was sleepy and in a hurry. The error message was in installworld > and my attempt to adduser ntpd concluded with an error: > Locked : yes > OK? (yes/no): yes > pw: Bad id 'ntpd': invalid > adduser: ERROR: There was an error adding user (ntpd). > On reboot the old ntpd set the clock and I thought all was well. > > The failure is a little surprising, is ntpd a reserved name? Why? You obviously entered the string "ntpd" instead of an integer when asked for the uid!? > The machine is re-running buildworld/installworld from a clean start, > so presumably it'll halt over the same error again. When that happens, > what's the simplest way to recover? Mergemaster is a big hammer, something > less comprehensive might suffice, even manual editing of files. In this case 'mergemaster -p' is enough. -- Herbert