Mailinglist Archive: opensuse-security (192 mails)

< Previous Next >
Re: [suse-security] manpath hanging (was:Re: SuSE SecurityAnnouncement - aaa_base - UPDATE)
Sorry, I asked the wrong question. What I mean is: After having killed the manpaths what can I do to prevent this from happening again? This morning I had another two manpaths running and taking up a lot of CPU time. Where did they get started? I couldn't find anything in the crontab.

--Ragnar

You must use ps aux|more
if you have jobs above 2.4 you may be must kill them
you can also must see
ps aux or ps -a |grep root and watch your daemons, becarefull with kernel tasks

Ragnar Beer wrote:

> > > >Has anyone else encountered this problem?
> > >
> > > PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME COMMAND
> > > 18307 root 10 0 704 704 384 R 0 33.1 1.1 2003m manpath
> > > 24773 root 10 0 704 704 384 R 0 32.7 1.1 688:48 manpath
> > > 29999 root 12 0 704 704 384 R 0 29.7 1.1 1:51 manpath
> > > <snip>
> > >
> > > 12:07am up 5 days, 11:46, 1 user, load average: 4.41, 4.32, 3.84
> > >
> > >
> > > ... and this machine does nothing. The manpath commands hang until you
> > > manually kill them.
> >
> >Yes, various times, SuSE 6.2 and 6.3 (don't have 6.4 yet).
> >It obviously doesn't always happen, but I could not track down when and
> >how. If I run the same command on the command lne (as is run by cron),
> >it always ran fine.
>
> I just discovered the same problem on two of my computers (SuSE 6.4).
> What can I do to stop this?
>
> --Ragnar
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: suse-security-unsubscribe@xxxxxxxx
> For additional commands, e-mail: suse-security-help@xxxxxxxx


< Previous Next >