You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many systemd commands allow wildcards for unit names, which is especially useful for parameterized units (e.g., "[email protected]", where multiple instances of the unit can be started by the operator and end up with arbitrary IDs following @ in the instance name (e.g., "[email protected]"). But systemd_filter=_SYSTEMD_UNIT=<unit-name> seems to only match exactly, with no way to use wild cards for flexible matching. Is that really the case, and is there an alternative way to more flexibly filter on a part of the unit name?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Many systemd commands allow wildcards for unit names, which is especially useful for parameterized units (e.g., "[email protected]", where multiple instances of the unit can be started by the operator and end up with arbitrary IDs following
@
in the instance name (e.g., "[email protected]"). Butsystemd_filter=_SYSTEMD_UNIT=<unit-name>
seems to only match exactly, with no way to use wild cards for flexible matching. Is that really the case, and is there an alternative way to more flexibly filter on a part of the unit name?Beta Was this translation helpful? Give feedback.
All reactions