If you use ssh-agent and have scripts that use commands, such as ssh or scp, that need your ssh key, you may have had the experience of running your script only to discover that you never ran ssh-add to add your key to ssh-agent. So, you type the passphrase once to run the script, and then you have to run ssh-add afterward and type it again to add it to ssh-agent.
To avoid this, add a check to the top of your script to see whether your key is loaded. If not, load it, and avoid having to run ssh-add afterward:
if ! ssh-add -L | grep --silent '/\.ssh/id_.sa'; then ssh-add fi
The -L option of ssh-add shows what keys are added, its output is piped to grep to check to see whether your key is loaded. If it's not, ssh-add is invoked to add your key.
If you want to extract images from a PDF file, you can use the pdfimages program from the poppler package. To extract the images from an entire file, run the command:
pdfimages input.pdf image-root
If you want to extract images from a range of pages, you can use the -f and -l options to specify the first and last pages in the range. To extract the images from pages two to four, use the command:
pdfimages -f 2 -l 4 input.pdf image-root
Images are written to files named image-root-nnn.xxx, where nnn is an image number and xxx is the image type (for example, jpg).
If you have scripts that need to be run as root, you can check for this at the start of the script with:
if [[ $UID -ne 0 ]]; then echo "Must be run as root" exit 1 fi
If you use sudo, you even could restart the script with sudo if it was not run as root:
if [[ $UID -ne 0 ]]; then sudo -p "Restarting with sudo. Password: " sh $0 $* stat=$? exit $stat fi
The sudo command runs the script as sh $0 $*. The sh is included in case the script does not have the execute bit set.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Tech Tip: Really Simple HTTP Server with Python
- Doing for User Space What We Did for Kernel Space
- Rogue Wave Software's Zend Server
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide