Hello all,

it seems that the newly added `systemctl edit` command requires its arguments
to be valid unit names.

This causes `edit` operation to fail in apparently valid use-cases like

    systemctl edit [email protected]
or
    systemctl edit [email protected]

In second case, the error message is especially cryptic:
"[email protected] ignored: not found".

Actually I understand what it does mean: systemctl asks the manager to show
unit's FragmentPath -> the manager tries to load the unit -> loading fails with
"File exists" because [email protected] is already instantiated.

(BTW, it's a separate question: is this failure valid or is it a bug?)

But well. I guess that `edit` operation should always work with unit files
directly, just like enable/disable commands do.

Is this all correct? Can anyone please comment on these two issues?

-- 
Ivan Shapovalov / intelfx /

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Reply via email to