Options: - Configure it as part of ExecStart if possible.
- Configure it using a second .service unit (oneshot), and depend on that one. - Do something with udev to mark unconfigured devices with SYSTEMD_READY=0? Not sure how. But if you can do this, it'll directly affect the "readiness" of the corresponding .device unit. On Tue, Jun 30, 2015, 18:37 Francis Moreau <francis.m...@gmail.com> wrote: > Hi, > > I have a service 'A' which creates a device 'X' and does some > configuring of the device. The device is created in a 'ExecStart=' > directive whereas its configuration happens during 'ExecStartPost='. > > But it seems that as soon as the device is seen by systemd, it creates > the corresponding device service and starts all services that depeneds > on this device. > > However this happens even if service 'A' hasn't finished to configure > the device yet. > > I tried to add 'Before=X.device' in 'A' service file, but it doesn't > seem to have any effects. > > Could anybody help me ? > > Thanks > _______________________________________________ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/systemd-devel >
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
