[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kolab-users
Subject:    man pages
From:       "Felipe Mendel N. Prates" <felipe.mnp () gmail ! com>
Date:       2005-12-22 13:47:26
Message-ID: e48b5c630512220547x607c761axdb54970e7174a4f1 () mail ! gmail ! com
[Download RAW message or body]

Here it is...

[root@server:~]# man bash
(output ok, the man page is displayed)

[root@server:~]# echo $MANPATH
(null)

[root@server:~]# eval `/kolab/etc/rc --eval all env`

[root@server:~]# man bash
(null, no man page displayed)

[root@server:~]# echo $MANPATH
/kolab/man:/kolab/local/man::/usr/share/man

[root@server:~]# unset MANPATH

[root@server:~]# echo $MANPATH
(null)

[root@server:~]# man bash
(null, no man page displayed)



On 12/22/05, Bernhard Reiter <bernhard.reiter@intevation.de> wrote:
> Am Mittwoch, 21. Dezember 2005 17:33 schrieb Felipe Mendel N. Prates:
> > Thanks for the response. You guessed right, before the eval I can read =
my
> > man pages normally. After the eval, I can't read even with "openpkg man=
.
> > Whether before or after the eval, "which man" always resolve to
> > /usr/bin/man. I've tried ltracing /usr/bin/man but got no clues.
>
> I tried it here on a few Kolab Servers and it worked.
> Try doing the steps manually:
>    /kolab/etc/rc --eval all env
> and then look at the result before copy and pasting it into the shell.
>
> Next check if MANPATH is set correctly.
>


[prev in list] [next in list] [prev in thread] [next in thread]