bsergiu wrote: > Hi Mike, > > I am glad it helped. Indeed, the command line params supersede the > config file. That means, your output setting in the config file does not > count if you run it with the script provided per default. > Ralphy was kind enough to compile the latest version of the > shairport-sync, i.e. 3.20, however he did not manage yet to switch to a > complete config-based shairport-sync installation. I was asking him also > if possible to remove all command line params and introduce the config > file by default. I guess this will be there in the near future. In the > meanwhile, what you can do is create somewhere a start script which just > starts shairport-sync as a daemon, with no other params (caution, I am > talking about the shairport-sync executable, not the script under > /usr/local/etc/init.d). Secure this script by adding it's filename in > the /opt/.filetool.sh and running -sudo filetool.sh -b- afterwards. > Ensure that at startup, the previous shairport-sync is killed and your > script is launched. You can do so by adding a command to kill it -sudo > shairport-sync -k- and a commandline to launch your script under > -/opt/bootlocal.sh-. And then, of course, the magic incantation: -sudo > filetool.sh -b-. > > I have to say that I have tried this myself with previous versions of > piCorePlayer, where I added -shairport- manually, as it was not there. > It should work though with the latest piCoreplayer version, as this is > still a standard mechanism. > > One more thing: I do not think that you need to start shairport-sync as > root in order to work with the config. The point is, that the WebGui > starts the script -/usr/local/etc/init.d/shairport-sync-, which has the > command line params and causes your config file settings to be partially > ignored (overlapping settings are ignored). When you start it manually > by typing -shairport-sync-, it starts the real executable under > -/usr/local/sbin/shairport-sync-, and since you do not pass all those > params as command line, it takes the config file completely into > account, and thus your desired output settings. This is why I gave the > hint above to start the executable, not the .../init.d/shairport-sync > script. > > I hope this helps, > > Sergiu > > PS: @Ralphy: Can you please simply remove the command line params > (except the daemon one) from the start script and include the file that > Ihave shared? Thanks a lot in advance!
Sergiu, I used the User commands facility to implement what you suggested as a temporary workaround until the config file is the default means of configuring shairport-sync. A User command #1 of 'shairport-sync -k; shairport-sync -d' works for me, killing the default process before starting a 'blank' daemon. For some reason, splitting the commands across two User commands fails but having them both on a single line works. Obviously, this only works when piCoreplayer is rebooted. Just restarting squeezelite and shairport-sync from the web interface causes the default command line options to be used :rolleyes: Thanks again for your help, Mike ------------------------------------------------------------------------ MikeDaPsych's Profile: http://forums.slimdevices.com/member.php?userid=41620 View this thread: http://forums.slimdevices.com/showthread.php?t=107352 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
