From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [RFC] dhcpcd: fix high cpu usage
Date: Mon, 28 Oct 2019 23:34:19 +0100 [thread overview]
Message-ID: <20191028223419.i1Q3lb8f4mz9JFa0dAB-vrnILdgunSIeneVi65BeuWs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15858@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 352 bytes --]
New comment by pbui on void-packages repository
https://github.com/void-linux/void-packages/pull/15858#issuecomment-547174540
Comment:
Hmm... unfortunately, I just experienced the high CPU usage situation with this package... so the patches are no sufficient for solving this problem. It may be worth reverting back to 8.0.6 until this is resolved.
next prev parent reply other threads:[~2019-10-28 22:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 13:54 [PR PATCH] " voidlinux-github
2019-10-28 22:34 ` voidlinux-github [this message]
2019-10-28 23:29 ` voidlinux-github
2019-10-28 23:53 ` voidlinux-github
2019-10-29 3:29 ` [PR PATCH] [Closed]: " voidlinux-github
2019-10-29 3:29 ` voidlinux-github
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=20191028223419.i1Q3lb8f4mz9JFa0dAB-vrnILdgunSIeneVi65BeuWs@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).