Michael Biebl <bi...@debian.org> writes:
> On Tue, 01 Dec 2015 12:32:06 +0100 Ansgar Burchardt <ans...@debian.org>
> wrote:
>> machines.target is not enabled by default. This means machines
>> configured to start at boot with "machinectl enable <machine>" will
>> actually not start unless one also enables machines.target manually.
>
> I wonder whether this is an upstream bug and
> machinectl enable <foo> should enable machines.target implicitly if not
> yet enabled or at least issue a warning.
I don't think that is an upstream bug: if I run "systemctl enable
${something}", I expect ${something} to be enabled as specified in the
[Install] section. This doesn't necessarily imply that the service will
be started at boot (in case the symlink is placed in a .target that does
not get started).
However I do not expect "systemctl enable ${something}" to also enable
${something-else} in case the symlink
${something-else}.wants/${something} was created. The same probably
also holds for "machinectl enable ${something}" which just enables a
"systemd-nspawn@${something}.service".
But I think that "machines.target" should be enabled by default.
Ansgar
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
