I'm not sure I understand why a rescan for new music, say, triggered by nc, would "wipe out anything playing on the 5 SBs" or "blow away somebody's carefully constructed playlist". Granted, I only have a single SlimDevice sucking off of my server, but it continues to play just fine during rescans triggered in just this way. Is this a server horsepower issue? If so, you could always dial the scanner priority down in the performance settings.
If you're listening to these podcasts at the end of the day, why not experiment with a suitable cron job firing off at 1700 (or whenever), something like: echo rescan | /usr/bin/nc -w 1 localhost 9090 That will trigger the scan for new content without wiping anything in the db. -- gharris999 ------------------------------------------------------------------------ gharris999's Profile: http://forums.slimdevices.com/member.php?userid=115 View this thread: http://forums.slimdevices.com/showthread.php?t=49213 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/unix
