Database Flooding

[Antonio]

Originally Posted by ChristianB

Hi Antonio,

can you make this available on github.com? I had to tweak your script to get it working on debian and would also like to include a cookie to the web requests to have higher limits on queries per hour. Having this in source control should make it easier to implement those changes and keep it working on windows and linux.

Done and available at https://github.com/AntonioPK/Fdb

Let me know if I've done anything wrong, since I had never used GitHub before.

[ChristianB]

Originally Posted by Antonio

Done and available at https://github.com/AntonioPK/Fdb

Let me know if I've done anything wrong, since I had never used GitHub before.

Can you rename the file so it doesn't include the version number? Something like fdb_comp_evaluator.pl or so? Git takes care of versions and if you want to release a working version you change the comment in the script and also create a release/tag on github.

I would suggest that I clone your repository, make my changes and submit changes as pull requests. This way you can test my changes before accepting the pull request.

[Antonio]

Originally Posted by ChristianB

Can you rename the file so it doesn't include the version number? Something like fdb_comp_evaluator.pl or so? Git takes care of versions and if you want to release a working version you change the comment in the script and also create a release/tag on github.

I would suggest that I clone your repository, make my changes and submit changes as pull requests. This way you can test my changes before accepting the pull request.

Changes made and released as ver. 1.5.0

[Antonio]

Available at: https://github.com/AntonioPK/Fdb/releases/latest

Should now work on both Linux and Windows platforms without modification.

Thanks to ChristiaB for doing the majority of the work on this release

Changes since v1.5.0
•added unix shebang
•added $yafupath config variable to specify the path to the yafu executable. Note, if Fdb is not in the same directory as yafu, yafu.ini should be copied to the Fdb directory.
•added $fdburl and $fdbcookie config variable to support cookie based authentication in the future
•changed mixed tab/space indentation to tab indentation and some other small white space changes

[Antonio]

Available at: https://github.com/AntonioPK/Fdb/releases/latest

Changes since v1.5.1: -

• Corrected bug in 'no composites received' code, total count was not being incremented.
• Corrected a display bug when Factordb failed to respond to a composite request.
•
• All constants dependant on the maximum page rate allowed by Factordb.com replaced with variables.
• The value of these variables are calculated from the new variable holding the maximum page rate.
• This is additional support for changes introduced in version 1.5.1
•
• Modified 10 minute wait loops so that the user has to wait at most 1 minute before Ctrl-Q exits the code.
• Added log file option (-l): - Can now log data to Fdb.csv, a comma separated list consisting
  of composite size, number of prime factors found, time to factor (in seconds).
• Added auto increment for random offset (-a xx): - This is in addition to the maximum set by the -r option,
  each time a worker collision occurs the additional random offset will be incremented by xx (once the number
  of collisions exceeds 5% of the number of composites factored), it also invokes an automatic decrement of
  the additional random offset each time a collision does not occur.
  Suggested starting values: -r 10 -a 3
• 'Get composite' display has been modified to show the current maximum random offset (offset/maximum offset).
• Display of the count for each error type is supressed until the count for that error is > 0.

[schickel]

Looks like someone's spamming the DB again. There are bunches (well, 300+ right now, anyway) of 72-digit composites that look like this:

[schickel]

Another crapload of composites. The few that I looked at were just factors of random numbers around 62 digits and up, not even any particular form.