On Fri, May 21, 2010 at 10:24:00AM -0500, Les Mikesell wrote: > The only difference here 'should' be that explicitly running 'sh' will > invoke your own shell aliases and search PATH to execute sh, where if > you omit it you'll get the #!/bin/sh interpreter specified in the script > itself. Is there anything in your aliases or anything before /bin in > PATH where the working shell might be found? No aliases. No modification of PATH from the stock install. All other init.d scripts are working without problem. And as reported earlier changing the init.d/smb file to #!/bin/bash makes no difference. But invoking as "bash /etc/init.d/smb start" also works while "/etc/init.d/smb start" fails for bash as well as sh spec'd in the file (yet giving an [ OK ] both ways). > Or, perhaps this difference is coincidental and something is randomly > killing smbd. You might be able to see something if you comment out the > nmbd startup in the script and > strace -f /etc/init.d/smb start > but it will only be useful if smbd dies and you can see a failing system > call causing it. Thanks. I'll try that after lunch. The only qualification on "randomly" would be that it's 100% killing it within an instant in the not-working invocations, and 100% leaving it untouched in the working invocations. Whit