Providing cross-training for employees who maintain a specific job focus reduces operation risks by enabling staff members to deploy contingency plans smoothly and rapidly. For example, an administrator who maintains an NT or Novell server can be cross-trained in Linux. When the inevitable human resources crunch occurs, the workload can be easily redistributed. If a staff member is out for a work emergency or due to a personal crisis, another can step in and help fill the role. Diagnosing a problem over a long-distance connection to someone who doesn't know the first thing about the bash interactive shell can be a frustrating experience at best and can lead to potentially greater catastrophes than the initial problem.
Distributing knowledge and skills to employees through cross-training also provides staff with a better understanding of multiple problem and solution domains available in their networked computing environment. By providing cross training of Linux skills to staff members who are responsible for other systems (such as NT or Novell), the collective of knowledge can assure the very best overall practices are employed. By the same token, appropriate NT systems training for staff members who are primarily focused on Linux will lend them understanding of how best to leverage the strengths and weaknesses of each operating system environment.
In today's high-speed networked computing environment, both inadvertent damage and malicious attacks can cripple a system in the blink of an eye. Damage recovery is a painfully slow and meticulous process. Data is almost never completely restored, and the time devoted to system recovery has net-zero productivity.
With proper training and planning, however, preventive measures can be taken to avoid risks and speed recovery in event of a breach. Knowledge of how best to protect the system through management of permissions and system services allows the administrator to maintain tight system control, while determining allowable access. Initial planning for system installation will accommodate the most-favored backup strategies within the organization.
The costs associated with Linux-based training are easily determined. It's far more difficult to ascertain the tangible and intangible costs of not investing in training. The backlash of not instituting an educational program can include reduced staff productivity and the loss of potential employee innovation and creativity. And the company's customers are another critical factor; clients depend on a networking organization for high-end technical knowledge and service. It just takes one slip to lose credibility, and perhaps business as well.
Finally, lack of adequate training could pave the way to security risks. Linux has become a big player on-line, and its growing popularity has led to an ever-expanding threat of potential damage from hackers. With sufficient knowledge of the Linux operating system, employees know which features or unused services to disable to ensure site protection.
The costs of inadequate training can be either obvious or subtle, but they trickle down through most phases of operations. Solid training allows a diverse staff to play from the same sheet of music, and the advantages are equal for both direct employees and paid consultants. In the final analysis, providing an ongoing education program for employees is the most important networking an organization can do.
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
- Doing for User Space What We Did for Kernel Space
- Tech Tip: Really Simple HTTP Server with Python
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
- SuperTuxKart 0.9.2 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