Bug 106727 - In socket-tables are no PID-column
Summary: In socket-tables are no PID-column
Status: RESOLVED UNMAINTAINED
Alias: None
Product: ksysguard
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-03 14:41 UTC by Egon Poppe
Modified: 2024-09-23 21:01 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Egon Poppe 2005-06-03 14:41:16 UTC
Version:           1.2.0 (using KDE KDE 3.4.0)
Installed from:    SuSE RPMs
OS:                Linux

If we show the tcp-socket-table then we find many processes, strating over the network of the users. We find the foreign-User too but we can't se the PID. If is nessesary to kill any process, we wish to kill only the process of determined user. Kill is only avaylable in the processtable, but there is no information over the foreign user.

Better is, we can kill the process in the tcp-socket-table or we became there a PID-information.
Comment 1 John Tapsell 2007-11-26 02:30:53 UTC
To find connect an inode to a pid, we need to iterate over /proc/*/fd/*  and look at what inode each process has open.
hmm
Comment 2 Christoph Cullmann 2024-09-23 21:01:19 UTC
ksysguard is no longer maintained, in Plasma 6 there is the Plasma system monitor for this task.

If your wish is still valid for the Plasma 6 replacement, please re-open and we can move this bug to the new product, thanks!