On Thu, 2006-06-01 at 14:39 -0400, Michael Grinnell wrote:
On Jun 1, 2006, at 1:58 PM, Sam Drinkard wrote:
Will McDonald wrote:
On 01/06/06, Sam Drinkard sam@wa4phy.net wrote:
<snip>
Whenever I'm troubleshooting startup files, or shell scripts in general, I find that running it like [root@foo.com init.d]# sh -x httpd start helps. It runs the script file and traces each line, so you can see where it fails.
If it were a bad shebang line, I would expect to see (under CentOS 4.3) [root@foo.com init.d]# ./httpd start -bash: ./httpd: /bin/bashr: bad interpreter: No such file or directory
I still think that either the symlink points to a non-existent target or, as another post said, bad acl/owner/permissions. But it could be from a command issued inside the script that points to something bad? Then the -x trace would nail it.
HTH
Michael
<snip sig stuff>