I wonder if there are other areas of these scripts where perhaps alternatives are possible, but as the entire sysvinit package has been flagged as a high importance issue, perhaps it would be better to wait to see if a proper fix rather than my hack appears. I would suggest you try clint's suggestion if adding "set -x" to the files he discussed, as that should show exactly where the problem occurs on your machine.
I wonder if there are other areas of these scripts where perhaps alternatives are possible, but as the entire sysvinit package has been flagged as a high importance issue, perhaps it would be better to wait to see if a proper fix rather than my hack appears. I would suggest you try clint's suggestion if adding "set -x" to the files he discussed, as that should show exactly where the problem occurs on your machine.
S