Displaying 2 results from an estimated 2 matches for "update_tickles".
2024 Oct 16
1
ctdb tcp kill: remaining connections
...hwenke schrieb am 01.03.2023 23:53:
> > On Wed, 1 Mar 2023 16:18:58 +0000, Ulrich Sibiller
<ulrich.sibiller at atos.net> wrote:
> > > which ignores the port and thus matches all connections for the ip
> > > anyway. On the other hand there's
> > > update_tickles 2049
> > > in /etc/ctdb/events/legacy/60.nfs without a corresponding tickle
> > > handling for lockd connections. I am thinking about adding an
> > > update_tickles 599 for lockd connections (what's the best way to
> > > determine that port?). Any objectio...
2023 Mar 09
1
ctdb tcp kill: remaining connections
Martin Schwenke schrieb am 01.03.2023 23:53:
> Not perfect, but better...
Yes, I am quite happy with the ctdb_killtcp.
> For ctdb_killtcp, when it was basically rewritten, we considered adding
> options for max_attempts, but decided to see if it was foolproof. We
> could now add those options. Patches welcome too...
I'll have a look.
> MonitorTimeoutCount defaults to 20