[systemd-devel] /etc/systemd/system/default.target.wants/ no longer checked for unit files

[Richard W.M. Jones]

On Sun, Jul 16, 2017 at 04:31:40PM +0200, Lennart Poettering wrote:
> default.target and multi-user.target are quite different:
> 
> For system services, default.target is generally an alias for either
> multi-user.target or graphical.target, but can point to anything else,
> too. By dropping in your deps into default.target you say "whatever
> the user picks as default, even if it is emergency.target, I want my
> service started".

Thanks Lennart, this is an interesting take which I hadn't thought
about before.  I think I will change virt-customize so it drops these
firstboot services into multi-user.target instead.

> For user services, default.target is a regular unit, and not an alias,
> as there things are usually quite a bit simpler.
> 
> Do note that if the user starts his system with a special
> runlevel/target specified on the kernel cmdline, default.target has no
> effect, as we don't bother with it then but directly boot into the
> specified name.
>
> Hence, unless you are really really sure your stuff should be loaded
> under all conditions, then default.target in system mode might be an
> option. In most cases however that's not desirable, and
> multi-user.target is the better place (or graphical.target, or so).

... And also for these reasons.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW