From gil@cortex.gc2.kloepfer.org  Sat May 24 21:50:18 1997
Received: from cortex.gc2.kloepfer.org (cortex.gc2.kloepfer.org [206.225.39.4])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA07899
          for <FreeBSD-gnats-submit@freebsd.org>; Sat, 24 May 1997 21:50:17 -0700 (PDT)
Received: (from gil@localhost)
	by cortex.gc2.kloepfer.org (8.8.5/8.8.5) id XAA00323;
	Sat, 24 May 1997 23:50:07 -0500 (CDT)
Message-Id: <199705250450.XAA00323@cortex.gc2.kloepfer.org>
Date: Sat, 24 May 1997 23:50:07 -0500 (CDT)
From: ngk@gc2.kloepfer.org
Reply-To: ngk@gc2.kloepfer.org
To: FreeBSD-gnats-submit@freebsd.org
Cc: ngk@gc2.kloepfer.org
Subject: /etc/login.conf needs a default
X-Send-Pr-Version: 3.2

>Number:         3677
>Category:       conf
>Synopsis:       login.conf needs a default or baseline file
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Sat May 24 22:00:01 PDT 1997
>Closed-Date:    Sun May 25 19:14:06 EST 1997
>Last-Modified:  Sun May 25 19:15:29 EST 1997
>Originator:     Gil Kloepfer Jr.
>Release:        FreeBSD 2.2.2-RELEASE i386
>Organization:
None
>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.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: davidn 
State-Changed-When: Sun May 25 19:14:06 EST 1997 
State-Changed-Why:  
This has since been fixed in the etc/Makefile 'distribution' target. 
The omission of login.conf from the release was in error. 
>Unformatted:
