#142 server - should go smoother with log retrieving

[Mustafa Yuecel]

I saw the following lines in msglog.txt:

10:48:18:928 rpcs 00:04:3f:00:01:df slog get 00:04:3f:00:00:d5 33984 421
10:48:19:172 rpcs 00:04:3f:00:01:df slog get 00:04:3f:00:00:d5 34406 272
10:48:19:377 rpcs 00:04:3f:00:01:df slog get 00:04:3f:00:00:d5 34681 1
10:48:19:581 rpcs 00:04:3f:00:01:df slog get 00:04:3f:00:00:d5 34692 1
10:48:19:785 rpcs 00:04:3f:00:01:df slog get 00:04:3f:00:00:d5 34699 1
10:48:19:989 rpcs 00:04:3f:00:01:df slog get 00:04:3f:00:00:d5 34705 2
10:48:20:193 rpcs 00:04:3f:00:01:df slog get 00:04:3f:00:00:d5 34708 2
10:48:20:397 rpcs 00:04:3f:00:01:df slog get 00:04:3f:00:00:d5 34711 4

these command rate cannot be healthy for the net. And it is not very effective...

[Mustafa Yuecel]

Logged In: YES
user_id=749518
Originator: YES

all timings and periods and timeouts should in the server should be configurable...

e.g. two dsn traffic requests within an interval of 20 sec should not result in two requests....

[Mustafa Yuecel]

Logged In: YES
user_id=749518
Originator: YES

Another dump after code distributing:

10:50:17:607 < :LH completed: 7233 lines read
10:50:17:668 > rpcs 00:04:3f:00:00:e7 dsn get power
10:50:17:670 > rpc 0 dsn ping
10:50:17:671 > rpcs 00:04:3f:00:01:9c dsn get power
10:50:17:674 > rpcs 00:04:3f:00:00:e7 dsn get traffic
10:50:17:676 > rpcs 00:04:3f:00:01:55 dsn get power
10:50:17:680 > rpcs 00:04:3f:00:01:04 dsn get power
10:50:17:683 > rpcs 00:04:3f:00:01:9c dsn get traffic
10:50:17:685 > rpcs 00:04:3f:00:00:27 dsn get power
10:50:17:687 > rpcs 00:04:3f:00:00:e7 tg get power
10:50:17:689 > rpcs 00:04:3f:00:01:55 dsn get traffic
10:50:17:691 > rpcs 00:04:3f:00:01:04 dsn get traffic
10:50:17:693 > rpcs 00:04:3f:00:00:27 dsn get traffic
10:50:17:695 > dsn get time
10:50:17:699 > rpcs 00:04:3f:00:01:a4 dsn get power
10:50:17:701 > rpcs 00:04:3f:00:01:de dsn get power
10:50:17:705 > cdist run
10:50:17:707 > rpc 0 xbank get proginfo
10:50:17:714 < [jaws@01:b6]$rpcs 00:04:3f:00:00:e7 dsn get power
10:50:17:734 < [jaws@01:b6]$rpc 0
10:50:17:735 < uart read err: 2
10:50:17:737 < uart read err: 2
10:50:17:738 < d
10:50:17:744 < uart read err: 2
10:50:17:747 < s
10:50:17:749 < uart read err: 2
10:50:17:750 < n
10:50:17:751 < uart read err: 2
10:50:17:754 < uart read err: 2
10:50:17:755 < p
10:50:17:756 < uart read err: 2
10:50:17:757 < i
10:50:17:764 < uart read err: 2
10:50:17:767 < n
10:50:17:768 < uart read err: 2
10:50:17:769 < g
10:50:17:770 < uart read err: 2
10:50:17:784 < [jaws@01:b6]$:DP 00:04:3f:00:01:b6 1080
10:50:17:788 < uart read err: 2
10:50:17:804 < rpcs 00:04:3f:00:01:9c dsn get power
10:50:17:844 < [jaws@01:b6]$rpcs 00:04:3f:00::DP 00:04:3f:00:01:9c 833
10:50:17:864 < 00:e7 dsn get traf:DP 00:04:3f:00:00:52 842
10:50:17:867 < fic
10:50:17:904 < [jaws@01:b6]$rpcs 00:04:3f:00:01:55 ds:DP 00:04:3f:00:01:04 548
10:50:17:915 < :RP 00:04:3f:00:01:9c
10:50:17:916 < :DPW 1 0.0
10:50:17:924 < :DP 00:04:3f:00:01:de 4773
10:50:17:928 < n get power
10:50:17:964 < [jaws@01:b6]$rpcs 00:04:3f:00:01:04 dsn get power
10:50:17:985 < :RP 00:04:3f:00:00:e7
10:50:17:988 < :DPW 1 0.0
10:50:18:004 < [jaws@01:b6]$rpcs 00:04:DP 00:04:3f:00:00:e7 57722
10:50:18:024 < :3f:00:01:9c dsn get traffic
10:50:18:064 < [jaws@01:b6]$rpcs 00:04:3f:00:00:27 dsn get power
10:50:18:104 < [jaws@01:b6]$rpcs 00:04:3f:00:00:g0nc:f:
10:50:18:114 < :RP 00:04:3f:00:01:9c
10:50:18:115 < :DTR 00:04:3f:00:01:9c 26320 38356 0
10:50:18:134 < t g:DP 00:04:3f:00:01:a4 766
10:50:18:156 < :RP 00:04:3f:00:00:e7
10:50:18:157 < :DTR 00:04:3f:00:00:e7 16063 17362 0
10:50:18:227 < :DP 00:04:3f:00:00:f9 573

[Roman Lim]

Logged In: YES
user_id=1611528
Originator: NO

there should be a way to disable lost log retrieval e.g. by setting numRequest to 0 in the server.properties file.
by now, 0 is not interpreted properly