From marcs@alive.znep.com  Sat Nov  7 01:44:46 1998
Received: from alive.znep.com (207-178-54-226.go2net.com [207.178.54.226])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA14625
          for <FreeBSD-gnats-submit@freebsd.org>; Sat, 7 Nov 1998 01:44:44 -0800 (PST)
          (envelope-from marcs@alive.znep.com)
Received: (from marcs@localhost)
	by alive.znep.com (8.9.1/8.9.1) id BAA18272;
	Sat, 7 Nov 1998 01:40:32 -0800 (PST)
	(envelope-from marcs)
Message-Id: <199811070940.BAA18272@alive.znep.com>
Date: Sat, 7 Nov 1998 01:40:32 -0800 (PST)
From: marcs@znep.com
Reply-To: marcs@znep.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: login.conf should not set manpath
X-Send-Pr-Version: 3.2

>Number:         8587
>Category:       conf
>Synopsis:       login.conf should not set manpath
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Nov  7 01:50:00 PST 1998
>Closed-Date:    Sun Dec 27 16:02:39 PST 1998
>Last-Modified:  Sun Dec 27 16:03:24 PST 1998
>Originator:     Marc Slemko
>Release:        FreeBSD 3.0-CURRENT i386
>Organization:
>Environment:

FreeBSD alive.znep.com 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Fri Nov  6 23:10:01 PST 1998     marcs@alive.znep.com:/usr/src/sys/compile/ALIVE  i386

Appears to have been around for a long time, possibly even before 
login.conf.

>Description:

login.conf sets a manpath.  The default manpath doesn't include
/usr/X11R6/man, so things don't work right.  I shouldn't have to mess
with activating a special class just for X users, etc.

>How-To-Repeat:

marcs@alive:~$ echo $MANPATH
/usr/share/man:/usr/local/man
marcs@alive:~$ man xrdb
No manual entry for xrdb
marcs@alive:~$ unset MANPATH
marcs@alive:~$ man xrdb 
(now it works right)

>Fix:
	
Remove the manpath setting from /etc/login.conf.  Then man will use
the manpath program to figure out the manpath, which actually uses
the manpath.config file, etc.  Let manpath do its job.
>Release-Note:
>Audit-Trail:

From: skynyrd@opus.cts.cwu.edu
To: FreeBSD-gnats-submit@FreeBSD.org, marcs@znep.com, skynyrd@opus.cts.cwu.edu
Cc:  Subject: Re: conf/8587: login.conf should not set manpath
Date: Fri, 25 Dec 1998 09:09:01 -0800 (PST)

 I think you are right.  When I was looking at this I also discovered that you cannot simply 
 comment out the manpath field in login.conf (I eliminated login.conf.db just to be sure it 
 wasn't overriding login.conf.)  After making sure that MANPATH wasn't coming from 
 anyplace else, I finally removed the commented out line altogether and MANPATH went
 away!
 
 According to getcap(3), lines beginning with '#' are comments and are to be ignored.
 I need to look at the login_cap stuff to see if they are calling getcap to track down this
 bug.
 
 I would like normal default behavior to be as you request, but also leave a commented-out
 manpath in the login.conf to remind sites that it can be customized that way - which 
 is more appropriate than /etc/csh.cshrc and slightly more functional than /etc/manpath.config
 if you have 10 billion users and want to customize their manpath to the finest granularity :)
 
 Once I sort out where the comment is being ignored I'll commit a fix.  Thanks for the 
 report! 
 
 -Chris
 
State-Changed-From-To: open->closed  
State-Changed-By: cwt 
State-Changed-When: Sun Dec 27 16:02:39 PST 1998 
State-Changed-Why:  
Suggested fix applied in v1.23 of login.conf. 
>Unformatted:
