From: Sven Eckelmann <sven@narfation.org>
To: Jonathan Haws <Jonathan.Haws@sdl.usu.edu>
Cc: "b.a.t.m.a.n@lists.open-mesh.org" <b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [PATCH] IPv4 multicast distribution support.
Date: Wed, 18 Jan 2017 09:11:06 +0100 [thread overview]
Message-ID: <2711856.7t1cvRFbFD@bentobox> (raw)
In-Reply-To: <1484716332.8609.3.camel@sdl.usu.edu>
[-- Attachment #1: Type: text/plain, Size: 591 bytes --]
On Mittwoch, 18. Januar 2017 05:12:12 CET Jonathan Haws wrote:
> Is there a typical test routine that is used to ensure proper operation
> of alfred? Should I simply add a third node to my setup and configure
> it as a slave and make sure things operate properly or is there a more
> automated test or better approach?
I would not be aware of some special test setup which is used for alfred.
And yes, you could simply add a slave to your setup which also tries to insert
data. All master nodes should then be able to retrieve the data from this
slave (after sync).
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-01-18 8:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 19:49 [B.A.T.M.A.N.] [PATCH] IPv4 multicast distribution support Jonathan Haws
2017-01-16 19:52 ` Jonathan Haws
2017-01-17 7:44 ` Sven Eckelmann
2017-01-17 15:39 ` Jonathan Haws
2017-01-17 16:54 ` Sven Eckelmann
2017-01-17 19:11 ` Linus Lüssing
2017-01-18 5:12 ` Jonathan Haws
2017-01-18 8:11 ` Sven Eckelmann [this message]
2017-01-17 19:30 ` Linus Lüssing
2017-01-18 5:06 ` Jonathan Haws
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=2711856.7t1cvRFbFD@bentobox \
--to=sven@narfation.org \
--cc=Jonathan.Haws@sdl.usu.edu \
--cc=b.a.t.m.a.n@lists.open-mesh.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.