Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!sdd.hp.com!ucsd!pacbell.com!ames!haven!umbc3!...!uunet!umbc5!cityzoo.acs.umbc.edu!greg
From: greg@cityzoo.acs.umbc.edu (Greg Sylvain,Lib 007a,3929,)
Newsgroups: comp.sys.hp
Subject: Man doesn't want to look into /usr/local/man/man1...why ?
Message-ID: <3571@umbc3.UMBC.EDU>
Date: 5 Jul 90 17:57:43 GMT
Sender: newspost@umbc3.UMBC.EDU
Reply-To: greg@umbc3.umbc.edu (Greg Sylvain,Lib 007a,3929,)
Organization: University of Maryland, Baltimore County
Lines: 36


	Let's try, this again.

	Ahoy out there,

	I'm having a problem with the `man' command I someone else has a better
solution.

 	I have some local man pages in /usr/local/man/manl and I have a symlink
from /usr/local/man/man1 to /usr/local/man/manl, but man seem to fail to 
travers this link. However, xman (running under R4) does this just fine. (i.e. 
xman follows a simlink from /usr/man/manl to /usr/local/man/manl.)  

	Because of the nature of being an educational institution, we try to 
keep a /usr/local tree pretty much the same between architectures.  This means
keeping man pages in /usr/local/man/manl simply for consitency between 
architectures.  And we have been able to keep a common set of install scripts 
for all the varied architectures that we have (it installs the appropriate 
binaries in the same destination directory for each machine).

	The only way I can think of to get man to work properly is to make 
a subdirectory man1 in it contains symlinks to all the man pages in ../manl/.
Needless to say, I'd rather not do this.  Any other suggestions ?

	Thanks alot,
	greg 

	(this is on a hp9000s300 machine running 7.0)

				Greg Sylvain
				Academic Computing Services
				Systems Programmer
			
	UUCP:           	...!{uunet}!umbc5!greg
	Internet (Arpa) :	greg@umbc5.umbc.edu
 	BITNET :		GREGS@UMBC