Jeff Flowerday;651240 Wrote: > Just a wild guess but maybe the jive_alsa process hasn't spawned yet > when the rcS script fires?
This is true, the last thing in the rcS starts squeezeplay (the big program that does all the SB stuff). Squeezeplay starts the jive_alsa processes and then goes into its own loop, it never retruns back to the rcS script. So in order to get the jive_alsa process number you wave to check after squeezeplay has started. The easiest way to do this is to put your commands in a separate file which has a sleep at the beginning, here is what it might look like with a name such as SB_priority.sh: sleep 100 chrt... ... ... In the end of the rcS file, just before the squeezeplay command type: SB_priority.sh & The '&' at the end is important, this causes the script to run as a separate process in parallel to the squeezeplay process. That should do it. John S. -- JohnSwenson ------------------------------------------------------------------------ JohnSwenson's Profile: http://forums.slimdevices.com/member.php?userid=5974 View this thread: http://forums.slimdevices.com/showthread.php?t=89359 _______________________________________________ audiophiles mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/audiophiles
