Server "uptime" bragging

I recently saw a blog post about someone showing their server having an uptime of over 400 days, and wanting other readers to reply with some of their larger uptimes. Quite a few people obliged, and the numbers were in the hundreds of days. This made me think, "Is this really a "good thing" anymore?"

Some questions that come to my mind when I see servers with long uptimes are

1.) Are patches being applied? There are a lot of security and performance updates that are released within a year. Some may not be critical, but are you being responsible and diligent in keeping your server up to date and secure?

2.) Does the server need to be up for so long because it is a single point of failure for a critical service? Hardware gets cheaper and cheaper, and many services can be loadbalanced or clustered. With the popularity of virtual machines, even more so. If this service experiences a failure, will your customers or users notice? How long will it take to restore its functionality?

3.) Do you know if the server will restart correctly in the event something causes a reboot? This could be unexpected, like a hardware or power failure; or expected, like applying kernel updates. Over a long period of time, a lot of small changes can happen that could cause startup scripts to break, but would go undetected until you have to restart. Or, your hardware just might not want to go through a restart for whatever whacky reason.

I guess what I'm saying is, having regular maintenance reboots aren't a "bad thing." Yeah, it used to look cool to have a server up for 600 days, but I don't think it's really worth it now.

Free download of SnagIt (through 6/5/2009)

Some of you may like to take screen shots for documentation, blog posts, or other troubleshooting info exchange. One product I've used that is more useful than Ctrl+PrintScrn or Alt+PrintScrn is SnagIt. Until 6/5/2009 5PM EST, they are providing free download and registration key for their SnagIt 7.2.5.

http://www.techsmith.com/Covermount/covermount.asp?ID=8

Note this is for PC only, and is not compatible with Windows Vista.

Rumor: iPhone and SlingPlayer over 3G without Jailbreak

I've overheard a couple rumors that users have been able to use the SlingPlayer application with their iPhone over 3G (as opposed to Wi-Fi) without having to jailbreak their phone. Apparently, when they connected their iPhone using a Cisco VPN solution, they were able to use the SlingPlayer application. It got me thinking if this rumor is true, would this trick work with another type of VPN server that is compatible with the iPhone? Perhaps running a PPTP server at home, such as Poptop?

I haven't been able to confirm or deny this, since I'm not willing to pay $30 for the iPhone app, and I'm not sure if it will work with my original SlingBox, but I wanted to share for those that would be interested.

Monkey - House: A Big F-U to GoDaddy

Heads up to those that, like me, trust their domain registrations with GoDaddy.

Monkey - House: A Big F-U to GoDaddy

It's ridiculous what they can do when your domain lapses. I guess I got distracted by their advertising.

Getting the VMware Boot/POST screen

I was trying to re-kickstart an install of a Linux server in my VMware cluster, but I couldn't get the VMware Boot/POST screen so I could choose the PXE network install option. I also was having a rough time with my Google search queries to find the answer. Since I had a tough time finding it, I thought I would write it here, so if anything, I could find it again.

I had to modify my .vmx file for my virtual machine and add the line

bios.bootDelay = "10000"

The numeric value is the number of seconds the POST/Boot screen is shown. So in my example, this would be 10 seconds, which deceptively goes by pretty quick.

DNS and Asset Information

Saw this post at TaoSecurity today about using DNS as a tool for Asset Management.

http://taosecurity.blogspot.com/2009/02/asset-management-assistance-via-custom.html

It toys with the thought of creating custom DNS records that identify asset owners. It's an interesting thought that was partially used at my last job. Our senior sysadmin had an unwritten policy that any server added to our internal DNS would also need a TXT record that contained information such as the hardware serial number. I'm not sure how many characters a TXT record supports, but I'm sure you could add other info as well. If you weren't sure who the contact person for a server was, or where it was located, you could "dig servername txt".

Here's an example of a DNS TXT record entry.

http://www.zytrax.com/books/dns/ch8/txt.html

Man page reading tip

I usually keep my ssh windows pretty small, but it makes them a pain to read man pages. The way I read man pages now is using Google and finding man pages posted online. That way, it's as easy as reading any other web page.

For Linux, I use the search string (minus the quotes) "man linux command", and it usually pulls up the appropriate man page on http://linux.die.net.

For Solaris, I'll use the search string (minus the quotes) "man sunos command", since the syntax or switches of the Solaris command may be slightly different than the Linux one.

Another bonus is that commands and configurations in the "SEE ALSO" section are usually hyperlinked to the corresponding web entry. There are probably browser plugins or toolbars that will accomplish the same thing, but this is universal and lightweight.