> On Oct 5, 2015, at 14:29, David Timothy Strauss <[email protected]> > wrote: > > If you only want one instance running, why not just create one service and > reconfigure/restart it? > Because the service dependencies are totally different.
> > On Mon, Oct 5, 2015, 09:04 Johannes Ernst <[email protected] > <mailto:[email protected]>> wrote: > I have a [email protected]. When started as > systemctl start foo@abc > I’d like all other currently active foo@… services to stop, and vice versa. > All of the [email protected] are supposed to be mutually exclusive with each > other. > > In [email protected], I attempted: > Conflicts: [email protected] > but that does not seem to do the trick (Starting foo@abc produces "Dependency > [email protected] dropped”) > > I’d like to avoid having to enumerate foo@abc, foo@def etc. in the Conflicts > section. > > Ideas? > > Thanks, > > > > Johannes. > > _______________________________________________ > systemd-devel mailing list > [email protected] > <mailto:[email protected]> > http://lists.freedesktop.org/mailman/listinfo/systemd-devel > <http://lists.freedesktop.org/mailman/listinfo/systemd-devel>
_______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
