Followup: Was Linux Worth It?
A few days back, I posted a story regarding our LTSP server upgrades over Christmas Break here at my school district. I must confess, things didn't go well on Thursday when school resumed. In fact, it was a horrible mess. Here's the skinny:
1) Both thin client servers worked GREAT when I was the only person logging in. Once all 250ish thin clients were in use, however, things quickly fell apart. SLOW access, Firefox wouldn't load, thin clients would hang...
2) The same hardware running older versions of K12LTSP worked quite well before the upgrade, so I was pretty sure I just needed to tweak things.
3) I had no idea what to tweak.
That's where technical support comes into play. No, I don't mean I called technical support, I mean that I used the amazing community of Linux users that are willing to bend over backwards to help each other. A handful of instant messages, a couple emails to the K12LTSP listserv, and I had some quick, insightful suggestions to fix the mess.
I made a few changes based on the feedback I received, and I tweaked the few things that I was sure wouldn't hurt. This morning, things are fast and smooth. That doesn't make yesterday any better, but they say what doesn't kill you makes you stronger, and my Geek Fu is rather strong today. :)
Oh, the things I tweaked? Sure, here ya go:
1) NFS on my file server was set at the default 8 daemons. I upped that to 16, and also changed the memory allowances. I used this tutorial that Google scrounged up for me.
2) I updated Firefox to the latest stable version. The K12LTSP version I used only has 1.5, and I thought it wouldn't hurt to get version 2 running.
3) I removed the big, beautiful photos that I had for the background on the KDM login screen.
Honestly, I think that #1 was the tweak that was the "Magic Bullet" -- but the others have proven nice as well. Firefox 2 is an awesome program, and really, the background took a long time to load when it was a big photograph.
Lastly, what did all the tech support cost me? A thank you. That's it. Even that wasn't required, but it seemed the least I could do. Also, now when someone else posts a question to me either via email, instant messenger, or on a mailing list, I'll share my experience with them. For free. Honestly, although the Linux software itself is awesome, it's really the people that make open source solutions so incredible.
The really cool part? It's not just awesome geeky gurus that make the open source community so incredible. It's you. It's me. It's the student that first showed me how to drag a window by holding down the ALT key if the screen is too small. It's people that aren't afraid of looking dumb by asking questions.
Don't hesitate asking questions to mailing lists, in the forums here, or even to me personally via email. Even if we can't help each other, someone, somewhere knows somebody that can. That's why open source is so great, the community of people that make it.
So, as I'm sure you guessed, yes Linux is definitely worth it. I'm going to go bask in my new thin client goodness now, and figure out why the OSX computers in the district are logging in so slow... Ugh.
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!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- SUSE LLC's SUSE Manager
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- SuperTuxKart 0.9.2 Released
- SourceClear Open
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