-
Notifications
You must be signed in to change notification settings - Fork 45
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
ensure executable paths are absolute #129
Conversation
systemd requires absolute paths for executables. Relative path executables do not take $PATH env into account when resolving the executable.
it's not strictly required, but it is required to get the right result
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.
LGTM I think, if this seems ready then I figure we go for a 1.0.1 release with this as well.
@consideRatio added one more push with clearer comments, so should be all set from me thanks everyone for the quick review! |
I'll create a changelog PR soon for 1.0.1, but I'd like to squeeze in some debugging log messages as well first. |
systemd requires absolute paths for executables in order to resolve as expected.
Relative path executables do not take $PATH env into account when resolving the executable, only after launching the process, so
systemd-run bash -c exe
works, while justsystemd-run exe
will not.The default executable for a Spawner is the relative
jupyterhub-singleuser
, assuming $PATH will be resolved.Fixes the failure in jupyterhub/the-littlest-jupyterhub#915