> Have you looked through your /var/log/messages file? Try grepping for
> 'rc-scripts' and alsa on your system logfile and see if it turns anything up.
>
> Also, just after a fresh boot, you can look at the output from the 'dmesg'
> command for hints.
Thanks, I will look at those. Something tells me though that it could be
more complicated. After playing around with runscript.sh, I noticed that
after a call to a function called wrap_script, any signs of alsasound
being launched completely disappeared. Now, netmount is also a startup
script and it's in the same runlevel. So, while alsasound disappears
after wrap_script, netmount keeps going and gets launched OK. When I
commented out wrap_script, alsasound WAS launched but the "start"
parameter for the alsasound script was missing.
The wrap_script function is a bit of a mystery to me. It wraps the
original alsasound script (or any other startup one for that matter) in
a function called "test" (if I remember it right), then sources it, then
runs that function.
> Permissions shouldn't be an issue if you can run it manually, but it never
> hurts to check that your /etc/init.d/ script is 755 root:root and that you
> have a proper link in /etc/runlevels/<runlevel>.
The links and permissions are right for sure.
Thanks,
Sergei
--
[email protected] mailing list
