On Thu, 31.01.13 20:37, Lars Kellogg-Stedman (l...@oddbit.com) wrote: > I have a templated service for which each instance needs to receive > arguments of the form "foo/bar". This works fine when starting the > service: > > # systemctl start myservice@foo/bar.service
"systemctl start will actually implicitly convert this to "myservice@foo\x2fbar.service" if you write the service name like this. > But trying to *enable* this service results in an error: > > # systemctl enable myservice@foo/bar > Failed to issue method call: Invalid argument There's currently an asymmetry here: the implicit logic described above only works on "systemctl enable", not on "systemctl start", and we really should fix that. It's just oversight that we currently don't apply this to "systemctl enable" correctly, too. Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
