From owner-freebsd-questions Wed Nov 21 9: 8:28 2001 Delivered-To: freebsd-questions@freebsd.org Received: from dc.cis.okstate.edu (dc.cis.okstate.edu [139.78.100.219]) by hub.freebsd.org (Postfix) with ESMTP id 82EF537B418 for ; Wed, 21 Nov 2001 09:08:26 -0800 (PST) Received: from dc.cis.okstate.edu (localhost.cis.okstate.edu [127.0.0.1]) by dc.cis.okstate.edu (8.11.3/8.11.3) with ESMTP id fALH8Pa20266 for ; Wed, 21 Nov 2001 11:08:25 -0600 (CST) (envelope-from martin@dc.cis.okstate.edu) Message-Id: <200111211708.fALH8Pa20266@dc.cis.okstate.edu> To: freebsd-questions@freebsd.org Subject: Password Aging and Classes Date: Wed, 21 Nov 2001 11:08:25 -0600 From: "Martin G. McCormick" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I created our user accounts on a FreeBSD system without assigning any of them to a particular class. If I want to use password aging, do I need to put everyone whose password needs to be renewed regularly in a class for this or do the default entries in /etc/login.conf cover classless accounts? There are only 12 or 13 accounts so moving all of them to a class wouldn't be that difficult but I want to enable password aging painlessly and hopefully without surprises such as people not being able to log in at all. The surprise factor is why I didn't just try it and see. Martin McCormick WB5AGZ Stillwater, OK OSU Center for Computing and Information Services Network Operations Group To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message