From: Lenny Bruzenak <lenny@magitekltd.com>
To: linux-audit@redhat.com
Subject: Re: Trying to understand audisp-remote network behavior
Date: Tue, 12 Jul 2022 13:12:22 -0600 [thread overview]
Message-ID: <6fc2c414-644e-82a8-cbc7-3c8e888f34cc@magitekltd.com> (raw)
In-Reply-To: <20220712185702.43C82133BA5@pb-smtp1.pobox.com>
On 7/12/22 12:57, Ken Hornstein wrote:
>>> Well, the default configuration is that heartbeats are turned off, so
>>> the general impression I would take away from that is you should only
>>> turn on heartbeats if you have some unusual requirement.
>> This has to be coordinated between the client and server as many of these
>> setting need to be. I can add some discussion to the man page that this is
>> recommended.
> Errr ... does it?
>
> I certainly turned them on all of our clients but did not on turn
> them on our server. Did not cause any problems. I mean, yes, I could
> see that turning them on the server might be helpful, but it doesn't
> seem to be required to make them work; from my reading of the code that
> the server will respond to a heartbeat message whether or not they
> are configured, and since connections all initiate from the clients
> that's the end that has to notice the connection has dropped.
I think what Steve was referring to is the tcp_client_max_idle setting,
which has a man page item saying it needs to be higher than the
heartbeat setting on the sending side.
>
> And yes, some additional documentation might be helpful. Like if there
> was a note in the man page that said, "Enabling heartbeats is the only
> way to ensure that a connection will be retried if it is lost", that
> might have clued me in that heartbeats are essentially required for
> reliable connectivity (I am assuming we all agree that statement is
> true; as far as I can tell, even with the latest code it still is!).
This may be true, doubtful it is the intent.
LCB
--
Lenny Bruzenak
MagitekLTD
--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
prev parent reply other threads:[~2022-07-12 19:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 4:05 Trying to understand audisp-remote network behavior Ken Hornstein
2022-07-11 22:25 ` Steve Grubb
2022-07-12 2:14 ` Ken Hornstein
2022-07-12 15:23 ` Lenny Bruzenak
2022-07-12 15:49 ` Ken Hornstein
2022-07-12 16:32 ` Steve Grubb
2022-07-12 18:57 ` Ken Hornstein
2022-07-12 19:12 ` Lenny Bruzenak [this message]
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=6fc2c414-644e-82a8-cbc7-3c8e888f34cc@magitekltd.com \
--to=lenny@magitekltd.com \
--cc=linux-audit@redhat.com \
/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).