Bug 15320 - lockd connections are not tracked explicitly
Summary: lockd connections are not tracked explicitly
Status: ASSIGNED
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: CTDB (show other bugs)
Version: 4.15.5
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Martin Schwenke
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-03-01 16:17 UTC by Ulrich Sibilller
Modified: 2023-03-02 02:06 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ulrich Sibilller 2023-03-01 16:17:15 UTC 
During a conversion on the samba ML (https://lists.samba.org/archive/samba/2023-February/244218.html) we came across lockd connections not being tracked/tickled explicitly:

> Martin Schwenke:
> In preparation for takeover, for NFS we only remember connections on
> 2049.  The other ports, such as lockd, would be handled on reboot
> (rather than crash) by the releasing side... but I doubt anyone has
> thought about this!  Perhaps we seen that part handling by UDP in the
> past?  Please feel free to open a bug to remind me to look at this.

This ticket is the requested reminder ;-)
Comment 1 Martin Schwenke 2023-03-02 02:06:52 UTC 
This branch may be helpful:

https://git.samba.org/?p=martins/samba.git;a=shortlog;h=refs/heads/ctdb-connections