546
edits
Avdump: Difference between revisions
→Autocreqing: sessions per ip
Karasuhebi (talk | contribs) m (→Usage) |
Epoximator (talk | contribs) (→Autocreqing: sessions per ip) |
||
| Line 84: | Line 84: | ||
* Communication between client and server is ''one-way'' (except session init/refresh); the client does not receive any confirmation for sent data. This means that there is no guaranty that all the dumps you send will arrive at the server and stored in the database, and there is no way to check this. | * Communication between client and server is ''one-way'' (except session init/refresh); the client does not receive any confirmation for sent data. This means that there is no guaranty that all the dumps you send will arrive at the server and stored in the database, and there is no way to check this. | ||
* Sessions are based on ''ip+port''; check your firewall and router settings to make sure the port is not changed (NAT/whatever). Use <tt>-port:nnnn</tt> to override the default port avdump use. | * Sessions are based on ''ip+port''; check your firewall and router settings to make sure the port is not changed (NAT/whatever). Use <tt>-port:nnnn</tt> to override the default port avdump use. | ||
* It is possible to run more than one instance of avdump at once, but not more than three will work ok. At the moment ''only three sessions per ip is allowed by the server'', meaning the fourth instance will terminate the first. Also, if you suffer under [http://en.wikipedia.org/wiki/Network_address_translation NAT], running more than one instance will make it worse. | |||
* There is no direct connection between data sent to AniDB and creqs generated. The data received will just be stored for later processing. There is no way to check the current status for a dump. Usually, it should take ''at least 48 hours'' from the moment you dump a file till the data actually changes. If any irregularities occur, or when there is too much data pending, it will take more time. | * There is no direct connection between data sent to AniDB and creqs generated. The data received will just be stored for later processing. There is no way to check the current status for a dump. Usually, it should take ''at least 48 hours'' from the moment you dump a file till the data actually changes. If any irregularities occur, or when there is too much data pending, it will take more time. | ||
* The creqs generated will report the user who sent the data first (for a specific file) as the creqer. | * The creqs generated will report the user who sent the data first (for a specific file) as the creqer. | ||