Re: bugsweb cronjobs
| From: | Maciej Sobaczewski | Date: | Wed, 31 Dec 2014 05:48:13 +0000 |
| Subject: | Re: bugsweb cronjobs | ||
| References: | 1 | Groups: | php.webmaster |
| Request: | Send a blank email to php-webmaster+get-20453@lists.php.net to get a copy of this message | ||
Hello Ferenc,
thanks for fixing it. More and more people are providing feedback and it will definitely help us with the bugfest. I have another idea/question by the way. What about bugs with Spam status? Are they deleted in any automated way? If not, I think it would be good to add it to weekly cronjob tasks. I do not see much sense in keeping them forever and if we're afraid of deleting real reports, we can remove only Spam reports which are more than week old.
What do you think?
Best regards,
Maciej.
W dniu 2014-12-30 o 12:10, Ferenc Kovacs pisze:
Hi, yesterday I've just realized that there are two bugsweb related cronjobs which aren't running for a while (probably since the last or second-to-last server-move): web/bugs.git:scripts/cron/email-assigned web/bugs.git:scripts/cron/no-feedback I've fixed the scripts, and executed manually. The no-feedback went well, but it seems that we need to tweak the sendmail settings on the bugsweb machine (or whitelist that machine on our mx), because we got a bunch of too many connections/too much mail errors from smtp.osuosl.org when trying to deliver ther mails to the @php.net addresses. I will be adding this two crons to systems.git:boxen/sgrv20.php.net for WEEKLY so that we won't forget to set up the next time when moving bugsweb to another machine.