[systemd-devel] /etc/systemd/system/default.target.wants/ no longer checked for unit files
Michael Biebl
mbiebl at gmail.com
Fri Jul 14 10:28:20 UTC 2017
2017-07-14 12:24 GMT+02:00 Mantas Mikulėnas <grawity at gmail.com>:
> On Fri, Jul 14, 2017 at 12:13 PM, Richard W.M. Jones <rjones at redhat.com>
> wrote:
>>
>>
>> https://github.com/systemd/systemd/issues/6334
>>
>> Since this commit
>>
>> https://github.com/systemd/systemd/commit/2d058a87ffb2d31a50422a8aebd119bbb4427244
>> (in v233 and v234), you can no longer create
>> /etc/systemd/system/default.target.wants/ and drop in service files
>> (or symlinks). The directory is skipped. I have reverted the commit
>> on top of systemd from git and that makes defaults.target.wants work
>> again.
>>
>> Is this supposed to work? It worked fine since at least Fedora 18-25,
>> but it is now broken in Fedora 26.
>>
>> If it was never supposed to work, how are you supposed to enable a
>> service for the default target, even allowing for the user to change
>> the default target and still have the service enabled?
>
>
> The current convention is to install all regular services into
> multi-user.target, and I would expect all custom "daily use" targets to be
> superset of multi-user.target as well, like the provided graphical.target
> already is.
Seems like default.target is used by quite a few services though:
https://codesearch.debian.net/search?q=WantedBy%3Ddefault.target
If default.target is not supposed to be used, then this should be
mentioned somewhere.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
More information about the systemd-devel
mailing list