summaryrefslogtreecommitdiffstats
path: root/lib/libprocstat
Commit message (Collapse)AuthorAgeFilesLines
* Disconnect non-MPSAFE SMBFS from the build in preparation for droppingattilio2012-10-183-3/+0
| | | | | | | | | | | | | GIANT from VFS. In addition, disconnect also netsmb, which is a base requirement for SMBFS. In the while SMBFS regular users can use FUSE interface and smbnetfs port to work with their SMBFS partitions. Also, there are ongoing efforts by vendor to support in-kernel smbfs, so there are good chances that it will get relinked once properly locked. This is not targeted for MFC.
* Disconnect non-MPSAFE NTFS from the build in preparation for droppingattilio2012-10-173-3/+0
| | | | | | | | | | | | | | GIANT from VFS. This code is particulary broken and fragile and other in-kernel implementations around, found in other operating systems, don't really seem clean and solid enough to be imported at all. If someone wants to reconsider in-kernel NTFS implementation for inclusion again, a fair effort for completely fixing and cleaning it up is expected. In the while NTFS regular users can use FUSE interface and ntfs-3g port to work with their NTFS partitions. This is not targeted for MFC.
* Disconnect non-MPSAFE NWFS from the build in preparation for droppingattilio2012-10-173-9/+0
| | | | | | | | | | | | GIANT from VFS. In addition, disconnect also netncp, which is a base requirement for NWFS. In the possibility of a future maintenance of the code and later readd to the FreeBSD base, maybe we should think about a better location for netncp. I'm not entirely sure the / top location is actually right, however I will let network people to comment on that more specifically. This is not targeted for MFC.
* procstat_getprocs: honor kvm_getprocs interface - cnt is signedavg2012-10-061-2/+5
| | | | MFC after: 10 days
* Add __BEGIN_DECLS and __END_DECLS to make libprocstat more C++-friendly.trociny2012-09-041-0/+2
| | | | | Submitted by: Daniel Dettlaff <dmilith gmail com> MFC after: 1 week
* Teach procstat_get_shm_info_kvm() how to fetch the pathname of a SHM filejhb2012-06-071-0/+17
| | | | | | descriptor from a core and set it in fts->fs_path. MFC after: 1 week
* Don't cast inode number or file size down to long or unsigned.gleb2012-05-182-4/+4
| | | | | | | Since ino_t size is about to change to 64-bits, casts to long would truncate 64-bit numbers on 32-bit archs. Sponsored by: Google Summer of Code 2011
* General mdoc(7) and typo fixes.gjb2012-05-111-1/+1
| | | | | | PR: 167734 Submitted by: Nobuyuki Koganemaru (kogane!jp.freebsd.org) MFC after: 3 days
* Export some more useful info about shared memory objects to userlandjhb2012-04-015-1/+101
| | | | | | | | | | | | | | | | | | | via procstat(1) and fstat(1): - Change shm file descriptors to track the pathname they are associated with and add a shm_path() method to copy the path out to a caller-supplied buffer. - Use the fo_stat() method of shared memory objects and shm_path() to export the path, mode, and size of a shared memory object via struct kinfo_file. - Add a struct shmstat to the libprocstat(3) interface along with a procstat_get_shm_info() to export the mode and size of a shared memory object. - Change procstat to always print out the path for a given object if it is valid. - Teach fstat about shared memory objects and to display their path, mode, and size. MFC after: 2 weeks
* Unbreak build.ed2012-02-101-1/+1
| | | | libprocstat still uses __si_namebuf.
* Updates to libprocstat(3) and procstat(1) to allow monitoring Capsicumrwatson2011-08-142-11/+19
| | | | | | | | | | 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
* Mention myself in the AUTHORS section.pluknet2011-07-121-1/+8
| | | | Requested by: stas
* Provide a simple manual page for libprocstat(3).pluknet2011-07-122-2/+255
| | | | Reviewed by: jilles, gjb
* Add missing libkvm and libutil dependencies.pluknet2011-06-251-0/+2
| | | | | | | Now libprocstat takes care of its own dependencies and does not require applications to specify them. Reviewed by: stas, jilles
* libprocstat: For MAP_PRIVATE, do not consider the file open for writing.jilles2011-06-181-2/+4
| | | | | | | | | 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.
* libprocstat: Fix typo in error messages.jilles2011-06-181-5/+5
|
* libprocstat: Remove spaces between function name and open parenthesis.jilles2011-06-181-2/+2
|
* libprocstat: Correct format for size_t (should be %zu, not %zd).jilles2011-06-181-3/+3
|
* Fix clang warnings.benl2011-06-181-2/+2
| | | | Approved by: philip (mentor)
* Release allocated memory in procstat_close().pluknet2011-05-181-0/+1
| | | | Reviewed by: stass
* - Whitespace fix.stas2011-05-151-1/+1
|
* - Add symbol versioning to libprocstat.stas2011-05-143-0/+24
| | | | Suggested by: kib
* - Don't try to build NWFS support module if NCP/IPX is disabled in the build.stas2011-05-122-3/+9
| | | | | | | - Rename ZFS definition to LIBPROCSTAT_ZFS to be consistent with NWFS and to prevent possible collisions. Reported by: many
* - Commit work from libprocstat project. These patches add support for runtimestas2011-05-1214-0/+2527
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
OpenPOWER on IntegriCloud