Hello reg, on Wednesday, May 24, 2000 at 12:55:53 -0400, you sat in front of your keyboard and wrote:

I am using suse 6.4 and other than my sound card not working properly, I have one problem.

Every day a process starts called manpath (uder ktop, lists it as, in tree format as 'sh...security-contro...security-contro...sh...csh...manpath') and it runs forever hogging the cpu. I figured I would let it run to see if it would ever end on it's own but it never does. Matter of fact, I went away for a few days and came back to find five seperate instances of it running and that it had been running for days. I read the man pages on manpth to find out what it is doing but can't figure out why it doesn't finish. Any suggestions?

I ran into the same problem some weeks ago, the solution was to edit the file /etc/manpath.config and to check each paths from the lines beginning by MANDATORY_MANPATH. Comment all the lines relating to paths that are not on your system and all should go fine. Regards... -- Jean-François Bocquet <tns01@free.fr> === Error is not forever, hope for right+ |== ICQ: 69968770 ====================== Darkness is not the opposite of light| |== http://tns01.free.fr =========== -But only absence- day will follow night.| +-- Linux User #177410 ---------------------------------------------*-- Lowell+ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

reg hughson tapped away at the keyboard with:

I am using suse 6.4 and other than my sound card not working properly, I have one problem.

Every day a process starts called manpath (uder ktop, lists it as, in tree format as 'sh...security-contro...security-contro...sh...csh...manpath') and it runs forever hogging the cpu. I figured I would let it run to see if it would

I assume that you also downloaded the yast.rpm and applied it. Or at least thought you did. It frequently fails for some reason; about 80 to 90% through the installation if you attempt it through YAST. Force a reinstallation of the new yast.rpm at the command line. rpm --install --replacepkgs yast.rpm That seems to have fixed the problem on all of "my" machines. -- Bernd Felsche - Innovative Reckoning Perth, Western Australia -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/