Focus on Software
The RPM standard is a panacea for those who use RPM-based distributions (Red Hat, Caldera, Mandrake, SuSE, etc.). Or is it? You may have noticed that RPMs from one distribution don't always work on another. They don't install due to dependency problems (even though they would run just fine), or they install but segfault (library incompatibilities), etc. So you grab a .src.rpm file, and try to build it. Often, that doesn't work because some distributions have seen fit to make slight alterations to their version of RPM. What about those who can't even build an RPM .spec file and the patches required? Well, you might want to check out http://specs.pananix.net/. The .spec and patch files are thin at the moment, but with help from the RPM community, this could be a great site for grabbing a .spec file and patches that work for your distribution. Hopefully, all that's required is the software archive file, the .spec and patches. The command
rpm -bb && rpm -i ../RPMS/i386/should do the trick.
This is a small web notebook with fields for subject and body. It automatically adds the creation date, modification date and a note number. webnotebook is similar to note, but is used via a web browser (lynx works just fine). You can search for any term, and the notes found will be listed. Searching on nothing returns everything. Unlike note, which sorts on note number, the default sort in webnotebook is the modification date (latest first). It requires MySQL server, web server configured for CGI, Perl and the Perl DBI/DBD module.
Much like Downloader for X, this program will download a number of files. While slightly more complex than Downloader for X, darxite runs a daemon in the background, which you can connect to in order to pass URLs for downloading (including downloading directories recursively). Several client programs, for X and the command line, can be used to pass commands, URLs and monitor download progress. This program will continue downloading even after you log out. It requires libpthread and glibc.
This tool is a Tcl/Tk front end for ping, traceroute, nslookup, finger and whois. Output is displayed in the window and can be saved for future reference. This tool works well for those not accustomed to a command line. I would only add netstat -rn, netstat -an and ifconfig to have a relatively complete set of tools for viewing the network status of the host. It requires Tcl/Tk.
Advanced Packet Sniffer: http://www.swrtec.de/
This packet sniffer provides a wealth of information about packets on your network, as well as a display of the entire packet. The header is put into human-readable form and presented, starting with the MAC address. A number of options are available, such as whether to include or exclude a particular MAC or IP address. This sniffer can be run only by root, but that constitutes a fairly good reason not to allow rogue Linux systems on your network. It requires glibc.
This particular utility seeks to replace the no-longer-free tripwire, but filetraq works from a slightly different perspective. Rather than track large numbers of files daily, it looks for changes in a few key files at very short intervals. Changes in any of these files are reported via e-mail when the change is detected. Key files include one of /etc/passwd or /etc/shadow and a few others, such as /etc/services and /etc/inetd.conf and easily editable startup files. Basically, filetraq uses diff to compare the file against the database, so you could include /bin/login also. It requires bash and recommends cron.
This utility will search through your mail log file using grep and display important statistics gleaned from that file: largest messages, source of most messages, etc. One problem this particular utility suffers from is the lack of a usage message. Both -h and help tell you to read the manual, but the manual isn't installed with the software—an oversight, I'm sure. It requires libstdc++, libm and glibc.
It has been awhile since a new password-cracking program has appeared. The ones currently available are difficult to compile or require mega-swap space and more resources than most modest systems have. nutcrack is quick. One caution: the dictionary used is extremely important. I created a new account, and used the account name as the password—it wasn't caught. So, be sure to add the contents of your password file (user name and GECOS field) to the dictionary. It requires Perl and a good dictionary file.
This particular daemon is yet another IP logger, but with one big difference: unlike many loggers, this one does not rely on promiscuous mode and logs the packets in an easily understood, human-readable format (configurable). This makes for fewer mistakes when manually reading the log, and it can be machine-processed easily. You can choose among logging TCP, UDP, ICMP or IGMP (or any combination). Caution: if you get many simultaneous connections, you will see a weedlog spawned to report each one (it will die, but you could end up with a very large process table). It requires libpthread and glibc.
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
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
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