Summary: | systemctl is-enabled does not work for templated units | ||
---|---|---|---|
Product: | systemd | Reporter: | Eivind Uggedal <eivind> |
Component: | general | Assignee: | systemd-bugs |
Status: | RESOLVED FIXED | QA Contact: | systemd-bugs |
Severity: | normal | ||
Priority: | medium | CC: | david, iksteen, maxime.deroucy, michael.tremer, rektide, tom |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Eivind Uggedal
2012-09-25 14:14:58 UTC
Instances that are not enabled trigger a "Failed to get unit file state" (No such file or directory), but it seems better to output 'disabled' if their template unite file exists. I agree that if templates unit file exist "is-enabled" should output "disabled" instead of "Failed to get unit file state". ``` max@max-server % systemctl is-enabled systemd-nspawn@.service disabled max@max-server % systemctl is-enabled systemd-nspawn@test.service Failed to get unit file state for systemd-nspawn@test.service: No such file or directory ``` `systemctl is-enabled systemd-nspawn@test.service` should output "disabled" All of this got fixed these days afaics, including the issues in the last comment. Closing hence. If any issue remains please open a new bug on github systemd. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.