MisterX Tech

In trying to uncover the version of a CLI tool I uncovered this small Easter Egg.


# nbd-client -v
nbd-client: unrecognized option '-v'
E: option eaten by 42 mice


Just a quick note for others to enjoy…

Here is a real error I got after making a system config change recently. Can anyone guess what that change might have been. To give a little hint I got this on a new session opened up in screen on the system that had the change.

[I have no name!@*****]>ssh ******
You don’t exist, go away!

Customer had started a fsck and didn’t set it to auto fix issues. Got into the check and , after several minutes, found the need to hold the “Y” key permanently. Since he was ready to eat lunch I hooked him up with some ghetto engineering.

Was troubleshooting a coding issue for a customer the other day when I noticed the number of requests currently being processed. I am going to write about this in the coming days. Basically there was a code issue (we do not support code for this customer) that caused a large number of “sleep” states in MySQL as well as a huge number of ‘W Sending Reply’ states in Apache.

Current Time: Thursday, 11-Feb-2010 11:47:54 CST

Restart Time: Thursday, 11-Feb-2010 09:17:12 CST

Parent Server Generation: 0

Server uptime: 2 hours 30 minutes 41 seconds

Total accesses: 226733 – Total Traffic: 10.8 GB

CPU Usage: u1812.56 s80.08 cu.04 cs0 – 20.9% CPU load

25.1 requests/sec – 1.2 MB/second – 49.8 kB/request

1337 requests currently being processed, 113 idle workers

From a single “badmail” folder on a Windows Server 2003 box. Amazing how bad script writiers are as almost all of these were related to no “From” being set in the script.

This Winzip install is on the same fragged Server 2000 box in the last post. This screen shot was taken Jan 7th 2007 but sadly I cannot get a new shot as a overzealous engineer uninstalled winzip last week for some strange reason.

What do you think ?

This was a VERY old Server 2000 install that had been forgotten about. Seems time wasnt nice to the filesystem…or maybe the Sysadmin was a sadistic BOFH who is into filesystem S&M ?!