ltsp-client-setup changes order of lts.conf "RCFILE_nn" and breaks some scripts

[Jordan Erickson]

In /var/lib/tftpboot/ltsp/i386/lts.conf, where you can set RCFILE_nn
scripts to run on the client at each boot, I was having a big issue with
a script I created to turn on headphone-jack-sense on my sound chips on
the clients. It worked fine in Feisty, but in Gutsy it broke.

Manually running the script after client bootup worked fine.

I manually chrooted and created my own symlinks to my script in default runlevels, ala:

---
# chroot /opt/ltsp/i386/
# update-rc.d ipaqsoundfix.sh defaults 98
---

So, the order of executing RCFILE_nn parms in lts.conf changed from Feisty to Gutsy, causing my script (which contains a single 'amixer set' command to turn on headphone-jack-sense) to fail. I know the script was being executed by adding an [ echo "hello" > /root/iamhere.txt ] to the script, so it has to do with the order of execution and how it changed from Feisty to Gutsy.

Thanks for your assistance!

[Oliver Grawert (ogra)]

well, we didnt change anything in this code, but the alsa stack and its initialization procedure changed completely, probably your sound devices are not there or not properly initialized at the point your script runs...

can you put: asoundconf list
in your script and redirect the output to a file to see if alsa sees your card at that point ?

[wolfger (wolfger)]

Over 5 months with no response. We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!