Re: Man errors?

[Ed Cogburn <ecogburn@greene.xtn.net>]

Ossama Othman wrote:
> 
> Hi,
> 
> What does all of the following mean and how can I correct the problem?
> 
> # man afclient
> Updating index cache for path `/usr/man'. Wait...man: can't open
> /usr/man/man1/gnuserv.1: No such file or directory
> man: warning: /usr/man/man1/gnudoit.xemacs20.1.gz: bad symlink or ROFF
> `.so' request
> man: can't open /usr/man/man1/gnuserv.1: No such file or directory
> man: warning: /usr/man/man1/gnuclient.xemacs20.1.gz: bad symlink or ROFF
> `.so' request
> man: can't open /usr/man/man1/gnuserv.1: No such file or directory
> man: warning: /usr/man/man1/gnuattach.xemacs20.1.gz: bad symlink or ROFF
> `.so' request
> man: warning: /etc/alternatives/yaccman is a dangling symlink
> man: can't open /usr/man/man1/yacc.1: No such file or directory
> man: warning: /usr/man/man1/yacc.1.gz: bad symlink or ROFF `.so' request
> man: warning: /usr/man/man1/pstogif.xemacs20.1.gz is a dangling symlink
> man: can't open /usr/man/man1/pstogif.1: No such file or directory
> man: warning: /usr/man/man1/pstogif.1.gz: bad symlink or ROFF `.so'
> request
> man: warning: /etc/alternatives/tixwish.1.gz is a dangling symlink
> man: can't open /usr/man/man1/tixwish.1: No such file or directory
> man: warning: /usr/man/man1/tixwish.1.gz: bad symlink or ROFF `.so'
> request
> man: can't open /usr/man/man1/gnuserv.1: No such file or directory
> man: warning: /usr/man/man1/gnuclient.1.gz: bad symlink or ROFF `.so'
> request
> man: can't open /usr/man/man1/gnuserv.1: No such file or directory
> man: warning: /usr/man/man1/gnudoit.1.gz: bad symlink or ROFF `.so'
> request
> man: can't open /usr/man/man1/gnuserv.1: No such file or directory
> man: warning: /usr/man/man1/gnuattach.1.gz: bad symlink or ROFF `.so'
> request
> done.
> No manual entry for afclient
> 
> I know that I have no man page for afclient.  The above errors/warnings
> occur whenever I try to "man" a non-existent man page.
> 
> Thanks,
> -Ossama
> 


	I had the exact same problem.  I don't know what started it though.  So,
this isn't the proper way to handle it (this is probably a bug in one of the
packages), but I solved the problem by going to /etc/alternatives and
deleting the dangling symlinks.  You should do this with mc (midnight
commander file manager) because it displays bad symlinks in red, so spotting
the problems is easy.


-- 
Ed


--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org