From: Lucio De Re <lucio.dere@gmail.com>
To: ori@eigenstate.org
Cc: 9fans@9fans.net
Subject: Re: [9fans] Flakey DNS server
Date: Thu, 8 Oct 2020 05:29:06 +0200 [thread overview]
Message-ID: <CAJQ9t7imoKcNWSMC3n7DfzL6CdA_DAZaQ8ycBcf9Z79m7SHvtQ@mail.gmail.com> (raw)
In-Reply-To: <CB20B87EADF16B264B2B766E0771C130@eigenstate.org>
On 10/8/20, ori@eigenstate.org <ori@eigenstate.org> wrote:
>> So the big question, before I commit to something I may not be
>> competent to fix: what is recommended by those in the know?
>
> You've written a lot of text here, but none of it describes
> what exactly is flaky. I'd recommend describing the flakiness
> in more detail.
>
I'm sorry I didn't phrase what I wanted to know properly. I can tell
if 9front has a fixed version of ndb/dns or not myself, I know where
it is "broken". For social rather than technical reasons, I am more
interested in how compatibly the no doubt improved version of the
server has been altered.
I have at least a partial answer: (a) the updated server, compiled
under Labs (not quite legacy) runs pretty much identically - no
differences in operation that I could report and (b) the same
Bad rrattach magic: 0x60 - previous -0x21524542
message appears in the logs and causes an assert exception. Which is
what I have been unable to fix in the past. Or determine if it's
something I can fix by tidying up a very bloated network database.
That said, thanks to all who have replied to me, it has been
informative and encouraging.
Lucio.
next prev parent reply other threads:[~2020-10-08 3:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 4:08 Lucio De Re
2020-10-07 13:15 ` [9fans] " Wes Kussmaul
2020-10-07 16:14 ` Kurt H Maier
2020-10-08 0:45 ` Wes Kussmaul
2020-10-08 0:59 ` ori
2020-10-08 3:48 ` Lucio De Re
2020-10-08 10:54 ` Ethan Gardener
2020-10-08 12:48 ` Wes Kussmaul
2020-10-24 22:14 ` cigar562hfsp952fans
2020-10-24 22:48 ` [9fans] " Charles Forsyth
2020-10-24 23:01 ` Calvin Morrison
2020-10-25 2:09 ` Wes Kussmaul
2020-10-25 13:33 ` hiro
2020-10-25 16:43 ` Wes Kussmaul
2020-10-25 18:32 ` hiro
2020-10-25 18:38 ` Wes Kussmaul
2020-10-25 18:54 ` hiro
2020-10-25 19:00 ` Wes Kussmaul
2020-10-25 19:28 ` hiro
2020-10-25 20:19 ` Wes Kussmaul
2020-10-27 0:39 ` Thaddeus Woskowiak
2020-10-27 7:06 ` Lucio De Re
2020-10-28 3:18 ` ori
2020-10-27 14:51 ` Wes Kussmaul
2020-10-29 0:24 ` cigar562hfsp952fans
2020-10-08 0:58 ` [9fans] " ori
2020-10-08 3:29 ` Lucio De Re [this message]
2020-10-08 12:06 ` kvik
2020-10-07 6:02 Steve Simon
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=CAJQ9t7imoKcNWSMC3n7DfzL6CdA_DAZaQ8ycBcf9Z79m7SHvtQ@mail.gmail.com \
--to=lucio.dere@gmail.com \
--cc=9fans@9fans.net \
--cc=ori@eigenstate.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).