4/3 How come *man* suddenly doesn't work anymore? What has changed?
Has the env path been changed?
\_ Correct problem reporting protocol: Say what you tried doing.
Say what didn't happen. Say who you are so we can see what
your environment is. Oh, and mail root. --scotsman
\_ Look to thine own self.
\_ it used to work. I haven't done any env changes.
\_ i love how you're totally unspecific about what the
problem is. care to give any details whatsoever?
\_ For this i must respond: "works fine for me!"
\_ echo $MANPATH. You should get "Undefined variable". If it
is defined, type in unsetenv MANPATH (csh/tcsh). MANPATH
should not be defined on soda.
\_ What's the reasoning behind this? MANPATH should _not_ be
defined? I have MANPATH set; the system's defaults + the
man pages I installed under my own directories. And
my `man` works just fine.
\_ until the system defaults change. Almost all "man" problems
are due to outdated MANPATH variables. -tom
\_ I understand this. But not having it set means "man"
would be unable to find user-installed man pages. So
I would think the solution should be keeping one's
MANPATH up-to-date with system's defaults, no? -not
UNIX admin
\_ You have to set MANPATH if you want user-installed
man pages, but almost everyone who breaks man by
setting MANPATH isn't really using a MANPATH (likely
including the original poster). If you're using it,
keep it up to date and don't ask stupid questions on
the MOTD. -tom
\_ haha...I agree it was my fault for setting the
MANPATH and forgot about it. But the very reason
I set the MANPATH variable then was because *man*
didn't work then, so setting it helped. Now I
totally forgot about such a variable, and have
no clue how come it suddenly doesn't work again.
not until someone mentioned not to set the variable
I would still have no clue why it didn't work. -op
\_ "\_ it used to work. I haven't done any env
changes."
Music to tech support's collective ear.
\_ This is a common problem among senior citizens. The solution is
\_ This is a common problem amoung senior citizens. The solution is
a prescription of Viagra.
\_ haha, gosh, you guys are horrible. Only one guy offered a good
solution--the echo $MANPATH
\_ Haven't worked tech support before, huh? Someone who waves
their arms and says "THIS ISN'T WORKING! FIX IT!" is going
to accomplish nothing but annoy those who might be able to
help. --scotsman
\_ bad questions usually get bad answers. go figure.
\_ obviously it wasn't a bad questions. Someone who has
a real clue was able to give the answer. I thought
the question was really clear. It asked why didn't
it work when it used to be without any change in user's
environment. If you know what is going on. It would
suggest you look into the MANPATH env variable.
\_ That someone guessed at your problem and hit doesn't
obviate your question's shortcomings. If they hadn't
actally addressed your problem, you would have gone away
thinking "huh, what idiots..." when you really need to
look inward. --scotsman
\_ why do you insist your less problem solving ability
is the questions fault? =) Question asked "what have
changed? has the env path been changed?" If you know
what's going on, would that tip you that yeah, maybe
it didn't work because the MANPATH was wrong!???
One thing I can agree with you is that, Idiots think
others are idiots.
\_ I can't make you take good advice. If you like
making things harder, I guess that's your
prerogative. --scotsman
\_ I agree with this person in spite of his poor
English. tom and scotsman are just being pompous
assholes.
\_ Seriously, grow up a little, then come back to
the conversation. --scotsman
\_ gigo
\_ Nothing has changed. The man pages are in /usr/local/man,
solution--the echo $MANPATH
/usr/X11/man and /csua/man as always. You are just an idiot. |