Date: 27 Apr 2000 09:20:35 -0400 From: Lowell Gilbert <lowell@world.std.com> To: freebsd-questions@freebsd.org Subject: Re: makewhatis Message-ID: <rd61z3rr87w.fsf@world.std.com> In-Reply-To: MMcClain@gi.com's message of 26 Apr 2000 20:07:31 %2B0200 References: <973597126BDDD11197AA00805FA7EBC90297CDA8@ntas0026.gi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
MMcClain@gi.com (McClain, Michael SD-EX) writes:
> In FreeBSD 3.4, is makewhatis broken?
> 'man bash' shows the man page, .apropos bash' says nothing appropriate.
Hmm. /usr/local isn't in root's path in /etc/crontab, so manpath(1)
doesn't kick back /usr/local/man, so makewhatis doesn't get told to
check /usr/local.
I'm not sure what The Right Thing is as a fix for this. Putting
/usr/local into the crontab path isn't a good idea, because it
shouldn't be needed for anything else run from the default crontab
(for obvious reasons). I'm kind of tempted to say that the right fix
would be to modify /etc/periodic/weekly/320.whatis to add /usr/local
there. It's not the prettiest fix, but other fixes seem like they
could break with some local settings.
I'll submit a PR for such a patch (which I'm also including in a
signature to this message).
Be well.
Lowell
--
*** /etc/periodic/weekly/320.whatis Fri Sep 17 00:02:18 1999
--- 320.whatis Thu Apr 27 09:19:32 2000
***************
*** 3,8 ****
--- 3,12 ----
# $FreeBSD: src/etc/periodic/weekly/320.whatis,v 1.2.2.1 1999/08/29 14:19:51 peter Exp $
#
+ # root cron jobs don't normally have /usr/local in the PATH;
+ # make sure it gets picked up by manpath
+ PATH=${PATH}:/usr/local/bin
+
if [ -x /usr/libexec/makewhatis.local -a -x /usr/bin/manpath ] ; then
echo ""
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?rd61z3rr87w.fsf>