aMule Bug Tracker - aMule |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000303 | aMule | Servers | public | 2005-02-20 18:13 | 2005-02-22 03:50 |
|
| Reporter | grin | |
| Assigned To | Kry | |
| Priority | normal | Severity | tweak | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | |
| Platform | AMD K7 (i386) | OS | Debian GNU/Linux SID | OS Version | actual |
| Product Version | 2.0.0-rc8 | |
| Target Version | | Fixed in Version | SVN | |
| Fixed in Revision | |
| Operating System | |
|
| Summary | 0000303: "Too many files republished by your client software. Please upgrade it." |
| Description | It seems some server thinks rescanning should not cause the whole bunch of files to be republished again (probably with the same hash, but I am not familiar w/ protocol) causing the funny message in the subject, kicking AND blacklisting my IP for several hours.
|
| Steps To Reproduce | share 300+ files, move some between shared dirs, rescan. probably not all servers kick you, and possible that you should do several rescans in a given (unknown) timeslot.
|
| Additional Information | razorback2 did that, for example.
|
| Tags | No tags attached. |
| Relationships | |
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2005-02-20 18:13 | grin | New Issue | |
| 2005-02-20 19:11 | phoenix | Note Added: 0000655 | |
| 2005-02-20 19:11 | phoenix | Status | new => confirmed |
| 2005-02-21 23:15 | phoenix | Status | confirmed => assigned |
| 2005-02-21 23:15 | phoenix | Assigned To | => Kry |
| 2005-02-22 01:59 | Kry | Status | assigned => resolved |
| 2005-02-22 01:59 | Kry | Fixed in Version | => CVS |
| 2005-02-22 01:59 | Kry | Resolution | open => fixed |
| 2005-02-22 01:59 | Kry | Note Added: 0000661 | |
| 2005-02-22 03:50 | phoenix | Status | resolved => closed |