Re: A need to manualy run /etc/cron.weekly/man-db
On Wed, Feb 25, 1998 at 11:02:08PM +, [EMAIL PROTECTED] wrote: 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=58showEditCmds=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 ? This reference to the reboot (and a previous one to running xman) make me suspicious. I wasn't able to corrupt the db even when turnung off the machine during use of man. The only corruption that I have seen is the one drived by use of the utility info which is solved by version 2.3.10-45 . which version are you running ( dpkg -s man-db can tell you)? However the newest version of man-db for bo (libc5) is available in bo-unstable (2.3.10-59bo61) toghether with a safer version of groff. fab -- | [EMAIL PROTECTED][EMAIL PROTECTED][EMAIL PROTECTED] | Líder Minimo del Pluto- Debian Developer Happy Debian User | 6F7267F5 fingerprint 57 16 C4 ED C9 86 40 7B 1A 69 A1 66 EC FB D2 5E more than 34 months are needed to get rid of the millennium. [me] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: A need to manualy run /etc/cron.weekly/man-db
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=58showEditCmds=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] .
Re: A need to manualy run /etc/cron.weekly/man-db
[EMAIL PROTECTED] writes: 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=58showEditCmds=1 it´s because the database of man-db is corrupted. HTH, Jens --- [EMAIL PROTECTED] [EMAIL PROTECTED] Key ID: 2048/E451C639 Jens Ritter Key fingerprint: 5F 3D 43 1E 24 1E CC 48 1E 05 93 3A A7 10 73 37 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
A need to manualy run /etc/cron.weekly/man-db
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 ? -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
