Sorry about the linguistic confusion. 'libraries' should naturally read 'directories. Oh, and while you're at it, make sure you don't have these directories already. It may be different ones for you. Do an strace to find out what it's complaining about. trace -p <pid of manpath> create the directories as you go along, and run a new strace until you've caught them all. This, by the way, is another way of solving the problem, if slightly uglier :) best regards //Anders

...

---------- From: Anders Johansson[SMTP:ANDERS.JOHANSSON@MODUL1.SE] Sent: Friday, May 19, 2000 1:20:41 PM To: suse-linux-e@suse.de Subject: Re: [SLE] Problem after upgrading Auto forwarded by a Rule

If you strace the hanging manpath process, you will find that it is looking for a couple of libraries. The problem lies in /etc/manpath.config

The libraries for me were /usr/man/allman and /opt/sniff/man

logon as root and delete the lines reading MANDATORY_MANPATH /usr/man/allman

and

MANDATORY_MANPATH /opt/sniff/man

from the file /etc/manpath.config and the problem should disappear

Hope this helps //Anders

On Fri, 19 May 2000, Prasanna Krishnan[SMTP:PRAS@LINUX.CA] wrote:

...

Jean-François Bocquet @free.fr wrote:

...

Hi SuSE users,

I recently upgraded the following packages of my SuSE Linux 6.4 distribution from the web server www.suse.com:

aaa_base gpm kpackage xfstt xshared firewals kbase scanlogd wvdial yast

and I modified my /etc/passwd file so that users which had /tmp for home directory to use /var/lib as recommended by the installation process.

The problem is that now each cron daily job ran at midnight leaves a task named 'manpath' wich takes about 100% cpu time.

I tryed to look for what is done by the cron daily scripts and I also tried to disable REINIT_MANDB but I didn't find any solution.

Does anybody can help ?

-- Jean-François Bocquet === 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/

Welcome to the club! :-) A few more people have posted about this problem. What I did was to place an entry in my crontab which killed the manpath. I know this is not a proper solution for the problem, but it doesn't leave manpath burning up my CPU all the time. Here's the line from my /etc/crontab:

30 0 * * * root killall -9 manpath

I put it around the middle of the page, before the comment that says to check scripts in cron.hourly, cron.daily, etc. HTH

-- 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/

-- 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/ ######################### This message has been scanned for viruses with F-Secure Anti-Virus for Microsoft Exchange and it has been found clean.

For more information about computer viruses, connect to http://www.DataFellows.com/vir-info/. #########################

-- 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/