Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • by vek (2312) on 2002.04.17 13:18 (#7185) Journal
    Are others reaching 'Camelot Naturals' when attempting to go to perlbox.org or is it just me? The DNS I'm using must be somewhat confused methinks :-)
  • Methinks the /. effect took down the server. It's still down as of 0700 CST.
  • Gone. The front page is blank, and all the subdirs you see listed on the google cache return 404. (And a Cobalt Raq 404 screen to boot).

    Oh Well.

  • by scmason (3055) on 2002.04.21 4:00 (#7322)
    Hi, Sorry that the site was down, but it seems that perlbox.org received so many hits (10,000 unique ip's in 2 hours) that it kept crashing the raq it was on at hostgo.com. This was due to a tremendous response to an article posted on slashdot.com. I have moved the site to an rs6000 running SuSePPC at the lab where I work at the University of Montana. The site is up, and very capable of handling any traffic thrown at it.

    I am interested to see what the consensus here is, the conversation at slashdot degenerated into a "perl is too slow for that" and "you should spend your time on more productive tasks" and "java is better than perl" type thing.

    I would appreciate any feedback! Anyone who wants to contribute some time and coding, there is an interest out there in this project. It's moving like hotcakes! I have been averaging around 400 downloads a day for the last three days.

    scmason
    me@perlbox.org