Linux System Administration Tools
Linux old-timers revel in reminding newcomers that they used to have to do everything by hand, at the command line, uphill, both ways, with duct tape for shoes. What really gets some of these folks sputtering is today's collection of system administration tools that introduce quite a bit of automation. There's good reason for this, actually; if you don't know how to administer your system by hand then you are sunk if something goes wrong. However, this factor doesn't mean you shouldn't take advantage of available helping hands.
There are four major players in the world of Linux system administration tools: COAS, Linuxconf, Webmin and YaST. One of these, YaST, is tied specifically to SuSE Linux. The other three, COAS, Linuxconf and Webmin, come by default with some distributions but are independently available for download and installation.
Linuxconf (Figure 1) comes with Mandrake Linux and Red Hat Linux, but is also available for most modern Linux distributions. You've probably encountered this tool before if you use one of these distributions, either as the whole package or in one of its modular components. Multiple interfaces for Linuxconf have been available for years, but now we're up to four: GUI, Web, command-line and ncurses.
Linuxconf has actually been around for years, which means its bugs have had longer to shake out than the other distribution-neutral tools. You can download and find out more about this tool at www.solucorp.qc.ca/linuxconf. Be sure to read through what each portion of the Linuxconf package is used for. There is a base package with the non-GUI components, and then there are various GUI front-end pieces from a more general X Window System version to one specifically built for GNOME.
Whether you stick with the command-line version or add a GUI front end, you run the tool by typing linuxconf. From here you navigate text or point and click menus to access a wide variety of system settings, everything from basic networking details to GRUB configuration. Linuxconf also plays well with people who refuse to use the root account for anything but the most vital tasks. If you try to run it as root, the tool simply asks for the root password--if this fact makes you nervous, then you may want to consider not using this tool, but this practice is fairly standard in modern administration tools. When you consider that anyone could just try to su to the root account at whim, you start to see why it is so important to have a secure root password in place.
Webmin (Figure 2) comes with, and was recently acquired by, Caldera Linux. This tool is not only available for most modern Linux distributions, it also runs on most major flavors of UNIX and is available in around twenty languages (though some modules are not available in all of the languages). As you might guess, Webmin is purely a web-based application and a heavily modular one at that.
There is a set of core modules that handle the usual system administration functionality, and then there are the third-party modules available for administering a variety of packages and services. To download and learn more about Webmin, point your web browser to www.webmin.com/webmin. Once again, this package is available in a number of formats specific to different distributions.
Where any user can install Linuxconf, Webmin must be installed by root. After that you can access this tool from any user account as long as you know the root password.
There are three separate rows of icons on this tool's front page. On the upper right, you have a pair of administrative links, one to log you out of the Webmin tool and another that allows you to fill out a feedback form that sends your comments back to the Webmin team. In the same top row on the upper left you can click on the word Webmin and go to the product home page. On the upper bar directly beneath those links, there are a series of menu icons, which are, from left to right:
Webmin: takes you back to the main Webmin screen.
System: a collection of configuration issues, such as user and group manipulation, disk quotas and cron jobs.
Servers: configuration routines for a number of servers you may have installed on your system, such as Apache, WU-FTPD and sendmail.
Hardware: configuration utilities for hardware issues such as RAID, printers and disk partitions.
Cluster: a collection of cluster maintenance tools.
Others: a set of tools that system administrators typically need, such as a command prompt, an alias manager and a file manager.
Finally, there is the Webmin tab, which has a series of Webmin management tools:
Webmin Actions Log: if you've enabled Webmin logging, this function allows you to search through the logfiles for what you've utilized this tool to do to your system.
Webmin Configuration: takes you to the amazing number of configuration options available for Webmin, everything from strengthening your Webmin authentication requirements to upgrading either the main package or individual modules.
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
- Tech Tip: Really Simple HTTP Server with Python
- Returning Values from Bash Functions
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Rogue Wave Software's Zend Server
- Doing for User Space What We Did for Kernel Space
- 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