Author name: Dan Langille

The beta website is no longer updating. It was behind by 153 commits and rising. I suspect the poor old box, with just 2GB of RAM cannot keep up with the demands of frequent svn up, while being an imaps server and a mail server. It may be time to find a new location for

I’m thinking of a status page. It will hold: Are incoming messages being processed? How many messages are in the incoming queue? How many messages are in the retry queue? How many messages have been processed this calendar day? Anything else you want to see?

A recent post by Abbe in the Website Feedback forum indicates that the vuxml processing has a bit to be improved. When I looked, prod differed from beta and dev. This could be as simple as a missed processing of vuln.xml. I re-ran the script, and the marked commits on prod then agreed with dev

FreshPorts has been using a chroot solution for some over a year. I now want to do that from within a jail for my development environment. Why am I jailing myself? Because I can. I want to keep my development environment separate and away from other similar developments. It’s just easier that way. NOTE: this

I upgraded my development copy of FreshPorts and ran into a problem. I kept seeing this in the logs: Jun 26 11:30:15 ngaio FreshPorts[37555]: sleeping after svn up failed for (/wdc/dan/PORTS-SVN ” 321793) Jun 26 11:34:25 ngaio FreshPorts[38219]: sleeping after svn up failed for (/wdc/dan/PORTS-SVN ” 321794) Jun 26 11:02:09 ngaio FreshPorts[30361]: sleeping after svn

After a little bit of work, prompted by koobs, I’ve made the following code changes. Lines 8-10 added a time value to the top of the page. This was intended to let the user know when they last refreshed this page. Lines 18-20 let me know how long it took to generate a given page.

It’s one thing to identify a bug. It’s another to clean up the data corrupted by that bug. Fortunately, FreshPorts takes its data from the FreeBSD ports tree. This makes it rather straight forward to clean up most data issues; you just refresh the database from the ports tree. Case in point: a recently found