Back to the main page.
Bug 768 - peermaster allowhost should not be case sensitive
Status | CLOSED WONTFIX |
Reported | 2011-06-17 23:25:00 +0200 |
Modified | 2011-09-09 15:47:56 +0200 |
Product: | FieldTrip |
Component: | peer |
Version: | unspecified |
Hardware: | PC |
Operating System: | Mac OS |
Importance: | P1 normal |
Assigned to: | Robert Oostenveld |
URL: | |
Tags: | |
Depends on: | |
Blocks: | |
See also: |
Robert Oostenveld - 2011-06-17 23:25:29 +0200
>> peermaster('allowhost', 'esi-svhpc2') >> peerlist there are 0 peers running in total (0 hosts, 0 users) there are 0 peers running on 0 hosts as master there are 0 peers running on 0 hosts as idle slave with 0 bytes memory available there are 0 peers running on 0 hosts as busy slave with 0 bytes and 0 seconds required there are 0 peers running on 0 hosts as zombie >> peermaster('allowhost', 'ESI-svHPC2') >> peerlist there are 8 peers running in total (1 hosts, 1 users) there are 0 peers running on 0 hosts as master there are 8 peers running on 1 hosts as idle slave with 44.0 GB memory available there are 0 peers running on 0 hosts as busy slave with 0 bytes and 0 seconds required there are 0 peers running on 0 hosts as zombie idle slave at public@ESI-svHPC2:1704, memavail = 4.0 GB, timavail = 24.0 hours idle slave at public@ESI-svHPC2:1710, memavail = 4.0 GB, timavail = 24.0 hours idle slave at public@ESI-svHPC2:1716, memavail = 8.0 GB, timavail = 24.0 hours idle slave at public@ESI-svHPC2:1717, memavail = 4.0 GB, timavail = 24.0 hours idle slave at public@ESI-svHPC2:1718, memavail = 8.0 GB, timavail = 24.0 hours idle slave at public@ESI-svHPC2:1719, memavail = 8.0 GB, timavail = 24.0 hours idle slave at public@ESI-svHPC2:1720, memavail = 4.0 GB, timavail = 24.0 hours idle slave at public@ESI-svHPC2:1721, memavail = 4.0 GB, timavail = 24.0 hours
Robert Oostenveld - 2011-08-31 17:27:43 +0200
I am closing this bug because the development on the fieldtrip/peer toolbox will be put onto hold in favor of the fieldtrip/qsub toolbox. The qsub toolbox is more promising for the DCCN as a whole and hence requires attention. The peer toolbox will remain available within fieldtrip, and external contributions to the code will be considered for inclusion. In the future, the development on fieldtrip/peer may be started up again and the bugs that I hereby close as "wontfix" can be revisited.