Bug#459910: [Popcon-developers] Bug#459910: please randomize the submission time (to prevent to DDoS popcon.debian.org)
On Wed, Jan 09, 2008 at 02:40:53PM +0100, Holger Levsen wrote: package: popularity-contest severity: important x-debbugs-cc: debian-publicity As discussed on irc this is because all clients hammer popcon.debian.org on the same day at the same time (in their local timezone at least) once a week, so many submissions get lost. Is it possible to get more data on this issue, like the relevant apache logs ? I suspect the issue is with the bandwidth rather than with the number of concurrent connection. Thanks in advance, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#459910: [Popcon-developers] Bug#459910: please randomize the submission time (to prevent to DDoS popcon.debian.org)
Hi, On Wednesday 09 January 2008 22:20, you wrote: As I read the patch, this will make the popcon cronjob run for up to one hour, thus delaying the other cron.weekly scripts... If I'm right, I consider this patch not good enough ;) I'm not sure it will delay the other jobs, but I figure that if they waited for a week, they can handle waiting for an hour. That's not my point. These scripts used to run at a fairly predictable time, which this patch changes, which might break unrelated software. Thats my concern (for a stable update, for sid, it's less an issue.) But obviously I'm no stable release manager :-) Martin, can you please comment on this. regards, Holger pgp7YsL1Z1rSo.pgp Description: PGP signature
Bug#459910: [Popcon-developers] Bug#459910: please randomize the submission time (to prevent to DDoS popcon.debian.org)
[Holger Levsen] As I read the patch, this will make the popcon cronjob run for up to one hour, thus delaying the other cron.weekly scripts... If I'm right, I consider this patch not good enough ;) I'm not sure it will delay the other jobs, but I figure that if they waited for a week, they can handle waiting for an hour. And besides, there is no guarantee on when the cron job will run, as there is no upper bound on how long a cron job will take. So I believe it is good enough, but I welcome patches. :) Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
