[systemd-devel] [PATCH 2/3] unit: do not care if order isn't right when retroactively starting deps

Michal Schmidt mschmidt at redhat.com
Mon Mar 25 09:49:31 PDT 2013

On 03/23/2013 03:14 AM, Lennart Poettering wrote:
> On Wed, 13.03.13 01:44, Michal Schmidt (mschmidt at redhat.com) wrote:
>> Attempt to satisfy requirement dependencies retroactively even if
>> the unexpectedly activated unit would prefer to be started After them.
>> This way remote-fs-pre.target can be pulled in by performing a manual
>> mount (the mount units have both Wants= and After=
>> remote-fs-pre.target).
> I am a bit concerned abou this. Wouldn't this also mean that if a mount
> for /foobar/waldo suddenly shows up we'd still retroactively mount /foobar too,
> if that happens to have a unit file? That sounds wrong, no?

You are right. It would do exactly this wrong thing.
I need to rethink.


More information about the systemd-devel mailing list