From owner-freebsd-current@freebsd.org Fri Aug 21 13:48:30 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 62EEA9BF261 for ; Fri, 21 Aug 2015 13:48:30 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 20EDCCAD for ; Fri, 21 Aug 2015 13:48:29 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtp (envelope-from ) id <1ZSmg8-003sAj-QJ>; Fri, 21 Aug 2015 15:48:20 +0200 Received: from p578a69f9.dip0.t-ipconnect.de ([87.138.105.249] helo=freyja.zeit4.iv.bundesimmobilien.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtpsa (envelope-from ) id <1ZSmg8-0002fJ-I0>; Fri, 21 Aug 2015 15:48:20 +0200 Date: Fri, 21 Aug 2015 15:48:13 +0200 From: "O. Hartmann" To: freebsd-current Subject: pw: pw: Invalid min_uid: '2000'; ignoring Message-ID: <20150821154813.06d84fde@freyja.zeit4.iv.bundesimmobilien.de> Organization: FU Berlin X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Originating-IP: 87.138.105.249 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 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: Fri, 21 Aug 2015 13:48:30 -0000 Setting up on NanoBSD vi pw command an initial /etc/pw.conf (usermod -D), I use amongst other options also: -u 2000,32767 -i 2000,32767 which finally and successfully expands to [...] # Range of valid default user ids minuid = 2000 maxuid = 32767 # Range of valid default group ids mingid = 2000 maxgid = 32767 [...] as expected. Adding or changing now a user within such an environment gives me pw: Invalid min_uid: '2000'; ignoring pw: Invalid max_uid: '32767'; ignoring pw: Invalid min_gid: '2000'; ignoring pw: Invalid max_gid: '32767'; ignoring which is obviously not correct. Since pw has undergone severe maintenance, I consider this a bug. Regards, Oliver