Summary: | incorrect shebang for runscript.sh | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | Arvind Jayaprakash <gentoo> |
Component: | OpenRC | Assignee: | OpenRC Team <openrc> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Arvind Jayaprakash
2012-12-21 17:26:46 UTC
no actual details as to why you think it doesn't conform to POSIX. please do not file vague bugs. (In reply to comment #0) > The file /lib[64]/rc/sh/runscript.sh is actually a bash script and not a > pure POSIX shell compliant code. The script fails to execute successfuly on > such systems > change the shebang to say #!/bin/bash as opposed to #!/bin/sh The script is meant to be posix compliant, so if it isn't, let us know why it isn't. That is the correct fix, not requiring bash. My bad due to poor understanding of how runscript works. The problem turned out to be with init scripts of various applications I have on my system (eg: memcached, mysql, etc. etc). It so happens that the error message shown usually suggests the problem is with runscript.sh as opposed to the init script. Here is an example of the output http://pastie.org/5567404 I guess the answer is something And those in init.d/memcached are fixed now. |