Michael Biebl writes:
> On Tue, 01 Dec 2015 12:32:06 +0100 Ansgar Burchardt
> wrote:
>> machines.target is not enabled by default. This means machines
>> configured to start at boot with "machinectl enable " will
>> actually not start unless one also enables
Am 30.12.2015 um 16:48 schrieb Ansgar Burchardt:
> But I think that "machines.target" should be enabled by default.
I'm a bit undecided on this. Could you poke upstream for their opinion
on this and whether distros should ship with machines.target enabled by
default or if this is supposed to be
On Tue, 01 Dec 2015 12:32:06 +0100 Ansgar Burchardt
wrote:
> Package: systemd-container
> Version: 228-2
> Severity: normal
>
> Hi,
>
> machines.target is not enabled by default. This means machines
> configured to start at boot with "machinectl enable " will
> actually not
Processing control commands:
> tags -1 confirmed
Bug #806787 [systemd-container] systemd-container: machines.target not enabled
by default
Added tag(s) confirmed.
--
806787: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806787
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Package: systemd-container
Version: 228-2
Severity: normal
Hi,
machines.target is not enabled by default. This means machines
configured to start at boot with "machinectl enable " will
actually not start unless one also enables machines.target manually.
Ansgar
-- System Information:
Debian
Control: tags -1 confirmed
On 1 December 2015 at 08:32, Ansgar Burchardt wrote:
> Package: systemd-container
> Version: 228-2
> Severity: normal
>
> Hi,
>
> machines.target is not enabled by default. This means machines
> configured to start at boot with "machinectl enable "
On 1 December 2015 at 10:05, Felipe Sateler wrote:
> Control: tags -1 confirmed
>
> On 1 December 2015 at 08:32, Ansgar Burchardt wrote:
>> Package: systemd-container
>> Version: 228-2
>> Severity: normal
>>
>> Hi,
>>
>> machines.target is not enabled by