To take a screenshot of the entire screen and save the image as screenshot.png, use the command:
$ import -window root screenshot.png*
To select an area to capture with a crosshair, use import without the -window option.
To take a screenshot of a specific area of the screen, use the -crop, option along with the dimension in pixels, for example:
import -crop 300X250
The import utility is part of the ImageMagick suite of tools.
Sometime you may want to find all files modified during the installation of a given package. This problem can be solved simply as follows:
echo temp > /tmp/afile # Install your package find /etc -newer /tmp/afile # Find files modified in /etc
A useful variation is to identify all files “accessed” during the execution of a given program. Often some files under /etc are accessed, and you need to know which ones. This can be done as follows:
echo temp > /tmp/afile # Run your program find /etc -anewer /tmp/afile
A sneaky variation is to find all files modified between time1 and time2. Let's use the times 2007-12-02 13:45 and 2007-12-04 01:30 as an example:
touch -t 200712021345.00 /tmp/file1 touch -t 200712040130.00 /tmp/file2 find /etc -newer /tmp/file1 -a ! -newer /tmp/file2
This works by using touch -t to set the modification date of the files to set a date range for use with find.
Do you have code for Linux written in Assembler, C, C++, FreePascal or any other native-compiled language that surfaces a Java JNI interface?
Have you had problems with crashes from time to time? It could be that your native code is improperly, from Java's point of view anyway, using signals. Even if your code is not explicitly using signals, the Run-Time Library (RTL) linked into your Java JNI Shared Object may be using signals “for” you.
The answer to your problems may lie in a Shared Object named libjsig.so that comes with later versions of Java. Basically, libjsig.so makes it easy to implement something called signal chaining that allows the Java JVM, and your Java JNI native code that uses signals, to interact with one another properly.
There are a couple ways to use libjsig.so, but one quick way to find out whether libjsig.so will benefit you is to use the wonderful Linux LD_PRELOAD capability discussed in the November 2004 issue of Linux Journal in the article “Modifying a Dynamic Library without Changing the Source Code” by Greg Kroah-Hartman (www.linuxjournal.com/article/7795).
To give it a go, in a bash shell, use the following technique to execute your Java application:
export LD_PRELOAD=/path/to/libjsig.so; java YOUR_JAVA_CLASS
For more information on libjsig.so try:
Signal Chaining: java.sun.com/javase/6/docs/technotes/guides/vm/signal-chaining.html
Revelations on Java signal handling and termination: www.ibm.com/developerworks/java/library/i-signalhandling/
Signal Handling on Solaris OS and Linux: java.sun.com/javase/6/webnotes/trouble/TSG-VM/html/gbzbl.html
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
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
- LiveCode Ltd.'s LiveCode
- 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