Date: Fri, 25 Dec 1998 09:10:00 -0800 (PST) From: skynyrd@opus.cts.cwu.edu To: freebsd-bugs@FreeBSD.ORG Subject: Re: conf/8587: login.conf should not set manpath Message-ID: <199812251710.JAA06461@freefall.freebsd.org>
index | next in thread | raw e-mail
The following reply was made to PR conf/8587; it has been noted by GNATS. 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the messagehome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812251710.JAA06461>