I have a similar problem, but from what I can tell with the current
templates this is not possible. I ended up using an internal script
that would loop over the process.
On 09/18/2015 02:34 PM, Dmitry Karpov wrote:
I have a template for creating the backup:
backup@.service
[Unit]
Description=Instance %i
[Service]
ExecStart=/bin/sh -c "echo do backup job for %i"
[Install]
WantedBy=maintenance.target
and some target:
maintenance.target
[Unit]
Description=target for maintenance
StopWhenUnneeded=yes
As can be seen, instances from backup@ start with maintenance.target.
But they run in parallel.
There is some way to run them one after the other?
I thought that specifying Conflicts=backup@*.service in the template
should lead to this, but it is not.
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
