Can't open man pages in SuSE
 

Ok.. let me restart this question since it has been broken...

In SLES 11 a freshly installed system when I try to get the man pages I get a weird error.
/usr/bin/nroff: Can't create temp directory, exiting...

I know this error is just confusing because mktemp work just fine.

I read around by googling but I can only find people relating the problem without any solution.

I found this post which is cute, but I dont want to set my LD_LIBRARY_PATH has it is just a bad patch to solving the real issue.

http://svn.pan-starrs.ifa.hawaii.edu...pp/ticket/1079

Has anyone found something to fix this?


Some info:
SLES 11 x64 guest OS on VMware ESX
with 3.8GB of free space ;-)

Well, I looked at $LD_LIBRARY_PATH on one of the SUSE boxes where I work. $LD_LIBRARY_PATH isn't set, but man works just fine... so $LD_LIBRARY_PATH in and of its self isn't the issue.

I would try running

just to make sure that it does in fact run... if it gives you anything at all, then there's no reason to go off down that alley. Also, as Evo2 mentioned, you may want to check and see if there's enough room on your /tmp partition.

Finally, it probably wouldn't hurt to know what distro and version that you're running, all the documentation that I've run into shows this problem to be Suse specific. You can find this information by typing

Pete, I split your post out of the original; please don't hi-jack others
threads, or reanimate long gone ones.


Cheers,
Tink

Why not? It wasn't fixed anyway? asking out of curiosity here.


Yeah but by splitting it, now it doesn't make any sense because I assumed the people would read the openning post.. now my question is worthless because its incomplete..

While it's not strictly speaking against any of LQs
written rules it's generally frowned upon to a) necropost
or b) hijack threads. You did both in one go, and
people have reported it.

One of the reasons being that people who had subscribed to
the original thread may not necessarily be interested in
getting e-Mail notifications for your tacked on post.


I shall call you rabbit, for you are jumping to conclusions. ;}

You don't know that. It wasn't FLAGGED as resolved, but
the links that got posted in the original thread may have
made the problem of the original poster go away.

Unfortunately a good number of our members who receive
valuable help don't bother reporting back whether or not
they got things sorted, or flag their threads as solved.



Cheers,
Tink