The following was posted to comp.os.linux.admin in late July by Cor Bosman:It has come to my attention that there is something bad going on with the /etc/gateways file on a lot of Linux machines. In an attempt to set up routed on machines all over the world. After some investigating these seemed to be all Linux machines. I was then told by someone on comp.os.linux.admin that the /etc/gateways file on most Linux distributions (at least all the way since the first SLS distribution) have the following information in /etc/gateways as an “example”:
> net microwalt gateway metallica passive > net hacktic gateway 22.214.171.124 passive > net default gateway 126.96.36.199 active
188.8.131.52 is one of our Suns. I have never given permission to include this in any Linux distribution. Since our domain pays for incoming traffic also, this is costing me a lot of money for no reason. I would therefore like to ask everyone running routed to check their /etc/gateways, and remove both lines mentioning 184.108.40.206. Even if you don't run routed, I'd appreciate it if you remove those entries. I would also ask that this be removed from all future Linux distributions. Knowing who is responsible for the questionable act is also something I'd be happy to hear.
So: Please check your /etc/gateways file! There is a big chance it will have illegal entries since I did not give permission to use those defaults. This may cause unnecessary traffic for both you and me. —Cor Bosman
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!
- Stunnel Security for Oracle
- SourceClear Open
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Google's SwiftShader Released
- Non-Linux FOSS: Caffeine!
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space
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