This photo was taken when my wife and I were waiting to get married in the chapel on the second floor of New York City Hall. I just received the 100th issue of LJ and brought it along. You can tell from the photo that my wife was a little jealous. So the title for the photo is “Beauty or LJ”. Hope you like it.
I enjoyed reading your article about setting up an FTP proxy [LJ, December 2002]. I was just curious about one point. You make a comment about not being able to configure the acceptable commands list differently for internal and external users. Is it possible to set up two proxies then route the incoming requests at the firewall for internal addresses to one proxy and those from external addresses to the other?
Mick Bauer replies: That's an excellent idea! You could set up a proxy on the firewall for external users, with read-only permissions, and set up a proxy on some host on the inside for outbound transactions, with looser permissions. You could then configure your firewall to permit outbound FTP only if it originates from the designated internal proxy.
It's great to see those huge old machines coming back! I saw an advert in Linux Journal for a CDC 6400, the baby brother of the immense CDC 6600. Of course today we could not use Freon to cool it. And software is coming back! SOAP, for instance, the Symbolic Optimal Assembly Program for the IBM 650. Magnetic drum memory will never die! I have even seen articles about ASP, the Attached Support Processor for the IBM 360/65. Who says I'm a dinosaur?
—Peter Chase, Alpine, Texas
The articles on ptrace in the November and December 2002 issues were very informative. So what's to stop someone from using ptrace to insert some malevolent code in a running program? Forgive me for looking on the dark side.
—Walter S. Heath, Concord, Massachusetts
Keep thinking evil thoughts. You can't keep a system secure without studying possible attacks. Fortunately, you can only ptrace a process if it's your own process, or if you're root.
I have found an error in my article, “OpenLDAP Everywhere” [LJ, December 2002]. In the auto.home section on page 54, the gomerp entry has the line:
The line should read:
cn: gomerpA reader contacted me after copying the entry exactly from the article. He has fixed his configuration and is up and running with unified logon. Matt Lung and I are very pleased with the article as published. Our mothers are very proud!
We were a little disappointed by your article on the applications for the Zaurus. You listed many commercial applications and yet when it came to mapping/navigation software you listed only the free one. zNav and zNav Lite are the only Zaurus mapping/navigation products that use commercial navigation charts.
—Patrick Cannon, Barco Software, LLC
Here the world's highest Linux install event took place Saturday the 12th of December 2002, 11,000 feet above the sea. It was the first of its kind in this part of Bolivia—and maybe a world record when it comes to altitudes and Linux install events.
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
- Managing Linux Using Puppet
- Tech Tip: Really Simple HTTP Server with Python
- Returning Values from Bash Functions
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Rogue Wave Software's Zend Server
- Doing for User Space What We Did for Kernel Space
- 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