GoogleBot: Slayer of Stock Prices
UAL Corp. had a nasty surprise on Monday when its stock price fell nearly 75% after a computerized chain-reaction caused outdated information to hit the trading floor hard — and UAL's financials even harder.
The trouble all began in 2002, when UAL filed for Chapter 11 Bankruptcy — which it put behind itself as of 2006. At the time, a number of news outlets including Tribune Co. — owners of the Chicago Tribune, Los Angeles Times, and Baltimore Sun, among others — reported on the filing, a normal occurrence for a media outlet. From there, all was well, until Sunday, when a Terminator-like rise of the machines set out to ruin UAL.
According to Tribune, a lone reader of the South Florida Sun-Sentinel website triggered the cataclysm after reading the 2002 story. Because Sunday morning is a particularly low-traffic time, this single hit put the story on the site's "Most Popular" list, starting the snowball downhill. A second reader, looking for information about storm-induced airline delays, clicked on the article, at which point the Googlebot got involved. Discovering the story, Googlebot quickly added it to Google News, and as it lacked a publication date, it was quickly pushed out to millions of readers, including Bloomberg LP, the go-to news source for Wall Street.
According to reports, the Bloomberg alert caused automated trading services to drop UAL, resulting in a drop from $12 per share to $3 per share within fifteen minutes. Tribune claims that it is all Google's fault, because they requested that the Googlebot not scrape Tribune sites, a request which they allege Google ignored. Google, however, denies that any such request was ever made. Tribune has responded, saying they can prove what they've alleged.
Whether the Googlebot was supposed to be on the site or not is really immaterial, as the real cause is made clear by an admission printed by Tribune on the very website responsible. "Tribune Co. spokesman Gary Weitman, said a company investigation ... found there was no activity on the story until [Googlebot] visited the Sun-Sentinel site around 10:30 p.m. Pacific time and found the story, which was undated in the archive." (Emphasis ours.)
Had the story been dated by its publisher, Googlebot wouldn't have needed to guess at the publication date, and the people who saw it would have immediately noticed the story was six years out-of-date. Moral of the story? If you're going to be the second-largest newspaper publisher in the U.S., take a cue from the second-grade and write your name and the date at the top of your paper before you hand it in.
Justin Ryan is a Contributing Editor for Linux Journal.
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
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader 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