Hi! Paul,

On 11/01/2014 09:46 PM, you wrote:

 PQ>> Quit using the -R all the time.  Only when you're finished extracting
 PQ>> the stats from the current status of the data.  :)

 PH> But if I do this I end up getting aggregate data for more than one day -
 PH> right? And in doing so loose the ability to pull data for just one 24 hour
 PH> period - I think?

Yes.  You're only able to pull stats since the last "-R" was
used.  So, your original statement "seems I can't have it both
ways" stands true.

This isn't one of FE's strong points.  It is a tosser/scanner & packer
tool, firstly, after all.

From my notes, I can see that I switched over to weekly stats back in '97. 
Back then there wasn't a lot going on then, to justify 24-hourly reports...
it seems.

 PQ>> Is there some other tool scanning posts outbound?  Since it seems
 PQ>> that FE may not be doing it, then whatever is isn't updating
 PQ>> FE's data.

 PH> Hmm... not at the HUB level that FE is looking after. It's set up to toss
 PH> echoarea packets to downlinks when packets comes in from my uplink.

Ah, I think I 'see' what you're talking about now.  The "pass
through" traffic?  That stuff may only show in the system link
summaries and not on a per echo basis.

 PH> Only the posts FE is making to a stats echo I set up for the NZ areas are
 PH> being seen by FE. FE is only looking only at the HUB .JAM bases. I conclude
 PH> that FE would need to see posts made directly to those JAM bases in
 PH> order for the outbound stats to be counted. I think all the inbound stats
 PH> are the tossed packets from my uplink. I guess inbound packets from
 PH> downlinks are also seen as inbound stats.

Yes, the 'Export' posts are those locally generated by a BBS (if any) or
your BATch scripts whenever FE does the scan out.  E.g., my own posts on
*this* node do not show in my main node's stats.  Only as 'Import' traffic.

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.6.0