Bug ID | 1197542 |
---|---|
Summary | zypper ps should show the interpreted program |
Classification | openSUSE |
Product | openSUSE Distribution |
Version | Leap 15.3 |
Hardware | Other |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | libzypp |
Assignee | zypp-maintainers@suse.de |
Reporter | sionescu@cddr.org |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
When a program that runs in an interpreter has some of its files deleted, "zypper ps" shows the interpreter instead of the actual program. Showing the program that's being executed is more useful for deciding if the machine warrants a reboot. For example, after an update to Python 3.6, zypper ps shows: 5857 | ... | python3.6 (deleted) | | /usr/lib64/libpython3.6m.so.1.0 25325 | ... | python3.6 (deleted) | | /usr/lib64/libpython3.6m.so.1.0 25332 | ... | python3.6 (deleted) | | /usr/lib64/python3.6/lib-dynload/_heapq.cpython-36m-x86_64-linux-gnu.so While ps shows those 3 processes to be, in order: 5857 ... \_ /usr/bin/python3 /usr/bin/chrome-gnome-shell 25325 ... \_ /usr/bin/python3 /usr/bin/blueman-applet 25332 ... \_ /usr/bin/python3 /usr/bin/blueman-tray Even if there's no general solution for detecting interpreters, hard-coding the detection of the most common system-wide interpreters (Bash, Python, Ruby, Perl) would still be very useful.