Looks to be a timestamp related bug

[Peter Van Epp]

	There looks to be a time stamp related bug. 2.0.0g capturing off my
backbone and displayed wit ra -r argus.log -c -n. When the time stamp screws
up it looks like the tcp port numbers do as well.

Fri 09/22 16:52:21.552507  icmp    142.58.200.4        ->    142.58.232.148       2        0         72           0           URP
Fri 09/22 16:52:21.554863  icmp  142.58.189.100        ->    142.58.232.148       2        0         72           0           URP
Fri 09/22 16:52:21.555660  icmp  142.58.181.170        ->    142.58.232.148       2        0         72           0           URP
Fri 09/22 16:57:02.937876   tcp    142.58.181.4.8080  <?>      24.113.11.50.1076  5        6         2109         160         EST
Wed 12/10 10:48:18.-813560832   tcp  142.58.108.1037      <->      142.58.4.139       5085     8626      253180       11014357    EST
Fri 09/22 16:51:51.377922  icmp   142.58.249.69        ->    142.58.173.153       34       0         1224         0           URN
Fri 09/22 16:57:03.437010   tcp    142.58.181.4.8080  <?>      24.113.11.50.1077  1        5         26           134         EST
Thu 12/11 01:22:57.1025769472   tcp  192.75.242.34054      o>      142.58.1.22        2230     3187      180524       1070290     TIM
Wed 12/10 22:32:17.1370228224   tcp    142.58.1.8080      <?>      24.113.1.1078      1        4         26           108         EST
Fri 09/22 16:59:17.534513   tcp    142.58.181.4.8080  <?>      24.113.11.50.1078  0        1         0            28          EST
Fri 09/22 16:54:09.251601   tcp    142.58.181.4.8080  <|       24.113.11.50.1079  7        8         593          212         RST

Peter Van Epp / Operations and Technical Support 
Simon Fraser University, Burnaby, B.C. Canada