On Wed, 04.02.15 01:52, Michael Biebl ([email protected]) wrote: > 2015-02-04 1:29 GMT+01:00 Lennart Poettering <[email protected]>: > > On Thu, 25.12.14 08:37, Andrei Borzenkov ([email protected]) 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. THis would cause runlevel3.target to be loaded, which > > would then detect the symlink and merge it into > > multi-user.target. After loading it would try to create the .wants > > link, but recognize that it is now trying to create a .wants link on > > itself, and suppress it. > > Is this the same issue as > https://bugzilla.redhat.com/show_bug.cgi?id=1002806#c20 ?
Feels like it. It's not clear to me though why the bug was closed, i.e. what fix was applied there... Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
