[CentOS] Odd failure of smbd to start from init.d - CentOS 5.4

On Thu, May 20, 2010 at 06:49:33PM -0400, Kwan Lowe wrote:

> The service scripts can check for lock files.  Do you have any stale
> locks in /var/run/subsys?

Thanks Kwan.

If I remove /var/run/smbd.pid (and /var/run/nmbd.pid for that matter), the
init.d/smb file still fails to get smbd running persistently. Same thing
with removing /var/lock/subsys/smb - which gets touched by init.d/smb only
after both files return 0 for successful starts, and does get touched in
this case, even though of course smbd hasn't really run, if at all, for more
than an instant.

Plus, if it were a lock file problem, those scripts shouldn't be showing 
"[ OK ]," right?

Also, since "sh /etc/init.d/smb (re)start" works but "/etc/init.d/smb
(re)start" doesn't, I can't see how the difference between those two
invocations would change the handling of the lock files. It's still the same
script being run. Just some change in the environment whose subtlety escapes
me.

Whit