Linux Journal, recognizes the importance of protecting the privacy of information provided by visitors to our web sites. We have created the following data collection policies to demonstrate our commitment to the issue of privacy.
Web Site User Information Collected by Linux Journal
Magazine Subscriber Information Collected by Linux Journal
In order for you to subscribe to Linux Journal, access your subscriber data on-line, or utilize our customization features, you will need to provide us with certain personally identifiable information. Some examples of this type of information include your name, address, phone number, billing address, and e-mail address. You will only be asked to provide personal information that is essential to complete or participate in the activity that you have selected.
Use of Information
Linux Journal takes every precaution to protect users' information from unauthorized use. When users submit sensitive information via our web sites, the information is considered confidential both on-line and off-line. We do not allow public access to the portion of the server that contains user information.
E-mail addresses provided to us will only be used to send relevant and important Linux Journal correspondence, such as notifying magazine subscribers a subscription has expired, or alternatively, to send a user their opted-in e-mail newsletter. Linux Journal strictly enforces e-mail privacy and therefore, e-mail addresses are never sold or provided to third parties. Additionally, upon request, Linux Journal will remove users (and their information) from our database or permit them to "opt-out" of any further e-mail newsletters that they had previously signed up for.
Our web server automatically recognizes and collects the domain name and IP address of visitors to our web sites. In addition, we collect aggregate tracking information derived mainly from tallying page views throughout our sites, and information volunteered by the visitor, such as survey information and/or site registrations. The information we collect is used to improve the content of our web pages, customize the content and/or layout for each individual visitor, and for us to contact visitors about our products and services as explained below.
If a visitor has enabled cookies in their browser, we will send a cookie file that will only store a unique, random session ID that is maintained throughout the session to track the pages visited. This allows us to provide our site visitors with certain conveniences, such as delivering unique content and helping with lost passwords.
Postal addresses collected on-line may be used for periodic mailings from us with information on new products and services or upcoming events, and from other reputable companies. We allow registered users of our publications and services to "opt out" of receiving postal mail from third companies. If you do not wish to be contacted by third-party companies, you may check the button on the subscribe form or user registration form to indicate your preference. You may also provide your name and postal address to our Customer Service manager, and they will be sure your name is removed from the list we share with other organizations. When contacting us, please include the titles of publications to which you subscribe.
Linux Journal is not responsible for the content or the privacy polices of websites to which it may provide links or the websites of its advertisers.
Questions or Comments?
If you have questions about this privacy statement or your dealings with Linux Journal, please do not hesitate to contact us.
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
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Tech Tip: Really Simple HTTP Server with Python
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Rogue Wave Software's Zend Server
- 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