My favorites | Sign in
Project Home Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 331: `cmdline` should not be cached
1 person starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  ----
Closed:  Apr 2013


Sign in to add a comment
 
Reported by Psihon...@gmail.com, Sep 24, 2012
After version 0.5, property `cmdline` of Process is cacheable. 
Could you explain why so? 
There are a lot of situations, when process `cmdline` contains some valuable information, which should be processed/validated. 

Thanks.

p.s. update psutil from 0.4.1 to 0.6.1, with cacheable `cmdline`, completely crashed our mail fetching monitoring system :)


Sep 24, 2012
Project Member #1 g.rodola
Cmdline is cached bacause is not supposed to change during the entire lifetime of the process (the same applies for process pid, ppid, name an exe).
How exactly your code was affected by this change?
The only difference in terms of compatibility should be that in case the process disappears NoSuchProcess is no longer raised.

Jan 21, 2013
#2 ruib...@gmail.com
runsvdir (of runit) alters its .cmdline to include recent stderr messages from all child processes.
Jan 22, 2013
Project Member #3 g.rodola
(No comment was entered for this change.)
Status: Accepted
Feb 27, 2013
Project Member #4 g.rodola
Fixed in r1570.
Status: FixedInSVN
Labels: Milestone-0.6.2
Mar 2, 2013
Project Member #6 g.rodola
Updated csets after the SVN -> Mercurial migration:
r1570 == revision 9d2f1e41eee3
Apr 7, 2013
Project Member #7 g.rodola
(No comment was entered for this change.)
Status: FixedInHG
Apr 11, 2013
Project Member #8 g.rodola
(No comment was entered for this change.)
Labels: -Milestone-0.6.2 Milestone-0.7.0
Apr 12, 2013
Project Member #9 g.rodola
(No comment was entered for this change.)
Status: Fixed
Sign in to add a comment

Powered by Google Project Hosting