Bug#806787: systemd-container: machines.target not enabled by default

[Ansgar Burchardt]

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 machines.target manually.
>
> I wonder whether this is an upstream bug and
> machinectl enable  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

Bug#806787: systemd-container: machines.target not enabled by default

[Michael Biebl]

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 an explicit admin action.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#806787: systemd-container: machines.target not enabled by default

[Michael Biebl]

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 start unless one also enables machines.target manually.

I wonder whether this is an upstream bug and
machinectl enable  should enable machines.target implicitly if not
yet enabled or at least issue a warning.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processed: Re: Bug#806787: systemd-container: machines.target not enabled by default

[Debian Bug Tracking System]

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 problems

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#806787: systemd-container: machines.target not enabled by default

[Ansgar Burchardt]

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 Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (300, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd-container depends on:
ii  libblkid12.27.1-1
ii  libbz2-1.0   1.0.6-8
ii  libc62.19-22
ii  libcap2  1:2.24-12
ii  libcurl3-gnutls  7.45.0-1+b1
ii  libgcrypt20  1.6.4-3
ii  liblzma5 5.1.1alpha+20120614-2.1
ii  libseccomp2  2.2.3-2
ii  libselinux1  2.4-3
ii  systemd  228-2
ii  zlib1g   1:1.2.8.dfsg-2+b1

systemd-container recommends no packages.

systemd-container suggests no packages.

-- no debconf information

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#806787: systemd-container: machines.target not enabled by default

[Felipe Sateler]

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 " will
> actually not start unless one also enables machines.target manually.
>

This is actually new in 228, since before that systemd-nspawn@ had
WantedBy=multi-user.target (and machines.target did not exist).

-- 

Saludos,
Felipe Sateler

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#806787: systemd-container: machines.target not enabled by default

[Felipe Sateler]

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 default.  This means machines
>> configured to start at boot with "machinectl enable " will
>> actually not start unless one also enables machines.target manually.
>>
>
> This is actually new in 228, since before that systemd-nspawn@ had
> WantedBy=multi-user.target (and machines.target did not exist).

Sorry, I totally misread this. It is new since 219.

-- 

Saludos,
Felipe Sateler

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers