Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I was hoping for a couple of neat tips that would help me get our NFS usage down a bit when multiple users log into our Linux cluster. At the moment we offer KDE by default as it's usually pretty stable and intuitive to use, with each user's /home directory mounted via NFS so that they get the same profile on every machine. The problem comes when around 10 or more users sit down at our cluster simultaneously, as the NFS usage starts to climb, response time for running programs increases and people start to mutter in my direction.
I already redirected the cache from Firefox to /tmp and installed as many programs as possible locally on each machine, but it'd be great if I could figure out how to slash the NFS usage of normal KDE processes as well? Would copying the .kde4 folder to somewhere local during login, then replacing it by a symlink in /home help at all, or is it likely to be services such as strigi, Akonadi etc that are indexing the NFS-mounted /home too often? If so, can I easily exclude files on the NFS mount from indexing, and are there any files that I need to keep indexing?!
I found a tip that suggested changing the flags for the NFS mount to 'async', but that sounds a bit risky on an open cluster where crashes occur, power cables get pulled out and users have a habit of hard-rebooting first and asking questions later. Especially as *some* of the data stored there is actually important.
Ok, thanks! I wasn't sure about all the KDE programs that seem to be dependent on strigi, I didn't want to switch it off and risk breaking KDE. So long as it's not essential then I guess I can give it a go.