Well, if you follow my blog at all you’ve probably noticed a bit of a lull in posting and, while I don’t spend a whole lot of time talking about myself here I figured I’d take a moment to share why things have been slow lately.
The truth is things haven’t been slow lately. Blogging has been slow, but not other things in my life. Last week was my last week working as a DBA at Plymouth State University. It’s been fun there, but next Monday I start my new gig working for SunGard Higher Education as a Senior Technical Consultant-Oracle Remote Database Administrator.
In addition to being a higher level position with more potential for growth this position also gives me the opportunity to telecommute from my home in Concord, NH! Expect to hear more about telecommuting and adjusting to the change soon, but suffice it to say I’m fairly excited to go from a 45 minute commute to a 45 second commute.
So after wrapping up my first book I took this week off to get back on track with my second book, a goal which was going well up until an incident happened yesterday with a glass of water and my only Mac keyboard. For the record, don’t try to blow-dry your keyboard.
So I’m back on line with a brand new keyboard and busy as hell writing and getting my home office set up. If you’ll bear with me just a bit longer I’ve got some great articles coming including a hands-on review of the USB Missile Launcher (yes I have one and I’m not afraid to use it.)
Whenever a command or shell script completes successfully, it sets a hidden status code of zero. If the command is unsuccessful, it sets a nonzero hidden status code. This completion status code is known as the exit status. The exit status of the last command or script that was run is contained in the special shell variable, $?.
Most of the time we never look at this value and instead check to see if the command did what we want or look for errors in the output of commands. In a shell script, however, we may want to check the exit status to make sure everything is going OK. The exit status of the last command can be displayed as follows:
example1.fil example2.xxx examples test.bsh umask_example.fil
$ echo $?
$ ls *.txt
ls: *.txt: No such file or directory
$ echo $?
The value of the exit code can then be used in a conditional statement or be transferred to another variable.
For more tips like this check out my book Easy Linux Commands, only $19.95 from Rampant TechPress.
Via Carla, here are three very good UserFriendly comics which aptly reflect my feelings on coffee:
UserFriendly is often good for a laugh. Hopefully they don’t mind me posting these cartoons here, their copyright notice is very explicit (and rather humerous!):
All images, characters, content and text are copyrighted and trademarks of J.D. Frazer except where other ownership applies. Don’t do bad things, we have lawyers.
UserFriendly.Org and its operators are not liable for comments or content posted by its visitors, and will cheerfully assist the lawful authorities in hunting down script-kiddies, spammers and other net scum. And if you’re really bad, we’ll call your mom. (We’re not kidding, we’ve done it before.)