Back to the main page.
Bug 159 - wrong peerlist
| Status | CLOSED FIXED |
| Reported | 2010-09-16 11:28:00 +0200 |
| Modified | 2011-01-05 12:01:03 +0100 |
| Product: | FieldTrip |
| Component: | peer |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Linux |
| Importance: | P1 normal |
| Assigned to: | Robert Oostenveld |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Marcel Zwiers - 2010-09-16 11:28:57 +0200
Problem: The peerlist is not updated/erased if the peer-threads are already running (or something along that line) Test: >>clear all >>peermaster, peer('peerlist') >>peermaster, peer('peerlist') This wil give a number of peers the first time, but the second time it gives only one peer
Marcel Zwiers - 2010-09-20 22:24:42 +0200
Since peer now moved to a private folder, this bug can best be reproduced by: >>clear all >>peermaster, peerlist >>peermaster, peerlist The first peerlist produces a list with all peers (as expected), the second peerlist contains a list with only one entry, i.e. the master.
Robert Oostenveld - 2010-09-21 17:24:53 +0200
the problem was that the allowuser/host/group option would cause the peerlist to be erased (and then slowly built up again once the new discoveries come in and are checked against the access restrictions). I have solved it similar to starting the threads: only update the allowxxx if needed, and if so, do a 1.5 sec pause see revision 1744
Robert Oostenveld - 2011-01-05 11:56:57 +0100
selected a long list of resolved bugs from roboos and changed the status into "RESOLVED"