Freenet Installation and Administration
Properly set up, a Freenet node shouldn't need any ongoing administration. However, there are a few automatable tasks that need to be done. First of all, the log files need to be rotated. Secondly, you'll want to restart the Freenet software periodically. Currently the disk (and I believe memory) usage of Freenet tends to balloon unless you restart your node periodically. Both rotating the log files, which requires restarting the node anyway, and restarting the node can be easily done with the script restart_script (shown in Listing 1). For your average node, restarting once a week should be fine.
IBM's JDK is probably the easiest JDK to install. It's precompiled and works, plus it's one of the faster JDKs out there. On the downside it's proprietary and requires registration to download. Both tarball and Red Hat RPMs are available at: www.ibm.com/java/jdk/linux130/index.html.
Kaffe, the OpenSource JDK, is another, more difficult option. You will have to compile in gmp support, something most distributions don't do in their Kaffe packages. A Debian package for Kaffe with gmp support is available from Mr. Bad's site, above. Otherwise, compile from anonymous CVS or a source package to which you apply the patch found in the Freenet README. Make sure you enable gmp support with the --enable-gmp option when you run ./configure.
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
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- Tech Tip: Really Simple HTTP Server with Python
- Parsing an RSS News Feed with a Bash Script
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
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