Work found
I’ve found work. Details here.
MSNPTC/1.0
MSNPTC/1.0 appears to be a poorly written spider bot. It has no concept of distributing requests. I am not the only person that thinks this: http://www.webmasterworld.com/forum11/2845.htm http://www.botsvsbrowsers.com/details/4800/index.html http://boardreader.com/t/Spiders_Crawlers_509179/MSNPTC_1_0_2849.html Let me demonstrate with an example: $ grep -c “MSNPTC/1.0” freshports.org-access.log 1975 $ grep “MSNPTC/1.0” freshports.org-access.log | head -1 219.142.53.25 – – [01/Nov/2007:16:52:00 -0400] “GET /login.php?origin=%2Fcommit.php%3Fcategory%3Dwww %26port%3Deventum%26files%3Dyes%26message_id
Checking archives for missing messages
FreshPorts is pretty good about not missing commits. It depends exclusively upon the cvs-all mailing list. If the message doesn’t arrive, it doesn’t get into FreshPorts. In the interests of increasing the complexity of FreshPorts, I’d like to validate the database against the cvs-all archives. Each commit generates one email message. Each email has a
Checking archives for missing messages Read More »
Sanity test failure reports no problem
Late yesterday, I noticed a couple of sanity test failures. What was interesting about these reports was the lack of an error message. I emailed the committer to let them know I was looking into it. There were two failures. The first against devel/aunit; the second against devel/florist-gpl. By the time you read this, the
Sanity test failure reports no problem Read More »
The RAM shortage fix
Here is the patch I just comitted which reduces the amount of RAM consumed. [dan@ngaio:/usr/websites/freshports.org/classes] $ cvs di -ub display_commit.php Index: display_commit.php =================================================================== RCS file: /home/repositories/freshports-1/classes/display_commit.php,v retrieving revision 1.8 diff -u -b -r1.8 display_commit.php — display_commit.php 10 Jul 2007 11:39:07 -0000 1.8 +++ display_commit.php 22 Oct 2007 17:22:23 -0000 @@ -87,19 +87,16 @@ $i=0; $GlobalHideLastChange
The RAM shortage fix Read More »
More RAM
I was scanning the error logs this morning, looking for anything unusual. I found it: [Mon Oct 22 12:31:10 2007] [error] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 512 bytes) in display_commit.php on line 91 I have seen this before, but could not recall where. I also could not
List the vulnerabilities for this port
The previous post was based on a question from Martin Wilke, who was looking for a vuxml entry against phpMyAdmin. We eventually found it. It had the wrong dates but it was found. Martin corrected the problem with a followup commit. This incident prompted me to make a couple of changes to FreshPorts with respect
List the vulnerabilities for this port Read More »
Vulnerabilities – finding them easily (vuxml)
This isn’t about detecting vulnerabilities. It is about finding vulnerabilities that others have already reported. Background reading: FreeBSD Porter’s Handbook: Keeping the community informed FreeBSD VuXML Here are the various vuxml pages provided by FreshPorts: The latest vulnerabilities are listed on the home page A complete list of all vulnerabilities by date A complete list
Vulnerabilities – finding them easily (vuxml) Read More »
Corrupted emails
FreshPorts encountered its first corrupted cvs-all email today. It handled it correctly. It errored out, put the emails aside in the retry queue, and sent me a notice. Af first, I thought the email had been corrupted on the way into my system. But after checking the above URL, I realised it was bad at
No more patching for MASTERPORT
Back in August, I wrote about patching the ports tree to cater for master/slave relationships. I am happy to report that this patch is no longer required. Instead of MASTERPORT, as provided by that patch, I can use MASTER_PORT, which is now part of the stock ports/Mk/bsd.port.mk. \o/ No more patching.
No more patching for MASTERPORT Read More »