🚀 go-pugleaf

In article <1992Oct7.042508.29269@cs.sfu.ca> patrice@cs.sfu.ca (Patrice  
Belleville) writes:
] Hi!
] 
] 	I recently upgraded to 3.0 (using builddisk) and it seems that man is
] (sometimes) broken. If a do a `man crontab', it complains that
] 
] 	"Reformatting page.  Wait...can't open file man8/cron.8
] 	 done"
] 
] and then creates an empty file  crontab.5 (owned by myself) in /usr/man/cat5.
] I have checked that /usr/man/man8/cron.8 is  world-readable (and indeed doing
] `man cron' works as expected).  Does anyone have  an idea as to what is going
] on?    I   can   reproduce   the   problem   at   will   (by   removing   the
] /usr/man/cat5/crontab.5) on entry `crontab', and  on `bootptab' as well. Both
] problem seem  to occur at the ".so man8/xxx" line, but the entry for `a.out',
] which contains ".so man5/yyy"  works fine  [I am not familiar with  nroff, so
] maybe the problem is obvious].

Here was the problem:

In the 2.* man directories, it appears there were no instances where the linked  
files (those containing the ".so manX/***" line) pointed to a directory other  
than the one that the link was in.  In the 3.0 man dirs, there are a few (not  
many) of these links that point to another directory--crontab is one of them.   
The link (.so file) is in man5, and the target is in man8.  This does not work.

The solution:  search for files containing the .so lines, and check where they  
point to.  If they point to some other directory, move them there.  There are 2  
of these in man5, and perhaps some others elsewhere, though I havent searched  
yet.
--
Douglas Scott                              (805)893-8352
Center for Computer Music Research and Composition
University of California, Santa Barbara
Internet: (NeXTMail ok)   <doug@foxtrot.ccmrc.ucsb.edu>