Bug 99973 - systat(1): systat -ifstat traffic counter overflow
Summary: systat(1): systat -ifstat traffic counter overflow
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 1.0-CURRENT
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-09 18:30 UTC by Vladimir K.
Modified: 2019-01-28 23:44 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir K. 2006-07-09 18:30:14 UTC
Traffic counter in systat -ifstat overflows after each 4GiB data transferred
and starts from the beginning

How-To-Repeat: transfer 4GiB or more data through the network interface while looking at
systat -ifstat
Comment 1 Yar Tikhiy freebsd_committer freebsd_triage 2006-11-27 11:57:30 UTC
State Changed
From-To: open->suspended

systat(1) just displays the values of byte counters on the network 
interfaces.  So does netstat(1).  The counters are u_long, so they 
are 32-bit on i386 and other 32-bit architectures, while they are 
64-bit on 64-bit architectures.  E.g., they can account up to 2^64-1 
bytes on amd64 or ia64. 

Of course, 64-bit counters can be emulated in systat(1) by paying 
attention to kernel counter overflows -- if someone writes a patch. 


Comment 2 Yar Tikhiy freebsd_committer freebsd_triage 2006-11-27 11:57:30 UTC
Responsible Changed
From-To: freebsd-bugs->yar

So I can see feedback...
Comment 3 Eitan Adler freebsd_committer freebsd_triage 2012-07-10 04:33:15 UTC
Responsible Changed
From-To: yar->freebsd-bugs

over to the pool (with bugmeister approval)
Comment 4 Eitan Adler freebsd_committer freebsd_triage 2018-05-20 23:52:48 UTC
For bugs matching the following conditions:
- Status == In Progress
- Assignee == "bugs@FreeBSD.org"
- Last Modified Year <= 2017

Do
- Set Status to "Open"
Comment 5 Oleksandr Tymoshenko freebsd_committer freebsd_triage 2019-01-28 23:44:00 UTC
This problem has been fixed in base r272284