Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

switch-to-configuration-ng: Better handling of socket-activated units #359724

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

switch-to-configuration-ng: Better handling of socket-activated units #359724

wants to merge 1 commit into from
+28 −2

Commits on Nov 28, 2024

  1. switch-to-configuration-ng: Better handling of socket-activated units 

    Previously, if any unit had a socket associated with it, stc-ng
counted it as "socket-activated", meaning that the unit would get
stopped and the socket get restarted. That can wreak havoc on units
like systemd-udevd and systemd-networkd.

Instead, let units set the new flag notSocketActivated, which sets a
boolean on the unit indicating to stc-ng that the unit wants to be
treated like any other non-socket-activated unit instead. That will
stop/start or restart these units on upgrades, without unnecessarily
tearing down any machinery that the system needs to run.
    @antifuchs
    antifuchs committed Nov 28, 2024
    Configuration menu
    Copy the full SHA
    bf9c6c9 View commit details
    Browse the repository at this point in the history