View Issue Details

IDProjectCategoryView StatusLast Update
0000114SoftwareLoggingpublic2010-10-14 23:27
ReporterPeter Assigned ToPeter  
PrioritynormalSeverityfeatureReproducibilityalways
Status closedResolutionfixed 
Product Version1.3.5 
Fixed in Version1.3.5 
Summary0000114: provide minimum log update functionality
Descriptionnow this might have to be how many packets are logged out of all possible ones, rather than a given rate. e.g. if we were to specify log no more often than once every 100ms, we might get 2 packets together then skip one, etc, so the data wouldnt have consistent gaps between it.

so may be better to specify how many packets are not logged between each that is. e.g. 0 = all logged, 1 = 50% logged, 2 = 33% logged, 3 = 25% logged, 4 = 20% logged, etc.

not the most easy thing to convey to users, but most accurate way to not record all data.
TagsNo tags attached.

Activities

Peter

2010-10-14 23:27

administrator   ~0000110

this is in v1.3.5 but as a ini option only (LogDivider). 0 = 100% of normal log data logged, 1 = 50%, 2 = 33%, etc.

Issue History

Date Modified Username Field Change
2010-08-13 15:32 Peter New Issue
2010-08-13 15:32 Peter Status new => assigned
2010-08-13 15:32 Peter Assigned To => Peter
2010-10-14 23:27 Peter Note Added: 0000110
2010-10-14 23:27 Peter Status assigned => closed
2010-10-14 23:27 Peter Resolution open => fixed
2010-10-14 23:27 Peter Fixed in Version => 1.3.5