From: Nikos Chantziaras <realnc@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: problem with v86d
Date: Wed, 11 Jun 2014 17:33:07 +0300 [thread overview]
Message-ID: <ln9pb3$82a$1@ger.gmane.org> (raw)
In-Reply-To: <5805.1402463655@ccs.covici.com>
On 11/06/14 08:14, covici@ccs.covici.com wrote:
> Hi. Does anyone have a clue as to why v86d should suddenly start being
> very cpu intensive on my computer? When I first boot its fine (using
> either systemd or openrc), but after a while -- maybe a day or two it
> starts using up lots of cpu and definitely increases the load average
> and slows down things. I notice this has not changed in several years,
> so I am wondering if it is not working as it used to?
>
> Thanks in advance for any ideas.
It's probably not v86d itself, but whoever is using it. But I don't know
how to find out for sure.
I didn't notice anything like that myself though. But that might be
because my machine isn't running for that long (I turn off my PC when I
don't need it.)
next prev parent reply other threads:[~2014-06-11 14:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 5:14 [gentoo-user] problem with v86d covici
2014-06-11 14:33 ` Nikos Chantziaras [this message]
2014-06-11 14:34 ` [gentoo-user] " James
2014-06-11 14:49 ` covici
2014-06-11 15:22 ` Nikos Chantziaras
2014-06-11 20:10 ` James
2014-06-11 20:38 ` covici
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ln9pb3$82a$1@ger.gmane.org' \
--to=realnc@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox