On Wed, Feb 23, 2022 at 11:55 PM Chris Adams <li...@cmadams.net> wrote: > > Once upon a time, Zbigniew Jędrzejewski-Szmek <zbys...@in.waw.pl> said: > > So this is the culprit. iscsi.service has Before=remote-fs-pre.target, > > After=network-online.target, which means that it'll delay the boot. > > If that's the problem, there's some other issue. On my up-to-date F35 > system, iscsi.service also has: > > ConditionDirectoryNotEmpty=/var/lib/iscsi/nodes > > And on my systems, that directory is empty, so iscsi.service shouldn't > be holding up anything.
How can one be sure that (in the general case) that one of the units that you are running After will not create the files/directories that will impact the test Condition(s)? Those tests occur before the unit is actually started, but not before the ordering is performed. _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
