From owner-freebsd-config Sat Apr 25 01:48:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28027 for freebsd-config-outgoing; Sat, 25 Apr 1998 01:48:04 -0700 (PDT) (envelope-from owner-freebsd-config@FreeBSD.ORG) Received: from const. (willow21.verinet.com [199.45.181.53]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA27963 for ; Sat, 25 Apr 1998 01:47:58 -0700 (PDT) (envelope-from allenc@verinet.com) Received: (from allenc@localhost) by const. (8.8.8/8.8.8) id CAA19253 for config@FreeBSD.ORG; Sat, 25 Apr 1998 02:49:31 -0600 (MDT) (envelope-from allenc) Date: Sat, 25 Apr 1998 02:49:31 -0600 (MDT) From: allen campbell Message-Id: <199804250849.CAA19253@const.> To: config@FreeBSD.ORG Subject: Re: Config Databases In-Reply-To: <19980424011635.26988@nuxi.com> Sender: owner-freebsd-config@FreeBSD.ORG Precedence: bulk > > Not directly related, but... > > > [ previous entries snipped ] > > # << The following errors have been detected: >> > > # << Missing login shell >> > > Not an error, defaults to /bin/sh > > > # << The following errors have been detected: >> > > # << Non-unique UID value >> > > # << The following entry has been ignored >> > > In my book, not an error. > I have two accounts for myself with the same UID -- my usual one with a > fancy shell, and a backup account with /bin/sh incase something happened > to the NFS mounted /usr/local > > So this may beg the question, if there needs to be the ability to express > a policy to determine what constitutes an error. Bad examples perhaps. The missing shell might constitute a warning, which could be accommodated also. Are you sure about that default to /bin/sh? The code from getpwent.c looks like if ((s = strsep(&result, ":")) == NULL) return 0; /* shell */ if(!(pw->pw_fields & _PWF_SHELL)) { pw->pw_shell = s; pw->pw_fields |= _PWF_SHELL; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-config" in the body of the message