Saturday, April 11

Cool

Ars Munuvica

Just browsing Ars Technica, as is my wont of a Saturday evening, when I find....  This:
One such Taliban propaganda site billed itself as the official voice of the "Islamic Emirate of Afghanistan," and regularly provided enthusiastic (if highly dubious) reports of successful attacks on coalition troops in the region. It was pulled offline last week after conservative blog The Jawa Report urged readers to complain to companies "unknowingly and unwittingly giving the Taliban some of the necessary tools they need to prolong the war." (The blogger also provided Taliban officials' contact emails, and suggested signing them up for sheep porn.)

Posted by: Pixy Misa at 07:24 PM | Comments (8) | Add Comment | Trackbacks (Suck)
Post contains 102 words, total size 1 kb.

1 Heh.â„¢

Posted by: Old Grouch at Saturday, April 11 2009 11:55 PM (fx4N3)

2 Did you port us to the new hardware today?

Posted by: Steven Den Beste at Sunday, April 19 2009 10:42 AM (+rSRq)

3 No, I got hit by a bus instead. sad

Minx tied itself in a knot for a little while, and I had to smack it.  So if you noticed any downtime, that was it.

Unfortunately, there's still no solution forthcoming for the network driver issue, and I haven't had time to roll my own.  So it will be at least another week before we can move in to our new home.

Posted by: Pixy Misa at Sunday, April 19 2009 08:26 PM (PiXy!)

4 When I say "hit by a bus"...  Well, the main production server at work crashed, let's see, four times in three days, and I had to pick up the pieces.  And the database got corrupted (MyISAM problem) and locked up (InnoDB problem), and replication choked a couple of times.  And I was already scheduled to implement some major software updates over the weekend.

So, yeah, bus.

Posted by: Pixy Misa at Sunday, April 19 2009 08:30 PM (PiXy!)

5 Then the major software changes clashed, and then we had another database issue, and I spent hours trying to find the bug in my code before I worked out that it wasn't a bug in my code, and then replication choked again, and then there was a bug in my code after all, only different, and I would have found it three days earlier if it hadn't been for all the fireworks.

Bus.

Posted by: Pixy Misa at Monday, April 20 2009 03:27 AM (PiXy!)

6 Seems like there's been a lot of shrine desecration going on!

Posted by: Steven Den Beste at Monday, April 20 2009 03:31 AM (+rSRq)

7 You have my sympathy!

(Only thing I have that I can complain about is the discovery - two days before taxes were due - that the spreadsheet we’ve been using to adjust individual withholding for my business had a mistake in it, so the 940s didn't match the W-2s.  Nuisance.)

Posted by: Old Grouch at Monday, April 20 2009 09:37 AM (92326)

8 The server crashed again, and this time corrupted the index on one of our largest tables.  It would take hours to rebuild, but fortunately I just got replication completely up to speed, so I'm dragging the table back across from the replica as fast as it would go.  Two days ago the replica was running a day behind, so we would have been stuffed.  Sometimes not everything goes wrong all at once...

On the other hand, I have a replacement server arriving today.  If that had been ready first, we wouldn't have had this crash. neutral

Posted by: Pixy Misa at Tuesday, April 21 2009 12:13 AM (PiXy!)

Hide Comments | Add Comment

Comments are disabled. Post is locked.
48kb generated in CPU 0.0496, elapsed 0.139 seconds.
56 queries taking 0.1302 seconds, 345 records returned.
Powered by Minx 1.1.6c-pink.