You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A better choice on Solaris 10 is to use /proc/$pid/psinfo since it also contains the uids (modulo the saved user id) - and is readable by everyone. Thus, if psutil really cares about the saved user id, it could also try /proc/$pid/cred first and then fall back to /proc/$pid/psinfo.
* Fix nice() for realtime processes under Solaris 10
fixes#1194
* Use psinfo as fallback [gu]id source on Solaris 10
fixes#1193
* Fix double free
* Match ssize_t return type of read functions
* Fix undefined behavior
with respect to strict aliasing rules and fix some warnings
For example, under strict aliasing rules of the C standard, casting a
char pointer to a struct pointer and accessing the character array
through that struct pointer yields undefined behavior.
* Update HISTORY with Solaris notes
How to reproduce:
As normal user, chose a PID of another user:
The thing is that psutil tries to read the uids from
/proc/$pid/cred
that is always only user-readable on Solaris 10:A better choice on Solaris 10 is to use
/proc/$pid/psinfo
since it also contains the uids (modulo the saved user id) - and is readable by everyone. Thus, if psutil really cares about the saved user id, it could also try/proc/$pid/cred
first and then fall back to/proc/$pid/psinfo
.For our example:
The text was updated successfully, but these errors were encountered: