From owner-freebsd-stable@FreeBSD.ORG Fri Jun 22 22:44:28 2012 Return-Path: Delivered-To: Freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 304BB106566B; Fri, 22 Jun 2012 22:44:28 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id E2AAF8FC0A; Fri, 22 Jun 2012 22:44:27 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.31]) by ltcfislmsgpa02.fnfis.com (8.14.4/8.14.4) with ESMTP id q5MMiR6U025790 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 22 Jun 2012 17:44:27 -0500 Received: from [10.0.0.105] (10.14.152.61) by smtp.fisglobal.com (10.132.206.31) with Microsoft SMTP Server (TLS) id 14.2.283.3; Fri, 22 Jun 2012 17:44:26 -0500 MIME-Version: 1.0 (Apple Message framework v1257) From: Devin Teske In-Reply-To: Date: Fri, 22 Jun 2012 15:44:22 -0700 Message-ID: <082B913F-3A95-48C1-8B5A-BD220937748C@fisglobal.com> References: <2322BE6D-24A8-4F4A-84B2-4DFE33BCA65B@fisglobal.com> <4FE3EB9D.9070509@fuzzwad.org> <4FE419CD.60708@rdtc.ru> <4FE4245C.3040806@rdtc.ru> <90361FE2-2298-48E5-B8B6-2BA704781098@fisglobal.com> <4FE431C0.8040509@rdtc.ru> <006001cd5072$84247cd0$8c6d7670$@milos.co.za> To: Devin Teske X-Mailer: Apple Mail (2.1257) X-Originating-IP: [10.14.152.61] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855, 1.0.260, 0.0.0000 definitions=2012-06-22_06:2012-06-22, 2012-06-22, 1970-01-01 signatures=0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Clayton Milos , Freebsd-stable@freebsd.org Subject: Re: [CFT] Need Testers for: sysutils/bsdconfig X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Devin Teske List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2012 22:44:28 -0000 On Jun 22, 2012, at 3:32 PM, Devin Teske wrote: >=20 > On Jun 22, 2012, at 5:27 AM, Clayton Milos wrote: >=20 >>=20 >> When selecting user account expiry the calendar starts at 1 January 1970= . I >> understand that this is when Unix time started but it would be nice for = it >> to start from the current date. >>=20 >=20 > This was on-purpose because there is a discrepancy in passwd(5) manual re= garding what a value of zero (0) means for these fields. >=20 > From passwd(5): >=20 > The change field is the number of seconds from the epoch, UTC, until= the > password for the account must be changed. This field may be left em= pty > to turn off the password aging feature. >=20 > Nowhere in the manual does it say that zero is a synonym to being left em= pty. >=20 And yet, this is how the system treats zero (was my complaint). The user root (and toor, and several other system users) come with a defaul= t value of zero for this field. If zero was treated according to the manual, then root would be disabled by= default. But that's clearly not the case in a default installation which h= as a value of zero. So, when you're using bsdconfig to view an existing user that has a value o= f zero, you will notice that the default calendar date/time that is chosen = corresponds to "zero seconds from the epoch, UTC", despite the fact that I = know (and you know) that zero is synonymous with NULL. So I'm a fan of updating the man page and when that is done, I am happy to = change bsdconfig to treat zero as-such. But right now I wanted to stay true= to the manual (which plainly states that any non-NULL value is treated as = seconds from the epoch). --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.