> On 5/21/2010 10:56 AM, Whit Blauvelt wrote:
>> 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.
> But /bin isn't first in PATH. Does 'which sh' say /bin/sh? Also, sh and
> bash are really the same thing. Does rpm -V bash show everything stock?
A suggestion: in the script, add
env > /tmp/smb.env
or whatever you want to call it. Then you can compare and contrast with
your environment.
mark