Solaris users: Blastwave.org needs our help!
A while back I recommend BlastWave as a great source of pre-built binaries for Solaris. Their service has saved me huge amounts of time.
Sadly, they are running low on funds. It's expensive to keep a high-profile web site like this up and running. Corporate donors are particularly needed.
I just donated $50. I hope you consider donating to them too. Otherwise, in less than 48 hours, they may have to shut down.
Katrina and the waves
Hurricane Katrina is wrecking havoc and our thoughts and prayers go out to everyone affected.
While technical concerns are minicule compared to people's homes and families, reading this Slashdot article reminded me of the fact that I have done business with two different companies that have NOCs in Florida. In both cases I asked my contact, "Do you really think it's a good idea to have a NOC in a place that has so many environmental disasters?" and both times I was assured that this would never, could never, possibly ever be a problem.
In one of those cases involved my (then) own employer. It was a company large enough that I was in a different division and had no real influence on their decisions, and I was probably talking to the wrong person anyway. Alas, this seems to be my week for saying "I told you so."
For all of you that haven't yet built a data center, let me quote from Chapter 17 on building a data center:
Selecting a town and a building is typically out of the hands of the system administration staff. However, if the data center is to serve a worldwide or significant geographic area, and it will be located in an area that is prone to earthquakes, flooding, hurricanes, lightning storms, tornados, ice storms or other natural disasters that may cause damage to the data center, or loss of power or communications, you must prepare for these eventualities.
And for those of you that are in Katrina's path, I hope you keep safe and dry!
Ethical question: domains
A friend proposed this delemma:
Company has about 20 domains registered that are "parked" (owned but never used). They are combinations and permutations of product names that were considered but not used, or were selected but are more like internal code names that might be mentioned in PowerPoint presentations but aren't really products.
When they were registered it was presented as the most important thing in the world to get them registered. It wasted about half a day total when you consider the time I spent registering them, paying the bills, and all the communication back and forth about which were available or not.
Now it's time to renew them. If I do nothing they will expire and there is very little risk that anyone will ever notice. If I ask the right people, it will waste another half a day of my time debating their value and then renewing them, processing the bills, etc. If I let them expire and then try to get props for saving money, I run the risk of rubbing someone the wrong way for not asking permission.
The company is currently putting a big emphasis on not wasting money. So if I demonstrate that I saved $100 that would put be in a good light. However, it will cost the company more than $100 in my salary to find out if I have permission to not renew them.
What do you think he should do?
Run "sed" on your cut&paste buffer
Two little known Mac OS X commands available from the Unix shell ("Terminal") are pbpaste and pbcopy. They are used for retrieving and sending text to the paste buffer. pbpaste outputs the cut&paste buffer to stdout. phbcopy reads stdin and puts it into the cut&paste buffer.
The more I use these commands the more new ways I find to use them. Read on.
Basic cutting and pasting:
Let's start with the basics.
Reading and writing the cut&paste buffer:
To store something, just send it to pbcopy's stdin.pbcopy <file.txt
Easy. Right? Now go into TextEdit or MS-Word and paste (CMD-V). The file gets pasted. It's much more accurate than selecting the file from the screen. No worries about missing the first or last line, etc.
Now do the opposite. Select a bunch of text in your favorite application and copy it into your cut&paste buffer. (CMD-C) Want to save it to a file?
pbpaste >newfile.txtThe entire buffer is there. Check it and see.
Paste pipeline into buffer:
Ever been working in the Unix shell and wanted to take the output of one command and paste it into an application? (For example, paste into MS-Word for a book you are writing). That becomes a lot easier:
ls ????-*-IRR.txt | pbcopyNow the output goes into the paste buffer.
If we want to see the output too, we can either run the command twice (once with the "|pbcopy" and once without) or we can simply add a "tee" command:
ls ????-*-IRR.txt | tee /dev/tty | pbcopy
Here's a longer command line:
ls | tr '[A-Z]' '[a-z']' | sort | pbcopyWhatever you do on the command line, you can put the output into the cut&paste buffer by ending the line with | pbcopy.
Paste into a pipeline:
What about the other way? Ever have some really great stuff in your cut&paste buffer but wish you could see it sorted?
pbpaste | sortHere's a better one. How many times have you been looking at a huge Cisco router configuration and wished you could find all references to a certain IP address? I used to copy the configuration into my cut&paste buffer then paste it into NotePad or TextEdit, and use "find". However, sometimes I needed to do a complicate search that could only be done with egrep. Then I had to save the file and grep from the command line. Now its a lot more simple:
Find 10.1.10.1:
pbpaste | grep 10.1.10.1or find 10.1.10.1 as a whole word, don't treat "." as a wildcard:
pbpaste | grep -F -w 10.1.10.1or maybe we just want to count the number of lines:
pbpaste | grep -F -w 10.1.10.1 | wc -l
"sed" your cut&paste buffer:
Here's my favorite. Today I had the following string in my cut&paste buffer:
access-list 101 permit tcp object-group OSXservers any eq ftpThis is a rule for access list 101 on my PIX firewall. Now what I wanted to do is paste that into access list 202. Sure, I could retype it. I could even paste it without the ENTER at the end of the line, and use my cursor keys to get to to "101" and change it to "202". However, that's a pain and it is also error prone, epecially considering the way a PIX can mishandle command line editing on long lines leaving you without a clue about the real location of your cursor.
Therefore I did this instead:
pbpaste | sed -e 's/ 101 / 202 /g' | pbcopyTo test my work, I looked at the buffer:
$ pbpasteIt worked! W00t! Thus I pasted it into my PIX and was on my way.
access-list 202 permit tcp object-group OSXservers any eq ftp
More info:
The system is smart enough to tell ASCII text from RTF from EPS. The man page has more information.
Heard any good rumors lately?
You may have heard a rumor that I'm working on a book called "The Art of Time Management for System Administrators." However, have you heard the big suprise? We've licensed cartoons from User Friendly for the book.
Now I just have to find someone to write the forward. Suggestions?
LISA Blog
David Blank-Edelman, chair of LISA2005 has created a blog so you can follow what it takes to create a conference. Check out LISA Conference Blog
Don't brag about overextending yourself
System administrators often find themselves over-extended, skipping vacations, and so on. I often find myself coaching people on ways to set limits, have fruitful and relaxing vacations, and so on.
Someone recently forwarded me this link which talks about the difference between US and EU attitudes about work.

