I am not sure this helps, because apparently "critical-chain" starts only AFTER graphical.target... and we wanted to know why graphical.target itself is delayed.
Also you asked a very relevant question: "How could iscsi services know whether the user actually needs the mounts or not?" My answer would be: it can't know! (or it would be overkill like inspecting /etc/ftab and much more places where mounts are needed). But as my first post said, the "philosophy" seems now rather "not to wait", and give instructions for those who need to wait. That being said, maybe most users need iscsi mounts to start their machines, and on the contrary that would hurt most users to not do as it is done here, which is wait for network-online and delay all by 10 seconds. A question of implementation choice probably, and coherence with choice made in other parts of the distrib! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882986 Title: open-iscsi is slowing down the boot process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1882986/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
