Skip to content

Latest commit

 

History

History
248 lines (180 loc) · 11.8 KB

index.rst

File metadata and controls

248 lines (180 loc) · 11.8 KB
Raw

Welcome to psutil-extra's documentation

Process information

All of these functions take a proc argument; this can either be a psutil.Process instance or an int representing a process ID.

Linux macOS NetBSD OpenBSD DragonFlyBSD FreeBSD
:pyproc_getgroups() :pyproc_getgroups() :pyproc_getgroups() :pyproc_getgroups() :pyproc_getgroups() :pyproc_getgroups()12
:pyproc_get_umask() :pyproc_getpgid()3 :pyproc_getpgid()4 :pyproc_getpgid()5 :pyproc_getpgid()6 :pyproc_getpgid()7
:pyproc_get_sigmasks() :pyproc_get_sigmasks() :pyproc_getsid()8 :pyproc_getsid()9 :pyproc_getsid()10 :pyproc_getsid()11
:pyproc_get_sigmasks() :pyproc_get_sigmasks() :pyproc_get_sigmasks()
:pyproc_getrlimit()12

Error handling

Errors raised will vary slightly between functions and across platforms (for example, proc_rlimit() and proc_getrlimit() raise ValueError for invalid resource values). However, here is the general rule:

psutil.Error subclasses (psutil.NoSuchProcess and psutil.AccessDenied) are raised if there is one that directly corresponds to the error that occured. For most other cases, an OSError is raised.

Indices and tables

  • genindex
  • modindex
  • search

  1. These functions, when called inside a oneshot_proc() context manager, will retrieve the requested information in a different way that collects as much extra information as possible about the process for later use.↩

  2. On FreeBSD, calling proc_getgroups() inside a oneshot_proc() will first attempt to retrieve the group list via a method that collects as much extra information as possible. However, this method may truncate the returned group list. In this case, proc_getgroups() will fall back on the normal method, which avoids truncation.↩

  3. These functions, when called inside a oneshot_proc() context manager, will retrieve the requested information in a different way that collects as much extra information as possible about the process for later use.↩

  4. These functions, when called inside a oneshot_proc() context manager, will retrieve the requested information in a different way that collects as much extra information as possible about the process for later use.↩

  5. These functions, when called inside a oneshot_proc() context manager, will retrieve the requested information in a different way that collects as much extra information as possible about the process for later use.↩

  6. These functions, when called inside a oneshot_proc() context manager, will retrieve the requested information in a different way that collects as much extra information as possible about the process for later use.↩

  7. These functions, when called inside a oneshot_proc() context manager, will retrieve the requested information in a different way that collects as much extra information as possible about the process for later use.↩

  8. These functions, when called inside a oneshot_proc() context manager, will retrieve the requested information in a different way that collects as much extra information as possible about the process for later use.↩

  9. These functions, when called inside a oneshot_proc() context manager, will retrieve the requested information in a different way that collects as much extra information as possible about the process for later use.↩

  10. These functions, when called inside a oneshot_proc() context manager, will retrieve the requested information in a different way that collects as much extra information as possible about the process for later use.↩

  11. These functions, when called inside a oneshot_proc() context manager, will retrieve the requested information in a different way that collects as much extra information as possible about the process for later use.↩

  12. On DragonFlyBSD, the first call to proc_getrlimit() inside a oneshot_proc() will retrieve all of the resource limits and cache them. Further calls to proc_getrlimit() will use this cache.↩