Letters to the Editor
1. How come your January issue is on the Web and I still haven't received my December issue? Did it get lost in the mail or am I impatient?
2. Can you put more articles on-line for us paying subscribers? I paid my dues and feel like I am due the flexibility of reading online or on paper, please.
—RSVPAdam Holt email@example.com
1. The December issue was mailed one week late due to a problem at our printers, which set back printing, and therefore mailing, by one week.
The Table of Contents is posted to the WWW and Usenet as soon as an issue is sent to the printer; printing and mailing take another three to four weeks.
2. We are working on putting articles on-line, but our first priority is putting the magazine on paper. If we don't get the magazine on paper, there won't be one on the WWW, either. We are not over-staffed, and right now many of the articles you see already on our site were html-ized by volunteers. Our goal is to have the entire journal on on the WWW, and we are working towards that goal by creating tools that will allow us to work simultaneously on the paper and WWW versions of the articles. But that's another project which competes for time with the all-important process of getting the articles on paper.
We understand that you feel that we owe you having all the articles on-line; but it's not something we offer as part of the subscription, partly because we don't have the resources to provide that service in a timely fashion. We would like to suggest that you compare the WWW service that we provide now, with a full, interactive index, many of our previous articles, and response forms all available, with what we provided a year (and less) ago—no WWW service at all. Please understand that we are growing, and increasing our level of service as we grow, but it takes time.
I'm just writing to give you the current URLs and e-mail addresses for the Hungry Programmers stuff that were mentioned in the Lesstif and Viewkit article in the November issue of LJ.
The URL for the Hungry Programmer's homepage is now http://www.hungry.com:8000/
The URL for the lesstif stuff is now http://www.hungry.com:8000/products/lesstif/
The URL for the lesstif documentation project is now www.hungry.com:8000/products/lesstif/Lessdox/LessTif.html
The URL for the viewkit stuff is now http://www.hungry.com:8000/products/viewkit/
The e-mail address for the hungry programmers is now firstname.lastname@example.org
The address for the mailing list is also different than what was published in the article. It is now email@example.com.
An alert LJ reader, Robert Day, pointed out an error in the Find tutorial published in the December issue. The tutorial provided an incorrect example for using find to locate files with the SUID bit set.
The example was:
find / -perm 4000 -print
As shown earlier in the article, this command would find only files whose permissions are exactly 4000. The correct example is:
find / -perm -4000 -print
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!
- Paranoid Penguin - Building a Secure Squid Web Proxy, Part IV
- SUSE LLC's SUSE Manager
- Google's SwiftShader Released
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space
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