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
Rename process to program name #50
Conversation
@@ -1,2 +1,9 @@ | |||
#!/usr/bin/env bash | |||
${${PROJECT_NAME}_VENV_DEVEL_DIR}/bin/python ${program_path} "$@" | |||
#!${${PROJECT_NAME}_VENV_DEVEL_DIR}/bin/python |
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.
Nice. I wonder, did you test this with just this change (no setproctitle
)? I was under the impression this might be enough but have never tried it.
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.
The interpreter name will still end up as part of sys.argv[0], so yeah, setproctitle (or similar) is still needed.
e8befb8
to
7c9dd14
Compare
7c9dd14
to
b12cd9a
Compare
Marking this WIP due to xenial packaging issue |
b12cd9a
to
75ae12b
Compare
592bf4d
to
0bca349
Compare
The |
d3a9e6e
to
0bca349
Compare
0bca349
to
2fecfba
Compare
6ef1103
to
17b8531
Compare
17b8531
to
d4d7567
Compare
Fixed by leveraging heredoc with exec rather than touching the shebang |
#51 works fine, but changing the process name seems to bork something about how the virtualenv is loaded (see test results).Replaced bash exec with python magic, this makes python process names very similar to native processes for monitoring purposes.Replaced shebang tweaking with bash and python magic.