On Thu, 25.09.14 19:45, Damien Robert (damien.olivier.robert+gm...@gmail.com) wrote:
> I really like the new preset directive, and I plan to use preset files > to synchronise the services I launch at boot across my computers. > > However it is a bit cumbersome that preset files do not parse instanced > services files. I could play with DefaultInstance in foobar@.service.d/ > droplets This wouldn't actually work as [Install] cannot be extended with .d/ drop-ins. Only the other sections can be. > and add foobar@.service in the preset file (this works); but this > only allow to configure one instance. How precisely would you envision this to work? I mean, so far "systemctl preset foo@bar.service" will precisely enable "foo@bar.service", but you are expecting that "systemctl preset foo@.service" would somehow result in enablement of foo@bar.service or so? How would we even denote that in the rules files? Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
