Linux Journal Contents #151, November 2006
Interview with Tim Bray
by James Gray
Tim Bray releases Atomic energy.
Caller ID with Asterisk and Ajax
by Mike Diehl
Want to do your call screening by Web page?
Migrating to Drupal
by Abhijeet Chavan and Michael Jelks
What drove Planetizen to migrate to Drupal?
Simple Web Sites Using DocBook, XML and CSS
by David Lynch
How to build simple content Web sites using DocBook XML and CSS.
Linux and Open Source in Telecommunications
by Ibrahim Haddad
What's good about being disruptive?
SMART (Smart Monitoring and Rebooting Tool)
by Albert Martorell
A smarter way to monitor services.
A Basic Text-Based Recording Studio
by Matthew Geddes
You don't need a fancy GUI to create a powerful recording studio.
Building and Integrating a Small Office Intranet
by Dave Jones
Add server-side credentials to the LAMP stack.
Add Web Porn Filtering and Other Content Filtering to Linux Desktops
by Donald Emmack
Station DansGuardian over incoming Web content.
Reuven M. Lerner's At the Forge
Marcel Gagné's Cooking with Linux
The Dynamic Web: for Those Who Like to Watch
Dave Taylor's Work the Shell
Analyzing Log Files Redux
Mick Bauer's Paranoid Penguin
Running Network Services under User-Mode Linux, Part I
Jon “maddog” Hall's Beachhead
A Small Conference
Doc Searls' Linux for Suits
The Search for Terrestrial Stupidity
Nicholas Petreley's /var/opinion
In Every Issue
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!
- Stunnel Security for Oracle
- SourceClear Open
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Tech Tip: Really Simple HTTP Server with Python
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
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