[ksysguard] [Bug 390387] network/sockets/tcp/list causes near freeze of KSysGuard measures refresh

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=390387

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #5 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksysguard] [Bug 390387] network/sockets/tcp/list causes near freeze of KSysGuard measures refresh

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=390387

--- Comment #4 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksysguard] [Bug 390387] network/sockets/tcp/list causes near freeze of KSysGuard measures refresh

[Justin Zobel]

https://bugs.kde.org/show_bug.cgi?id=390387

Justin Zobel  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #3 from Justin Zobel  ---
Thank you for reporting this issue in KDE software. As it has been a while
since this issue was reported, can we please ask you to see if you can
reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when
replying. Thank you!

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksysguard] [Bug 390387] network/sockets/tcp/list causes near freeze of KSysGuard measures refresh

[Gerald Butler]

https://bugs.kde.org/show_bug.cgi?id=390387

--- Comment #2 from Gerald Butler  ---
Seems like this:


0129 char *get_host_name(int addr)
0130 {
0131 static char buffer[1024];
0132 struct hostent *host;
0133 struct in_addr a_addr;
0134 
0135 if (addr == 0) {
0136 return (char *)"*";
0137 }
0138 
0139 memset(buffer, 0, sizeof(buffer));
0140 
0141 if ((host = gethostbyaddr((char *), 4, AF_INET)) == NULL) {
0142 a_addr.s_addr = addr;
0143 return inet_ntoa(a_addr);
0144 } else {
0145 strncpy(buffer, host->h_name, sizeof(buffer)-1);
0146 buffer[sizeof(buffer) -1] = 0;
0147 return (char *)buffer;
0148 }
0149 }

Should be changed to have a timeout on "gethostbyaddr" of some small number of
milliseconds (maybe like 10 ms)? Of course, that would involve an
interruptable/time-outable get_host_by_addr wrapper of some sort. Ideally, this
would simply put the physical address in the column and do the lookups async
and populate the model with the host-names in the background if it was still
wanted.

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksysguard] [Bug 390387] network/sockets/tcp/list causes near freeze of KSysGuard measures refresh

[Gerald Butler]

https://bugs.kde.org/show_bug.cgi?id=390387

--- Comment #1 from Gerald Butler  ---
Found this in the source:

if ((netstat = fopen("/proc/net/tcp", "r")) != NULL) {
0200 registerMonitor("network/sockets/tcp/count", "integer",
printNetStat, printNetStatInfo, sm);
0201 /* This monitor takes _way_ too much time (up to a minute, or
more) since it does DNS lookups
0202Hide the monitor, leaving it there for backwards compatibility
*/
0203 registerLegacyMonitor("network/sockets/tcp/list", "listview",
printNetStatTcpUdpRaw, printNetStatTcpUdpRawInfo, sm);
0204 fclose(netstat);
0205 }

This seems to indicate the issue is related to DNS look-ups. Any way to enable
this without DNS look-ups (just so addresses)?

-- 
You are receiving this mail because:
You are watching all bug changes.