Update for August 6, 2001

Currently uptime.openacs.org is being moved to point to this server. As DNS spreads out today people should be able to access it. Once DNS has made its happy away around the 'net I'll made the name changes though out the site and add they OpenACS logo. Due to the server situation with openacs.org this move was speed up a bit. I will always keep uptime.alal.com as a backup name for this just incase of possbile DNS problems.

In addtion, I added some code that Tom Jackson posted on the AOLserver mailing list to record Code Red Incidents. I have set it up with some minor modifications so I can watch who STILL have not patched their servers. Almost like a wall of shame.

Update for July 16, 2001

I added some code to check and make sure that the server and talk to the Internet before checking hosts. I have a few things to clean up and will be releasing that code shortly.

Update for June 12, 2001

Okay, I finally have clean things up a bit and I'm fairly happy with things working. If anybody sees any problems, please but them out to me.

While I would still like to "standardize" the SQL to NOT rely on one DB, it think the first two things I will be adding will be:

• A check to make sure the servers connection is working
• I'm going attempted a "ping response" time for each successful grab. Won't be the BEST measurement, but might be helpful
• Personally, I think I'm going to make this into a OpenACS module so I can use the user permissions there

After that I'd like to starting looking at the possibility of distrubuted uptime mainly just to see if it can be done.

Read This Update for June, 11 2001

There are two things I should never do on a Friday:

• Attempted to quickly "port" anything releated to SQL
• Post code

Looking at what I did, I notices I did some really "bad things". Ugh. Tonite I'm going correct my mistakes. I think right now I'm gong to move away from use the DB for much of the time calculation and move to using ns_time and such. What I'd really like to do is move away from tying this down to one particular database.

End of June 11 update

This is a postgres version of Uptime, which Arsdigita run until June, 2001. This thread over at OpenACS's forums started it.

I download the uptime source code from Arsdigita and made a few changes and it currently is running at

http://uptime-pg.alal.com.

My Code currently at versioin 0.1.

The following was done to make it work:

• Ported the data-model.sql to postgresql and grabbed to postgres.sql data model from the OpenACS to get some of the "oracle-isms" that are required. SQL data models currently in use.
• You need Phil G's utilites.tcl for this to work.
• I change the director structure around a bit, mainly is was a bit more familar with it. The private TCL library is no longer under the web root.
• Removed some of the "oracle-isms" from the .tcl code. unique -> distinct. Changed all sysdate to sysdate(), etc.
• There are still a fix issues with computing times, etc. but it is working.

The OpenACS groups has a working version also, but I've yet to see the code. Once I go, I'll see what can be merged together (i.e. most of my stuff will be wrong and gone *smile*).

A couple ideas for uptime (my own and from others):

• Make the code more DB indepentant and create data models for Sybase, Adabas, etc.
• Intergrate the postgres data model and tcl node in OpenACS as another feature of OpenACS community sites.
• Distributed servers across multiple servers. This would be quite an interesting hack.

At some point, I'll move this information to a better location and make the source/cvs archive available. I'm not sure what the OpenACS people are going to do just yet and I don't want to step on any toes :)