It's a new year and a great time to review what you're doing right and not so right in your Unix career. Time to commit to an effective to do list!
Need a way to make connecting to lots of servers using different settings and usernames easier? Look no further than the ssh config file.
Whether your aware of it or now, copyrighted or pornographic material on your work or personal computer can land you in jail or in the poor house.
If you get a secret thrill out of a well crafted Perl one-liner, but only have a few that you can pull out of your mental pocket and use, this book may be just what Santa should be leaving under your tree!
Sometimes what seems like the simplest of questions can have you scrambling for answers. Today's seemingly simple question is "How can a bash script identify its own location?"
Sorting data numerically and alphanumerically isn't generally much of a challenge on Unix systems, but sometimes .5 is smaller than .11.
Last week's post provided some tips and tricks for debugging scripts. This week's provides some even better ones!
All kinds of things can go wrong with your shell scripts, but they don't have to. Let's look a some debugging tips that can help ensure your scripts run the way you intend.
The kill command provides a lot more functionality than just terminating processes. You can use it to send any of more than 60 signals to processes and what happens next depends on the signal, the process and maybe even your settings.
It's easy to find files on Unix systems. You can find them by almost any criteria that you can imagine. The bigger challenge is deciding how to describe what you're looking for and deciding what to do with the files once you find them.
