AboutWelcome to Free Software Daily (FSD). FSD is a hub for news and articles by and for the free and open source community. FSD is a community driven site where members of the community submit and vote for the stories that they think are important and interesting to them. Click the "About" link to read more...
Spiceworks next week is set to make available an enhanced version of its free network management software which now includes remote-access capabilities, enhanced antivirus support and an IT management dashboard designed to showcase data relevant to troubleshooting.
In this final section I'll present some MIDI-specific troubleshooting tips, along with a brief description of the setup here at StudioDave, a few closing remarks, and of course some links to the Linux music-maker du jour.
Troubleshooting in Linux is a breeze if you know which tools to use and how to use them. In this article we learn to do some general Linux troubleshooting on the most common elements of the computer: hardware, programs installed, network, and log files.
The Apache Web server (Apache) comes with a powerful logging framework. In the default configuration, Apache logs all errors to an error log and all access requests to an access log. The default level of logging is sufficient for analyzing traffic patterns and for getting basic information about errors, but it may be inadequate for troubleshooting purposes. Familiarity with all the logging features can help you troubleshoot the Web server or applications hosted on Apache.
Troubleshooting has always been one of the most frustrating aspects of computer ownership. Due to the practically infinite number of potential problems, it would be utterly impossible to write a how-to guide to fix all of them, but in this article we are going to address some of the most common problems.
There is a lot of information scattered across the Internet about the different utilities used for network troubleshooting. Yet, few articles detail the background processes taking place while using these utilities. To get a complete and precise idea on how tracing and troubleshooting work in a network, this article analyzes the internal working of 3 network utilities and checks what makes each of them unique.
Recently, a Red Hat developer got rid of a flaw in an Intel graphics driver, probably for a special corporate customer. For years, the flaw had been a thorn in the side of numerous users of systems with the 945GM chip-set. Now, Theodore 'tytso' Tso has stated in a discussion on LKML that users have to accept more responsibility for troubleshooting and quality assurance.
At last we reach the final installment of this series, the question & answer stage in which we'll consider some of the common problems encountered with audio and MIDI on Linux, along with some common and perhaps not-so-common solutions to those problems. We've looked at some indispensable items for your Linux system troubleshooting toolkit, now let's see how they are applied.
As an administrator you may be face with the task of constantly monitoring web servers, mail servers, ftp servers, etc. Basically, your organization wants all of their servers up and running all of the time. Nagios 3 offers an easy set up and configuration to make this happen so that you can monitor multiple servers and have Nagios alert you to problems.