To run AMD, you simply type amd at the prompt, providing the mount point(s) amd the map(s) on the command line. For example, if the map in listing 1 is named /etc/map.main, and a map named /etc/map.silly also exists, to execute AMD you would type:
amd /u /etc/map.main /silly /etc/map.silly
It is a good idea to include this statement in your rc files.
A number of options are available for the amd command. Two useful options are the ability to specify the NFS mount points and the timeout period. The program amq helps control AMD. For example, amq can force AMD to unmount a file system and to flush the cache (useful when debugging NFS problems). The man page for amq provides a complete description of all its capabilities.
Because AMD is just a front end to regular NFS, you have to worry about the same issues that you would when running NFS alone—you must ensure that exports and their options are correct. Explaining NFS is beyond the scope of this article; however, if you are unfamiliar with the basics of NFS, see the NFS Resources box on page FIXME.
Binaries and patches to port AMD to Linux may be obtained from sunsite and other sources (see sidebar). AMD has stayed relatively stable and bug free in the last few years; development is no longer active. AMD comes with excellent documentation.
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!
- Google's SwiftShader Released
- Interview with Patrick Volkerding
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Tech Tip: Really Simple HTTP Server with Python
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Returning Values from Bash Functions
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