> > > > On a previous posting I said that I needed to run the mentioned cron script > > manualy. > > Now I found out when I had to run this script manualy. > > It turned out that it happaned after a shutdown command when I was logged > > to an xterm (and su to root). Prior to the shutdown I also had an xman > > window opened. > > And after I turned on the power, rebooted and logged again, I got a > > segmentation fault whenever I tried to man -w something. Only after manualy > > running the script the man -w something worked. > > Has someone else experienced this ? > > Yes. Please refer to the Debian-user faq: > http://www.debian.org/cgi-bin/fom?file=58&showEditCmds=1 > > it´s because the database of man-db is corrupted.
The above reference (fom?...) is claims that the DB is getting corrupted and that rebuliding it solves the problem. This is seems to an answer. However, it is also said that the DB corruption is due to a failed search. But my claim is that the corruption appears after using the reboot or shutdown command from an xterm. Furthere, when I reboot or shutdown the machine from a VT (after switching to a VT using ctrl+alt+F?), the DB does not get corrupted. Is this a bug ? -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
