Date: Sat, 24 May 1997 23:50:07 -0500 (CDT) From: ngk@gc2.kloepfer.org To: FreeBSD-gnats-submit@FreeBSD.ORG Cc: ngk@gc2.kloepfer.org Subject: conf/3677: /etc/login.conf needs a default Message-ID: <199705250450.XAA00323@cortex.gc2.kloepfer.org> Resent-Message-ID: <199705250500.WAA08326@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 3677 >Category: conf >Synopsis: login.conf needs a default or baseline file >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sat May 24 22:00:01 PDT 1997 >Last-Modified: >Originator: Gil Kloepfer Jr. >Organization: None >Release: FreeBSD 2.2.2-RELEASE i386 >Environment: FreeBSD 2.2.2-Release, all platforms >Description: After installation, there is no /etc/login.conf file, so when login or inetd accesses the root class, a syslog message is displayed: May 24 23:18:13 host login: login_getclass: unknown class 'root' May 24 23:25:03 host inetd[253]: login_getclass: unknown class 'root' >How-To-Repeat: Install FreeBSD 2.2.2-Release >Fix: The login.conf file has a lot of options and defaults. It probably should exist with the default values for the default class, and a set of relatively secure values for the root class. This would make it easier for someone first dealing with the file to have a template to work with. It would also eliminate the messages noted above when the system is first built. The syslog messages are NOT a bug, they're probably a good way to alert a system administrator that the /etc/login.conf doesn't exist. >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705250450.XAA00323>