Useful Things You Can Do with FVWM
Sometimes one wants to temporarily reconfigure FVWM, perhaps to test the effect of some configuration command. One way to do this is to modify the config file and then restart FVWM. You probably will find, depending, of course, on how your FVWM is configured, that if you click on the root window, you get a menu containing the option Restart FVWM. This is a little tedious, however. Maneuvering the mouse to the root window, clicking on it and choosing the option to restart FVWM takes time, particularly if the root window is completely obscured by windows. And the restart of FVWM takes a significant fraction of a second. There's a better and faster way--the program FvwmCommand, which comes packaged with FVWM.
FvwmCommand can perform a number of functions. We're only interested in one function, however: sending commands to FVWM. Sending commands is a simple task: one simply runs FvwmCommand command_to_send. For example, the command to restart FVWM is called Restart, so to restart FVWM, one only need give the command FvwmCommand Restart at the shell prompt.
In order for FvwmCommand to work, it needs to talk to FVWM. It doesn't do so directly, however; instead, it does so through an intermediary, called FvwmCommandS. FvwmCommandS is an FVWM module, which is a program started by FVWM that communicates with it by means of a special protocol.
The best way to get FVWM to start FvwmCommandS is to put a command to this effect in FVWM's config file. The command to use is Module, and it takes as its argument the name of the module to start. So in this case, the full command is Module FvwmCommandS. Once you've put this command into the FVWM config file and restarted FVWM, you should find that FvwmCommand works for you.
Ronan McGoran is a UNIX system administrator. His home page can be found here.
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!
- SourceClear Open
- SUSE LLC's SUSE Manager
- Tech Tip: Really Simple HTTP Server with Python
- My +1 Sword of Productivity
- Doing for User Space What We Did for Kernel Space
- Returning Values from Bash Functions
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- SuperTuxKart 0.9.2 Released
- 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