| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
libprocstat still uses __si_namebuf.
|
|
|
|
|
|
|
|
|
|
| |
capability mode and capabilities.
Right now no attempt is made to unwrap capabilities when operating on
a crashdump, so further refinement is required.
Approved by: re (bz)
Sponsored by: Google Inc
|
|
|
|
| |
Requested by: stas
|
|
|
|
| |
Reviewed by: jilles, gjb
|
|
|
|
|
|
|
| |
Now libprocstat takes care of its own dependencies and does not
require applications to specify them.
Reviewed by: stas, jilles
|
|
|
|
|
|
|
|
|
| |
If a file is mapped with with MAP_PRIVATE, no write permission is required
and changes do not end up in the file. Therefore, tools like fuser and fstat
should not show the file as open for writing.
The protection as displayed by procstat -v still includes write in this
case, and shows 'C' for copy-on-write.
|
| |
|
| |
|
| |
|
|
|
|
| |
Approved by: philip (mentor)
|
|
|
|
| |
Reviewed by: stass
|
| |
|
|
|
|
| |
Suggested by: kib
|
|
|
|
|
|
|
| |
- Rename ZFS definition to LIBPROCSTAT_ZFS to be consistent with NWFS and to
prevent possible collisions.
Reported by: many
|
|
file and processes information retrieval from the running kernel via sysctl
in the form of new library, libprocstat. The library also supports KVM backend
for analyzing memory crash dumps. Both procstat(1) and fstat(1) utilities have
been modified to take advantage of the library (as the bonus point the fstat(1)
utility no longer need superuser privileges to operate), and the procstat(1)
utility is now able to display information from memory dumps as well.
The newly introduced fuser(1) utility also uses this library and able to operate
via sysctl and kvm backends.
The library is by no means complete (e.g. KVM backend is missing vnode name
resolution routines, and there're no manpages for the library itself) so I
plan to improve it further. I'm commiting it so it will get wider exposure
and review.
We won't be able to MFC this work as it relies on changes in HEAD, which
was introduced some time ago, that break kernel ABI. OTOH we may be able
to merge the library with KVM backend if we really need it there.
Discussed with: rwatson
|