wiredfool

Archive for 2002

Tech Support Pricing

There are going to be changes around here. New tech support rules and all.

If I get an email and my response contains any of the following:

  • What were you doing?
  • What did you expect?
  • What url?
  • Can you reproduce it?
  • Look at the email I sent yesterday.
  • Look in the docs.
  • Can you get anywhere else on the net?

$50. If I get paged or called on my cell, $100. If I get woken up, called in on a weekend, or contacted before sufficient caffeine, $200. For Each Question.

If my response contains:

  • Here’s your problem:

$25.

If my response is:

  • Hmm, I’ve never seen that before.
  • Oh, that’s a bug
  • I think you can do that if you try this ugly hack.
  • I’ll have a fix for you in the next version.

Free. I like this sort of report. It’s interesting. It’s not sending back the same 5 questions over and over.

*** Ok

Enough bitching about work. Some days I can just hammer, some days it feels like my brain is over there in the puddle. It would really help if I could be ultra productive on grey days, and not productive on bright sunny days so that I could justify saying that I wouldn’t get anything done anyway, so I might as well be outside playing.

No comments

Shadow Fractal

shadow of a fern on the wall

No comments

DWIM

— I’m sorry to say that once again, the computer is doing exactly what you told it to do.

— AArgh!

No comments

Googling of History

While diving through my referer logs last night I went to Google to see where I was in a search. Of course, I was there, but so was a bit of ancient history. So ancient that it’s part of my black period.

http://associates.userland.com/ericSoroos/1999/09/23

A manila site that Brent made for me as part of one of the early manila demos.

And not only is it still up, but it’s the #5 hit for “Omar Torrez” on Google. I’m beginning to think that their ranking engine isn’t all that it’s cracked up to be if it’s elevating my posts like that. Of course, this post is probably going to elevate that one.

No comments

Targeted

Danger!  Looming Targets.

No comments

You are Here

the earth, from afar.

http://earthobservatory.nasa.gov/Newsroom/BlueMarble/

Has links to images of the earth at a full resolution of 21000 pixels square. Now I need a bigger desktop to take advantage of them.

Nasa – providing cool desktop pictures since before the GUI.

No comments

Software inspiration

This is how wierd software gets written.

I’m sitting on the couch with a laptop. The radio has changed to a silly talk radio program. It has a remote control, which is across the room.

I have mp3’s on the laptop, an airport card, and an IR port.

I want my new laptop to be a remote control. To save me walking across the room to hit a single button.

Possible approaches:

  • The linux box on the desk has mp3s too, and it’s sound card is connected to the stereo. It’s running a webserver. It also has all the standard linux tools.
  • The laptop has an airport card, ir port. An OSX remote control for the amp & cd player? An airport card plugged into the tape 2 input?!
  • A cgi on the webserver on the linux box.
  • My old radio userland hack, brought up to speed with the latest version.

Google hasn’t found anything appropriate. Maybe I should just get up and hit the button.

No comments

ok, one picture

hi, my url is...

No comments

Off to dinner

Off to the seattle webloggers unite dammit dinner.

If you’re there, I’ll see ya. If not, I’m sure there will be pics and whatnot.

*** Later

Sorry, no pics. Guess you had to be there.

No comments

Frontier/OSX Server Management

***in progress. Please don’t link until this notice is removed.

Taken in part from a series of my posts to the frontier-osx discussion group, updated to current practice. This is the collected knowlege of running several Frontier/OSX servers for the last 6 months. The servers run the gamut from Manila/Apache machines to heavily loaded app servers running custom web apps.

System Coordination

The idea behind system coordination is for individual frontier installations to be as independent from each other and portable from machine to machine as possible, so that any two installations could reside on the same physical machine if necessary.

  • File System Layout

    Due to Frontier’s dependence on absolute pathnames, all of the installations need to have consistent but different paths. My setup has a partition creatively named ‘Frontier’ on each machine, with all of the installations having a recognizable name within that (I.e. BetaOSX, DeployOSX, etc.) The frontier executable in each folder is renamed to correspond to the installation, without special characters or spaces. This allows for easy starting and stopping of each instance from the command line. (e.g. open /Volumes/Frontier/BetaOSX/betaosx opens my beta instance.)

  • Port Forwarding
    – or how we don’t need to be root

  • Other System Services
    -email, apache, bind?

    Backup Strategies

    I backup frontier installations, but not the os. I believe that the combination of moving installations from machine to machine and relatively quick OS installs makes OS partition backups unnecessary.

  • Installations that need to be restarted every night

    My webapps use enough memory that Frontier needs to be restarted on a daily basis. On older machines, some of the images use enough space that additional copies of all of the guess databaese aren’t feasable. Backups are done with the following

    1. Frontier is asked to save all it’s databases and quit, via an XML-RPC request.
    2. After Frontier quits, rsync is used to copy the databases to a backup server.
    3. Frontier is then restarted using the open shell command.

    The downside of this approach is that there is some unnessary downtime while the databases are copied to the backup server. Using rsync reduces the downtime below what would be necessary using a straight frontier copy by a factor of 2 or more in my tests. On the other hand, only one copy of the databases is required on the machine, and since Frontier is not running at the time of copy, you are gauranteed that the databases will be in a consistent state in the backup.

  • Installations that don’t need to be restarted
    I have found on my servers that Manila only installations do not need to be restarted every night. Memory usage on these apps approaches a steady state after several days of usage. This may indicate somewhat lightly loaded systems, but they’re stable so I don’t worry to much about it.

    I am using a modified version of the mainresponder guest database backup script that keeps exactly one complete copy of all the databases in the backups folder. A callback after this runs triggers rsync to copy the databases to the backup server.

    System Monitoring

  • Heartbeat monitoring
    – is it down

  • Process hang monitoring & restart.
    – have you hit the tcp bug?

    No comments
  • « Previous PageNext Page »