On Thu, Oct 02, 2014 at 02:02:49AM +0200, Michael Biebl wrote: > Am 02.10.2014 um 01:23 schrieb Ryan Kuester: > > dh_systemd_enable in package init-system-helpers skips enabling > > templated unit files (i.e., those with a "@" in their name), saying it's > > not useful to do so [1]. Is that really true? > > Yes, I think so. Template files themselves are usually not enabled, but > instances of them. So it doesn't make sense to enable [email protected], but > it might make sense to enable [email protected]. > > > I'm finding it useful in a templated service unit which declares a > > WantedBy to another templated service unit. 'systemctl enable $service' > > happily installs the expected symlink, and this construction causes both > > services to be instantiated with the instance name substituted. > > Do you have a concrete example?
An example from private packages, not official Debian packages: 1. [email protected] is instantiated and started as [email protected] by a udev rule when a USB drive is plugged. 2. [email protected] is instantiated and started as [email protected] by virtue of being symlinked under [email protected]/, the symlink coming by means of enabling [email protected]. Perhaps my example isn't compelling to anyone except me :^), but is there a reason to squash what systemctl and systemd seem to allow? systemctl seems to allow enabling of templates and systemd instantiates them in a reasonable way. -- Ryan _______________________________________________ Pkg-systemd-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
