-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add the path to shiny-server binary and add explanation #24
base: master
Are you sure you want to change the base?
Conversation
For some reason if the shiny-server is not referenced by the full path , the start-stop-daemon does not start it.
It could read |
DESC="shiny server" | ||
NAME=shiny-server | ||
DAEMON=shiny-server | ||
DAEMON=/usr/local/bin/shiny-server |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
DAEMON=
which shiny-server`` may be preferable.
I know that this is old, but thought I'd still comment, as the suggestion is a misunderstanding of how the TLDR; |
Hi @jimklo, Thank you for trying to teach me that, but I know what which does :-). The only misunderstanding might be about the problem at stake. I had only one version of shiny server installed, but for whatever reason (it's old, as you say it...) using |
I know your problem has nothing to do with multiple versions, and it could be just the way your system is behaving. According to the man page for 'which', it just searched the PATH environment variable and returns the absolute path of the first one it find. What I'm saying is something is odd about your system if 'which' finds the program, but the shell you're executing 'which' cannot. They should be using the same PATH environment variable to resolve. Hence why I question using 'which' - I'm not denying it works for you, but I'd like to know why it works, because the way you describe the problem - 'which' should not work either, unless your sub-shell's environment is different from the main shell's. If you can do: '''PATH= which shiny-server''' And this returns a path - something is really odd. |
Yeah, the problem comes from the fact, as specified by the OP, that if the name of the daemon only is provided, the script will not execute properly - should it be on the path or not! It is because of the following line:
|
For some reason if the shiny-server is not referenced by the full path , the start-stop-daemon does not start it.