| 14 | | The ''biggest'' contributor seems to be Arch, although there are some Ubuntu users with the same issue. They may be running into a similar issue to skyper, in that they are only getting `/bin/java` as the interpreter (for whatever reason, the start script ''used to'' use the java command path to determine the java version, instead of using `java -version`). By using `java -version`, we fix the issue where `/bin/java` is the interpreter, since we don't depend upon its path. However, the fact that we are getting `/bin/java` as an interpreter when some of the other paths exist is a problem. And that seems to be specific to `/bin/bash` as the interpreter. Since `/bin/bash` exhibits different behavior, |
| | 14 | The ''biggest'' contributor seems to be Arch, although there are some Ubuntu users with the same issue. They may be running into a similar issue to skyper, in that they are only getting `/bin/java` as the interpreter (for whatever reason, the start script ''used to'' use the java command path to determine the java version, instead of using `java -version`). By using `java -version`, we fix the issue where `/bin/java` is the interpreter, since we don't depend upon its path. However, the fact that we are getting `/bin/java` as an interpreter when some of the other paths exist is a problem. And that seems to be specific to `/bin/bash` as the interpreter. Since `/bin/bash` exhibits different behavior, I am disinclined to use it in the #!. |
