Bug 47710 - ksysguardd is not correctly reporting the network activity
Summary: ksysguardd is not correctly reporting the network activity
Status: RESOLVED FIXED
Alias: None
Product: ksysguard
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: FreeBSD Ports FreeBSD
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-09-10 17:48 UTC by Yoan Adida
Modified: 2004-01-10 22:34 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bugzilla Maintainers 2002-09-10 17:39:43 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           ksysguard
Version:           KDE 3.0.3 
Severity:          normal
Installed from:    FreeBSD Ports
Compiler:          gcc version 2.95.3
OS:                FreeBSD
OS/Compiler notes: FreeBSD 4.5.6

ksysguardd is sending to ksysguard crap about the network interfaces inputs and outputs using sysctl in FreeBSD. It would be better to use kvm_read when kvm is available.

BTW for all the OS it could be possible to enhance very much ksysguardd with a config file to determine if it must or not be working throught PF_INET sockets or just PF_UNIX sockets or some other way. When working with PF_INET sockets ksysguardd is generating some of the network activity it is reporting and for people with just one computer but working on a lan it could be disturbing.

(Submitted via bugs.kde.org)
Comment 1 groot 2003-12-30 18:32:32 UTC
Can you recheck with a more current KDE? ksysguardd segfaults on me immediately here, but that is probably unrelated; it does prevent me from checking this this.
Comment 2 andy 2004-01-10 22:34:42 UTC
Subject: kdebase/ksysguard/ksysguardd/FreeBSD [POSSIBLY UNSAFE]

CVS commit by fawcett: 

Patch from Markus Brueffer to fix:

bug:47710:
It wasn't the use of sysctl that causes the problems, but how the data returned was used

The wishlist part of this bug should be filed as a separate item, I will mail the submitter to do this.


bug:61512
behaviour is now correct

CCMAIL: brueffer@phoenix-systems.de
CCMAIL: 47710-done@bugs.kde.org
CCMAIL: 61512-done@bugs.kde.org


  M +39 -22    netdev.c   1.10 [POSSIBLY UNSAFE: printf]