-
Notifications
You must be signed in to change notification settings - Fork 33
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
Solaris failures from pipenv #25
Comments
Is there documentation what format Solaris uses for its proc? And more importantly, why is it in a different format? Is it following a different spec? |
Yes, the documentation for the format of proc(4) can be found here: It appears that /proc/pid/psinfo would be the right place to get the tty and ppid. I've seen an implementation of this in python here: I'm not sure about the reasoning for the formatting/spec |
Might be easier to get this info from 'ps' |
I just ran into this too on SmartOS (Solaris...). I guess pipenv is a NOOP for me now because of this unless I do that hack above. |
@anilj If Pipenv is your main concern Id suggest filing a PR to catch this error at the call site. |
Hi, I've hit an issue on Solaris 11.4 when trying to invoke a shell using pipenv version 2018.11.26 (python3.7)
Similar to:
detect_shell fails on IBM i / AIX #21
The messages I would see were like so:
The real issue here is that when shellingham tries to split the data it reads from /proc/PID/status, it fails, because the formatting is not as it expected.
In order to get around this, I modified posix/proc.py like so:
This solved the failures on my end.
Perhaps this is already fixed by 'Switch to parse 'ps wwl' for better compatibility #23'.
I can test this if necessary.
The text was updated successfully, but these errors were encountered: