Dear all,

        Follwoing the recent discussion of problems with man, I decided to
try and fix it by doing mandb --create. So - I log in, su, and try and run
it - 

[EMAIL PROTECTED]:~# mandb --create
Processing manual pages under /usr/man...
mandb: warning: /usr/man/man8/mailq.8.gz: whatis parse for mailq(8) failed
mandb: warning: /usr/man/man8/sendmail.8.gz: whatis parse for sendmail(8)
failed
mandb: warning: /usr/man/man8/runq.8.gz: whatis parse for runq(8) failed
mandb: warning: /usr/man/man8/rmail.8.gz: whatis parse for rmail(8) failed
mandb: warning: /usr/man/man8/rsmtp.8.gz: whatis parse for rsmtp(8) failed
mandb: warning: /usr/man/man8/in.smtpd.8.gz: whatis parse for in.smtpd(8)
failed
mandb: can't open /usr/man/man1/gnuserv.1: No such file or directory
mandb: warning: /usr/man/man1/gnudoit.xemacs20.1.gz: bad symlink or ROFF
`.so' r
equest
mandb: warning: /usr/man/man1/uupath.1.gz: whatis parse for uupath(1)
failed
mandb: can't open /usr/man/man1/gnuserv.1: No such file or directory
mandb: warning: /usr/man/man1/gnuclient.1.gz: bad symlink or ROFF `.so'
request
mandb: can't open /usr/man/man1/gnuserv.1: No such file or directory
mandb: warning: /usr/man/man1/gnuclient.xemacs20.1.gz: bad symlink or ROFF
`.so'
 request
mandb: can't open /usr/man/man1/gnuserv.1: No such file or directory
mandb: warning: /usr/man/man1/gnuattach.xemacs20.1.gz: bad symlink or ROFF
`.so'
 request
mandb: can't open /usr/man/man1/gnuserv.1: No such file or directory
mandb: warning: /usr/man/man1/gnuattach.1.gz: bad symlink or ROFF `.so'
request
mandb: can't open /usr/man/man1/gnuserv.1: No such file or directory
mandb: warning: /usr/man/man1/gnudoit.1.gz: bad symlink or ROFF `.so'
request
mandb: warning: /usr/man/man1/pstogif.xemacs20.1.gz is a dangling symlink
mandb: can't open /usr/man/man1/pstogif.1: No such file or directory
mandb: warning: /usr/man/man1/pstogif.1.gz: bad symlink or ROFF `.so'
request
mandb: warning: /usr/man/man1/analog.1.gz: whatis parse for analog(1)
failed

It then just sits there (and indeed the process seems no longer to be
running):

 9:23am  up 65 days, 12:38,  2 users,  load average: 0.11, 0.39, 0.73
52 processes: 50 sleeping, 1 running, 1 zombie, 0 stopped
CPU states:  4.0% user,  4.9% system,  0.0% nice, 91.2% idle
Mem:   14144K av,  13240K used,    904K free,  22732K shrd,   1944K buff
Swap:  66524K av,   1984K used,  64540K free                  4196K cached

  PID USER     PRI  NI  SIZE  RSS SHARE STAT  LIB %CPU %MEM   TIME COMMAND
29087 mcv21     15   0   776  776   576 R       0  8.5  5.4   1:05 top
28580 root       1   0   660  660   500 S       0  0.3  4.6   0:06
in.telnetd
    1 root       0   0   116   64    40 S       0  0.0  0.4   0:20 init


The running process being stop, and the zombie being a runq (zombie) which
I probably should get round to killing.

Should I kill the process, and try again, or what?

Thanks,

Matthew

-- 
Elen sila lumenn' omentielvo

Steward of the Cambridge Tolkien Society
Selwyn College Computer Support
http://www.geocities.com/Area51/Chamber/8841/
http://www.cam.ac.uk/CambUniv/Societies/tolkien/
http://pick.sel.cam.ac.uk/

Reply via email to