> On Oct 5, 2015, at 14:29, David Timothy Strauss <da...@davidstrauss.net> > 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 <johannes.er...@gmail.com > <mailto:johannes.er...@gmail.com>> wrote: > I have a foo@.service. When started as > systemctl start foo@abc > I’d like all other currently active foo@… services to stop, and vice versa. > All of the foo@.services are supposed to be mutually exclusive with each > other. > > In foo@.service, I attempted: > Conflicts: foo@.service > but that does not seem to do the trick (Starting foo@abc produces "Dependency > Conflicts=foo@abc.service 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 > systemd-devel@lists.freedesktop.org > <mailto:systemd-devel@lists.freedesktop.org> > http://lists.freedesktop.org/mailman/listinfo/systemd-devel > <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
