On Fri, Feb 15, 2013 at 10:40 AM, Thomas Bächler <[email protected]> wrote: > Am 14.02.2013 21:45, schrieb Jouke Witteveen: >> On Tue, Feb 12, 2013 at 1:40 PM, Ivan Shapovalov <[email protected]> >> wrote: >>> If a profile is WantedBy=multi-user.target, it breaks init sequence >>> if its interface is not immediately available at runtime >>> (e. g. a cell-phone or USB modem). >> >> Does this work? Is there a reason not to make the device the default trigger? > > That's an interesting question. You can always add a profile as a > dependency to > /etc/systemd/system/sys-subsystem-net-devices-FOO.device.wants/ > and add > BindsTo=sys-subsystem-net-devices-FOO.device > so it goes down when the devices vanishes. This is actually pretty nice > if you think about it. > > But do we really want that? Some people may say that they only want > their devices going up when they launch multi-user.target, but not when > they launch rescue.target. It's a matter you should consider carefully. > >
Another option is to add everything to network.target.wants. Although that might be a better place, it doesn't really solve the initial problem. On the other hand: what is precisely the problem: the unit just times out and is not supposed to block anything.
