[systemd-devel] multi-user.target only wants network.service if I'm doing 'systemct show runlevel3.target'

[Zbigniew Jędrzejewski-Szmek]

On Sun, Feb 08, 2015 at 09:12:32AM +0300, Andrei Borzenkov wrote:
> В Wed, 4 Feb 2015 01:29:11 +0100
> Lennart Poettering <lennart at poettering.net> пишет:
> 
> > On Thu, 25.12.14 08:37, Andrei Borzenkov (arvidjaar at gmail.com) wrote:
> > 
> > > This looks like fallout of moving to generators for sysv units. Before
> > > systemd added dependencies on runlevelX.target directly to units built
> > > from initscripts. This forced runlevelX.target resolution and
> > > everything was OK. Now core systemd never references these targets
> > > directly.
> > > 
> > > This is a genuine bug which will bite people. But it looks like worked
> > > just by accident before anyway :( So we need possibility to define
> > > aliases for existing units without exhaustive search across all unit
> > > definitions ... may be unit.alias.d?
> > 
> > This is a real shortcoming of the current logic in systemd, indeed.
> > 
> > So, one possible way out of this might be add a .wants/ dep from
> > multi-user.target.wants/ to runlevel3.target, if runlevel3.target is
> > linked to that.
> 
> Won't it cause a loop? runlevel3.target is already link to
> multi-user.target; this will make it to Want itself?
This loop will be dropped. Although I think that I added code which warns
when a dependency on self is declared. This warning might have to be changed
if we got this route.

Zbyszek