On Sat, Jun 8, 2013 at 5:43 PM, <systemdki...@yopmail.com> wrote:
> Where in boot sequence tune A/V latency? Is sound.target relevant?
anything device specific should be triggered from a udev rule, so that
you're not running this service while the device isn't actually
available yet to userspace...
systemd already installs a 99-systemd.rules file that has:
SUBSYSTEM=="sound", KERNEL=="card*", TAG+="systemd",
ENV{SYSTEMD_WANTS}+="sound.target"
So linking your service file into sound.target.wants should work.
(but, I haven't tested this particular case or taget myself).
you probably want to do:
# mkdir /etc/systemd/system/sound.target.wants
# ln -sf /path/to/your.service
/etc/systemd/system/sound.target.wants/your.service
Auke
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
