public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1001629] bsd stack uses wrong timeout values if hz != 100
Date: Sun, 19 Jan 2014 18:58:00 -0000 [thread overview]
Message-ID: <bug-1001629-13-HsKRojTn6T@http.bugs.ecos.sourceware.org/> (raw)
In-Reply-To: <bug-1001629-13@http.bugs.ecos.sourceware.org/>
Please do not reply to this email, use the link below.
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001629
Grant Edwards <grant.b.edwards@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |grant.b.edwards@gmail.com
--- Comment #1 from Grant Edwards <grant.b.edwards@gmail.com> ---
I just ran into this exact same problem (though I noticed it when IPv6
addresses were timing out at 10% of the DHCP lease time).
The fix I'm currently using is almost identical to the proposed patch, except I
neglected to fix the show_ticks_in_us() function.
Is there some reason this fix hasn't been comitted?
What would it take to get it committed?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-01-19 18:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 7:54 [Bug 1001629] New: " bugzilla-daemon
2012-07-25 8:08 ` [Bug 1001629] " bugzilla-daemon
2014-01-19 18:58 ` bugzilla-daemon [this message]
2014-01-20 15:57 ` bugzilla-daemon
2014-01-21 15:59 ` bugzilla-daemon
2014-01-21 17:03 ` bugzilla-daemon
2012-07-25 7:54 [Bug 1001629] New: " bugzilla-daemon
2012-07-25 8:08 ` [Bug 1001629] " bugzilla-daemon
2014-01-19 18:58 ` bugzilla-daemon
2014-01-20 15:57 ` bugzilla-daemon
2014-01-21 15:59 ` bugzilla-daemon
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=bug-1001629-13-HsKRojTn6T@http.bugs.ecos.sourceware.org/ \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-bugs@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).