I like to know how long each of my boxes have been up and running. I really don’t care so much about Windows PC’s, but I really like knowing how long my Linux boxes have been up. Notifications of uptimes are very nice, if a server goes down, I’ll get an email letting me know it’s no longer up and running.
Anyway, for the last year and a half or more I’ve been using The Uptime Project from MrEriksson. I don’t think the project is being developed or even maintained any longer, but it still works very well. All you need to do is get a username and password then download the client for your operating system.
But, I just wanted to point out that one uptime, for router.longren.org. It’s got an uptime of 155 days, almost half a year, by far the best uptime for any box I’ve personally owned. The neat thing about The Uptime Project is that it records reboots and total downtime.
Take note of this graphic. Notice there’s been 3,775,826 queries processed by that MySQL server in a little more than 5 days. Nothing too impressive right? Right.
We know MySQL can handle many more queries than that in a much shorter period of time. What amazes me is how well MySQL performs on the server it’s running on. The box hosting that MySQL server is an old HP. It’s got 1 Pentium II 400mhz processor with 128Mb of RAM. And it serves data to anywhere between 10 and 14 seperate PC’s at any given point in time. In addition to that, this MySQL server also provides data to a web interface that is used by 50 or so people. The MySQL server pumps out about 500Mb worth of data every day.
MySQL never ceases to amaze me in what it can do on less than optimal hardware.
Slackware 11.0 Release Candidate 5 is here. Lots of updates to existing packages. Not many packages were upgraded. Patrick is giving the scouts honor that this will be the last RC before 11.0 final.
Head on over to the Slackware Blog to have a look at the full changelog entry. Hopefully we will see Slackware 11.0 released sometime next week or maybe even by the end of the week since we’ve seen such a long RC cycle. I don’t think we’ve seen anything greater than RC2 since Slackware 9.0 or so. It’s been a while since we’ve seen this many release candidates.
Slackware 11.0 Release Candidate 4 is out! This release sees kernel 2.4.33.3 included as the default. Soon after RC4 was made, Patrick made another small update to the ChangeLog:
Sun Sep 3 19:59:47 CDT 2006
a/udev-097-i486-8.tgz: Fixed a missing ‘[‘ in rc.udev. Thanks to
guilherme for pointing out the error, and to J., who found the missing
‘[‘. (It had fallen off my desk and ended up under a table)
kernels/System.map: Forgot to gzip a bunch of these. Thanks, Steve’o.
This should definitely be the last RC before Slackware 11.0 final is released. In the past two or three Slackware releases (10.0, 10.1, and 10.2), we’ve only seen 2 or 3 release candidates. I suppose there’s a chance we’ll see RC5 this time, but I’m thinking this RC4 will be the last. Probably see Slackware 11.0 final within a week and a half or so.
Slackware 11.0 Release Candidate 3 is here!! The 2.6 kernel was moved from /testing/ to /extra/. What’s that mean? Not much really, other than it’s considered to be more stable since it’s now in /extra/.
I like to know how long each of my boxes have been up and running. I really don’t care so much about Windows PC’s, but I really like knowing how long my Linux boxes have been up. Notifications of uptimes are very nice, if a server goes down, I’ll get an email letting me know it’s no longer up and running.
