If you only want one instance running, why not just create one service and reconfigure/restart it? <div class="gmail_quote"><div dir="ltr">On Mon, Oct 5, 2015, 09:04 Johannes Ernst <<a href="mailto:johannes.ernst@gmail.com">johannes.ernst@gmail.com</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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 <a href="mailto:systemd-devel@lists.freedesktop.org" target="_blank">systemd-devel@lists.freedesktop.org</a> <a href="http://lists.freedesktop.org/mailman/listinfo/systemd-devel" rel="noreferrer" target="_blank">http://lists.freedesktop.org/mailman/listinfo/systemd-devel</a> </blockquote></div>