Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
NetworkManager
NetworkManager
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 139
    • Issues 139
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 10
    • Merge Requests 10
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • NetworkManager
  • NetworkManagerNetworkManager
  • Merge Requests
  • !37

Closed
Opened Oct 30, 2018 by Benjamin Berg@benzeaContributor
  • Report abuse
Report abuse

DBus service specific connection lifetime management

  • Overview 17
  • Commits 5
  • Changes 16

For P2P connections (see also !24 (closed)) I would like to be able to ensure that the P2P connection is torn down and removed when the userspace streaming service stops without doing a clean shutdown.

The approach taken in this patchset is to:

  • Add a simple NMKeepAlive object to track the reason to keep a connection alive (connection visibility, dbus name or simply user activated), moving the logic around a bit.
  • Add a new AddAndActivateConnection2 routine, to allow passing arbitrary options
  • Add a new "persist" option ("disk", "memory", "volatile") and "bind" option ("none", "dbus-client") to implement the behaviour

With this, the client can pass {"persist": "volatile", "bind": "dbus-client"} to AddAndActivateConnection. If done, the connection will be disconnected and also the information destroyed when the dbus client who activated the connection disappears from the bus.

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Reference: NetworkManager/NetworkManager!37
Source branch: dbus-service-specific-connection