DOCSLIB.ORG

Nagios Version 1.0 Documentation

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Nagios Version 1.0 Documentation Nagios® Version 1.0 Documentation Copyright © 1999-2002 Ethan Galstad Email: [email protected] Last Updated: 08-28-2002 [ Table of Contents ] Nagios and the Nagios logo are registered trademarks of Ethan Galstad. All other trademarks, servicemarks, registered trademarks, and registered servicemarks mentioned herein may be the property of their respective owner(s). The information contained herein is provided AS IS with NO WARRANTY OF ANY KIND, INCLUDING THE WARRANTY OF DESIGN, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE. Version 1.0 Documentation Table of Contents About What is Nagios? System requirements Licensing Downloading the latest version Other monitoring utilities Release Notes What's new in this version Change log Support Frequently Asked Questions (FAQs) Mailing lists Contract help Getting Started Advice for beginners Installing Nagios Compiling and installing Nagios Setting up the web interface Configuring Nagios Configuration overview Main configuration file options Object configuration file options CGI configuration file options Configuring authorization for the CGIs Extended information configuration Running Nagios Verifying the configuration Starting Nagios Stopping and restarting Nagios Nagios Plugins Standard plugins Writing your own plugins Nagios Addons nrpe- Daemon and plugin for executing plugins on remote hosts nsca- Daemon and client program for sending passive check results across the network Theory Of Operation Determing status and reachability of network hosts Network outages Notifications Plugin theory Service check scheduling State types Time periods Advanced Topics Event handlers External commands Indirect host and service checks Passive service checks Volatile services Service result freshness checks Distributed monitoring Redundant and failover monitoring Detection and handling of state flapping Service check parallelization Notification escalations Monitoring service and host clusters Host and service dependencies State stalking Performance data Scheduled host and service downtime Database support Using the embedded Perl interpreter Object inheritence using template-based config data Time-saving tips for templated-based object definitions Integration With Other Software Portsentry SNMP Traps TCP Wrappers Miscellaneous Securing Nagios Tuning Nagios for maximum performance Using macros in commands Information on the CGIs Custom CGI headers and footers About NagiosTM What Is This? NagiosTM is a system and network monitoring application. It watches hosts and services that you specify, alerting you when things go bad and when they get better. NagiosTM was originally designed to run under Linux, although it should work under most other unices as well. For more information on what operating systems Nagios will and will not run under, see the OS ports page at http://www.nagios.org/ports.shtml. Some of the many features of NagiosTM include: ● Monitoring of network services (SMTP, POP3, HTTP, NNTP, PING, etc.) ● Monitoring of host resources (processor load, disk usage, etc.) ● Simple plugin design that allows users to easily develop their own service checks ● Parallelized service checks ● Ability to define network host hierarchy using "parent" hosts, allowing detection of and distinction between hosts that are down and those that are unreachable ● Contact notifications when service or host problems occur and get resolved (via email, pager, or user- defined method) ● Ability to define event handlers to be run during service or host events for proactive problem resolution ● Automatic log file rotation ● Support for implementing redundant monitoring hosts ● Optional web interface for viewing current network status, notification and problem history, log file, etc. System Requirements The only requirement of running Nagios is a machine running Linux (or UNIX variant) and a C compiler. You will probably also want to have TCP/IP configured, as most service checks will be performed over the network. You are not required to use the CGIs included with Nagios. However, if you do decide to use them, you will need to have the following software installed... 1. A web server (preferrably Apache) 2. Thomas Boutell's gd library version 1.6.3 or higher (required by the statusmap and trends CGIs) Licensing NagiosTM is licensed under the terms of the GNU General Public License Version 2 as published by the Free Software Foundation. This gives you legal permission to copy, distribute and/or modify Nagios under certain conditions. Read the 'LICENSE' file in the Nagios distribution or read the online version of the license for more details. NagiosTM is provided AS IS with NO WARRANTY OF ANY KIND, INCLUDING THE WARRANTY OF DESIGN, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE. Acknowledgements Several people have contributed to Nagios by either reporting bugs, suggesting improvements, writing plugins, etc. A list of some of the many contributors to the development of Nagios can be found at http://www.nagios.org. Downloading The Latest Version You can check for new versions of Nagios at http://www.nagios.org. Other Monitoring Utilities In case you weren't aware, there are other network monitoring utilities available besides Nagios. I think Nagios is a pretty good contender, but I'm obviously biased. Here are links to a few other free monitoring utilities. There are many others that are not listed here - search the net (or Freshmeat) and you'll find them. ● Angel Network Monitor ● Autostatus ● Big Brother ● HiWAyS ● MARS ● Mon ● Netup (French) ● NocMonitor ● NodeWatch ● Penemo ● PIKT ● RITW ● Scotty ● Spong ● Sysmon Nagios and the Nagios logo are trademarks of Ethan Galstad. All other trademarks, servicemarks, registered trademarks, and registered servicemarks may be the property of their respective owner(s). What's New in Version 1.0 Important: Make sure you read through the documentation (especially the FAQs) before sending a question to the mailing lists. Many of the changes described below are the direct result of this project being renamed from NetSaint. Transitioning from NetSaint to Nagios will undoubtedly take some time, but it'll be well worth it. Change Log The change log for Nagios can be found online at http://www.nagios.org or in the Changelog file in the root directory of the source code distribution. Changes 1. User/Group Change. The default user/group that Nagios runs under is now nagios/nagios. 2. Directory Change. The default directory that Nagios gets installed in is now /usr/local/nagios. 3. URL Changes. The base URLs for accessing the HTML files and CGIs through the web interface are now /nagios/ and /nagios/cgi-bin/, respectively. 4. Config File Changes. The main config file is now nagios.cfg and the CGI config file is now cgi.cfg. 5. Process Check Command Changes. The old process_check_command variable in the CGI config file has been renamed to nagios_check_command. Also, if you do not specify a check command, the CGIs will assume the Nagios process is running properly. 6. Archive Changes. Archived log files from Netsaint must be renamed from "netsaint-date.log" format to "nagios-date.log" format if you want to make them available to the Nagios CGIs. You can rename all your archived log files with the following command (assuming you've already moved them to their new directory location): rename netsaint nagios netsaint*.log 7. Retention File Format Change. The format of the retention file (or database, if that's what you were using) has changed to support more variables. No conversion utility is yet available, which means you'll either have to find a way to manually convert your retention data, or lose it when you make the changeover. 8. Database Schema Changes. The database schema for status, retention, comment, and extended information data has changed. If you were using database support previously, you'll either have to recreate the databases using the sample scripts provided in the contrib/database directory just alter your existing tables (an exercise which will be left to you). Also note that the default database name is now nagios. New Features 1. Template-Based Object Config File. This is probably the biggest feature which has been added. Use of the template-based object config file format is optional, but highly recommended. Note that the older config file format is still supported if you really want it. The template-based config file is much easier to read, modify, and expand upon compared to the older format. It also allows you to specify host- and service-specific values for things like flap detection thresholds, flap detection and performance data processing options, etc. If you're interested in trying out the new template-based config file format, check out the convertcfg utility in the contrib/ directory of the distribution - it can be used to quickly convert your old config files to the template-based format. More information on the template-based object config file can be found here. 2. Template-Based Extended Info Config File. This is similar to the template-based object configuration file format mentioned above. You can now store extended host and service information in a template- based config file. More information on doing this can be found here. If you wish, you can still use the older style of defining extended information directives in the CGI configuration file as described here. 3. Host Dependencies. You can now define optional host dependencies which will prevent notifications from being sent out for a host if one or more criteria fail. In the past there have been implicit dependencies between hosts that are related through "parenting", but this now allows you to create explicit dependencies between unrelated hosts. More information on dependencies can be found here. 4. Host Escalations. You can now define optional notification escalations for specific hosts. In the past you were only able to define escalations for entire hostgroups. While this was closely matched to non- escalated notification logic, it didn't provide much flexibility. Note that hostgroup escalations are still supported and can be used in conjunction with host escalations. More information on notification escalations can be found here. 5. Freshness Checking.
Load more

Recommended publications
  • THINC: a Virtual and Remote Display Architecture for Desktop Computing and Mobile Devices
    THINC: A Virtual and Remote Display Architecture for Desktop Computing and Mobile Devices Ricardo A. Baratto Submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy in the Graduate School of Arts and Sciences COLUMBIA UNIVERSITY 2011 c 2011 Ricardo A. Baratto This work may be used in accordance with Creative Commons, Attribution-NonCommercial-NoDerivs License. For more information about that license, see http://creativecommons.org/licenses/by-nc-nd/3.0/. For other uses, please contact the author. ABSTRACT THINC: A Virtual and Remote Display Architecture for Desktop Computing and Mobile Devices Ricardo A. Baratto THINC is a new virtual and remote display architecture for desktop computing. It has been designed to address the limitations and performance shortcomings of existing remote display technology, and to provide a building block around which novel desktop architectures can be built. THINC is architected around the notion of a virtual display device driver, a software-only component that behaves like a traditional device driver, but instead of managing specific hardware, enables desktop input and output to be intercepted, manipulated, and redirected at will. On top of this architecture, THINC introduces a simple, low-level, device-independent representation of display changes, and a number of novel optimizations and techniques to perform efficient interception and redirection of display output. This dissertation presents the design and implementation of THINC. It also intro- duces a number of novel systems which build upon THINC's architecture to provide new and improved desktop computing services. The contributions of this dissertation are as follows: • A high performance remote display system for LAN and WAN environments.
    [Show full text]
  • Accessing Windows Applications from Unix and Vice Versa
    50-20-42 DATA COMMUNICATIONS MANAGEMENT ACCESSING WINDOWS APPLICATIONS FROM UNIX AND VICE VERSA Raj Rajagopal INSIDE Accessing Windows Applications from an X-Station, Coexistence Options, Windows in an X-Station, Accessing Windows Applications, Accessing UNIX Applications from Windows Desktops, Emulators Migrating from one environment to another takes planning, resources and, most importantly, time (except in very trivial cases). This implies that even if eventually migrating to another environment, one still has to deal with coexistence among environments in the interim. In many com- panies it would make good business sense not to migrate legacy systems at all. Instead, it may be better to develop new systems in the desired en- vironment and phase out the legacy applications. The data created by the legacy applications is important and one must ensure that data can be ac- cessed from a new environment. Coexistence considerations are very im- portant in this case. Coexistence between Windows PAYOFF IDEA NT, UNIX, and NetWare deals with a Some users want applications they develop in number of related issues. One may one environment to execute in other environ- need to access Windows applications ments with very little change. With this approach, they can continue to develop applications with from a UNIX machine or need to ac- the confidence that they will execute in another cess UNIX applications from Win- environment even if the environments change in dows desktops. One may prefer to the future. In applications that can run in both have the same type of desktop (Òan Windows NT and UNIX, this can be accomplished enterprise desktopÓ) for all users and in several ways: be able to access different environ- •use APIs — there are three flavors of this ap- ments.
    [Show full text]
  • Building an out of the Box Raspberry Pi Modular Synthesizer J¨Urgenreuter
    Case Study: Building an Out Of The Box Raspberry Pi Modular Synthesizer J¨urgenReuter Karlsruhe, Germany, reuter [email protected] Abstract Headless Synth Modules The idea is simple and obvious: Take some Rasp- berry Pi computing units, each as a reusable syn- VCO VCA thesizer module. Connect them via a network. Con- nect a notebook or PC to control and monitor them. Start playing on your virtual analog modular syn- thesizer. However, is existing Linux audio software sufficiently mature to implement this vision out of Network the box? We investigate how far we get in building such a synthesizer, what existing software to choose with focus on networking, analyse what limits we Control Host hit and what features still need to be implemented (Synth GUI & to make our vision become reality. Configuration) Keywords Raspberry Pi, Virtual Anolog Modular Synthesizer, Figure 1: The Vision Distributed Networked Audio proach of a network of RPis reveals several ad- 1 The Vision vantages: The popular Raspberry Pi (or, shortly, RPi )[Raspberry Pi Foundation, 2014b] is a • Dedicated System. The RPis are solely small, cheap, yet powerful, computing unit with used for synthesis. The OS, residing on many I/O jacks with Linux/ARMv6 available an SD card, can be tailored to this pur- as operating system (OS). It is predestinated pose. Many services are irrelevant for head- for building networks of collaborative modules, less mode or use in a synthesizer and thus with each RPi taking over the role of a synthe- need not be installed, thus saving space sizer module with dedicated function as e.g.
    [Show full text]
  • Mai Mult a Minha Cultural Mini
    MAIMULT A MINHA US010063202B2CULTURAL MINI (12 ) United States Patent ( 10 ) Patent No. : US 10 ,063 , 202 B2 Kallai et al. (45 ) Date of Patent: Aug. 28 , 2018 ( 54 ) INTELLIGENTLY MODIFYING THE GAIN ( 56 ) References Cited PARAMETER OF A PLAYBACK DEVICE U . S . PATENT DOCUMENTS (71 ) Applicant : Sonos, Inc ., Santa Barbara , CA (US ) 3 ,956 ,591 A 5 / 1976 Gates , Jr. 4 , 105 ,974 A 8 / 1978 Rogers (72 ) Inventors : Christopher Kallai, Santa Barbara , CA D260 , 764 S 9 / 1981 Castagna et al . (US ) ; Mike Chamness , Gloucester, MA 4 ,296 ,278 A 10 / 1981 Cullison et al . (US ) ; Michael Darrell Andrew 4 , 306 , 114 A 12 / 1981 Callahan 4 , 382 , 158 A 5 / 1983 Ohshita et al . Ericson , Santa Barbara , CA (US ) 4 , 509 , 211 A 4 / 1985 Robbins D279 ,779 S 7 / 1985 Taylor ( 73 ) Assignee : SONOS, INC . , Santa Barbara , CA (US ) 4 ,530 ,091 A 7 / 1985 Crockett ( * ) Notice : Subject to any disclaimer , the term of this ( Continued ) patent is extended or adjusted under 35 U . S . C . 154 (b ) by 0 days . FOREIGN PATENT DOCUMENTS CA 2320451 A1 3 / 2001 ( 21) Appl. No. : 15 /670 , 769 CN 1598767 A 3 /2005 (22 ) Filed : Aug . 7 , 2017 ( Continued ) (65 ) ) Prior Publication Data OTHER PUBLICATIONS US 2017 /0346459 A1 Nov . 30 , 2017 “ 884 + Automatic Matrix Mixer Control System ,” Ivie Technolo gies, Inc. , 2000 , pp . 1 - 4 . Related U . S . Application Data (Continued ) (63 ) Continuation of application No . 13 /458 ,558 , filed on Apr. 27 , 2012 , now Pat. No . 9 ,729 , 115 . Primary Examiner — James Mooney (51 ) Int. Cl. HOZG 3 / 00 ( 2006 .
    [Show full text]
  • Real-Time Audio Servers on BSD Unix Derivatives
    Juha Erkkilä Real-Time Audio Servers on BSD Unix Derivatives Master's Thesis in Information Technology June 17, 2005 University of Jyväskylä Department of Mathematical Information Technology Jyväskylä Author: Juha Erkkilä Contact information: [email protected].fi Title: Real-Time Audio Servers on BSD Unix Derivatives Työn nimi: Reaaliaikaiset äänipalvelinsovellukset BSD Unix -johdannaisjärjestelmissä Project: Master's Thesis in Information Technology Page count: 146 Abstract: This paper covers real-time and interprocess communication features of 4.4BSD Unix derived operating systems, and especially their applicability for real- time audio servers. The research ground of bringing real-time properties to tradi- tional Unix operating systems (such as 4.4BSD) is covered. Included are some design ideas used in BSD-variants, such as using multithreaded kernels, and schedulers that can provide real-time guarantees to processes. Factors affecting the design of real- time audio servers are considered, especially the suitability of various interprocess communication facilities as mechanisms to pass audio data between applications. To test these mechanisms on a real operating system, an audio server and a client utilizing these techniques is written and tested on an OpenBSD operating system. The performance of the audio server and OpenBSD is analyzed, with attempts to identify some bottlenecks of real-time operation in the OpenBSD system. Suomenkielinen tiivistelmä: Tämä tutkielma kattaa reaaliaikaisuus- ja prosessien väliset kommunikaatio-ominaisuudet, keskittyen 4.4BSD Unix -johdannaisiin käyt- töjärjestelmiin, ja erityisesti siihen kuinka hyvin nämä soveltuvat reaaliaikaisille äänipalvelinsovelluksille. Tutkimusalueeseen sisältyy reaaliaikaisuusominaisuuk- sien tuominen perinteisiin Unix-käyttöjärjestelmiin (kuten 4.4BSD:hen). Mukana on suunnitteluideoita, joita on käytetty joissakin BSD-varianteissa, kuten säikeis- tetyt kernelit, ja skedulerit, jotka voivat tarjota reaaliaikaisuustakeita prosesseille.
    [Show full text]
  • Nagios Core Version 3.X Documentation
    Nagios Core Version 3.x Documentation http://www.nagios.org Copyright © 2009 Nagios Core Development Team and Community Contributors. Copyright © 1999-2009 Ethan Galstad. Portions copyright by Nagios Community members. See the THANKS file for more information. Last Updated: 06-16-2009 [ Table of Contents ] Nagios, Nagios Core, NRPE, NSCA, and the Nagios logo are trademarks, servicemarks, registered servicemarks or registered trademarks of Nagios Enterprises. All other trademarks, servicemarks, registered trademarks, and registered servicemarks mentioned herein may be the property of their respective owner(s). The information contained herein is provided AS IS with NO WARRANTY OF ANY KIND, INCLUDING THE WARRANTY OF DESIGN, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE. 1 Nagios Core 3.x Documentation Table of Contents About What is Nagios? System requirements Licensing Downloading the latest version Release Notes What’s new in this version Known issues Support Nagios Support Portal Nagios Community Wiki Getting Started Advice for beginners Quickstart installation guide Upgrading from previous versions How to monitor a Windows machine How to monitor a Linux/Unix machine How to monitor a Netware server How to monitor a network printer How to monitor a router/switch How to monitor a publicly available service (HTTP, FTP, SSH, etc.) Configuring Nagios Configuration overview Main configuration file options Object configuration overview Object definitions CGI configuration file options Configuring authorization for the CGIs Running Nagios
    [Show full text]
  • Virtualization Techniques to Enable Transparent Access to Peripheral Devices Across Networks
    VIRTUALIZATION TECHNIQUES TO ENABLE TRANSPARENT ACCESS TO PERIPHERAL DEVICES ACROSS NETWORKS By NINAD HARI GHODKE A THESIS PRESENTED TO THE GRADUATE SCHOOL OF THE UNIVERSITY OF FLORIDA IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF MASTER OF SCIENCE UNIVERSITY OF FLORIDA 2004 Copyright 2004 by Ninad Hari Ghodke ACKNOWLEDGMENTS I would like to acknowledge Dr Renato Figueiredo for his direction and advice in this work and his patience in helping me write this thesis. I thank Dr Richard Newman and Dr Jose Fortes for serving on my committee and reviewing my work. I am grateful to all my friends and colleagues in the ACIS lab for their encouragement and help. Finally I would thank my family, for where and what I am now. This effort was sponsored by the National Science Foundation under grants EIA-0224442, ACI-0219925 and NSF Middleware Initiative (NMI) collaborative grant ANI-0301108. I also acknowledge a gift from VMware Corporation and a SUR grant from IBM. Any opinions, findings and conclusions or recommenda- tions expressed in this material are those of the author and do not necessarily reflect the views of NSF, IBM, or VMware. I would like to thank Peter Dinda at Northwestern University for providing access to resources. iii TABLE OF CONTENTS page ACKNOWLEDGMENTS ............................. iii LIST OF TABLES ................................. vi LIST OF FIGURES ................................ vii ABSTRACT .................................... viii CHAPTER 1 INTRODUCTION .............................. 1 2 APPLICATIONS ............................... 4 2.1 Network Computing in Grid and Utility Computing Environments 5 2.2 Pervasive Computing ......................... 7 3 SYSTEM CALL MODIFICATION ..................... 9 3.1 Introduction .............................. 9 3.2 Implementation ............................ 9 3.2.1 Architecture .........................
    [Show full text]
  • Status=Not/Inst/Cfg-Files/Unpacked
    Desired=Unknown/Install/Remove/Purge/Hold |Status=Not/Inst/Cfgfiles/Unpacked/Failedcfg/Halfinst/trigaWait/Trigpend |/Err?=(none)/Reinstrequired(Status,Err:uppercase=bad) ||/NameVersion Description +++=========================================================================== =============================================================================== ================================================================================ ===== ii0trace1.0bt4 0traceisatraceroutetoolthatcanberunwithinanexisting,open TCPconnectionthereforebypassingsometypesofstatefulpacketfilterswith ease. ii3proxy0.6.1bt2 3APA3A3proxytinyproxyserver iiace1.10bt2 ACE(AutomatedCorporateEnumerator)isasimpleyetpowerfulVoIPCo rporateDirectoryenumerationtoolthatmimicsthebehaviorofanIPPhoneinor dert iiadduser3.112ubuntu1 addandremoveusersandgroups iiadmsnmp0.1bt3 SNMPauditscanner. iiafflib3.6.10bt1 AnopensourceimplementationofAFFwritteninC. iiair2.0.0bt2 AIRisaGUIfrontendtodd/dc3dddesignedforeasilycreatingforen sicimages. iiaircrackng1.1bt9 Aircrackngwirelessexploitationandenumerationsuite iialacarte0.13.10ubuntu1 easyGNOMEmenueditingtool iialsabase1.0.22.1+dfsg0ubuntu3 ALSAdriverconfigurationfiles iialsatools1.0.220ubuntu1 ConsolebasedALSAutilitiesforspecifichardware iialsautils1.0.220ubuntu5 ALSAutilities iiamap5.2bt4 Amapisanextgenerationtoolforassistingnetworkpenetrationtesti ng.Itperformsfastandreliableapplicationprotocoldetection,independanton the iiapache22.2.145ubuntu8.4 ApacheHTTPServermetapackage iiapache2mpmprefork2.2.145ubuntu8.4 ApacheHTTPServertraditionalnonthreadedmodel
    [Show full text]
  • Linux Thin Client Networks Design and Deployment
    Linux Thin Client Networks Design and Deployment A quick guide for System Administrators David Richards BIRMINGHAM - MUMBAI Linux Thin Client Networks Design and Deployment A quick guide for System Administrators Copyright © 2007 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, Packt Publishing, nor its dealers or distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: August 2007 Production Reference: 1030807 Published by Packt Publishing Ltd. 32 Lincoln Road Olton Birmingham, B27 6PA, UK. ISBN 978-1-847192-04-2 www.packtpub.com Cover Image by Andrew Jalali (www.acjalali.com) Credits Author Project Manager David Richards Patricia Weir Reviewers Project Coordinator Diego Torres Milano Sagara Naik Blaine Hilton Indexer Senior Acquisition Editor Bhushan Pangaonkar David Barnes Proofreader Development Editor Chris Smith Nikhil Bangera Production Coordinator Technical Editor Shantanu Zagade Rajlaxmi Nanda Cover Designer Editorial Manager Shantanu Zagade Dipali Chittar About the Author David Richards is a System Administrator for the City of Largo, Florida.
    [Show full text]
  • Mikmod Sound Library Documentation Edition 1.3 August 2016
    MikMod Sound Library Documentation edition 1.3 August 2016 Miodrag Vallat ([email protected]) Copyright c 1998-2014 Miodrag Vallat and others | see file AUTHORS for complete list. This library is free software; you can redistribute it and/or modify it under the terms of the GNU Library General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WAR- RANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Library General Public License for more details. You should have received a copy of the GNU Library General Public License along with this library; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. Chapter 1: Introduction 1 1 Introduction The MikMod sound library is an excellent way for a programmer to add music and sound effects to an application. It is a powerful and flexible library, with a simple and easy-to-learn API. Besides, the library is very portable and runs under a lot of Unices, as well as under OS/2, MacOS and Windows. Third party individuals also maintain ports on other systems, including MS-DOS, and BeOS. MikMod is able to play a wide range of module formats, as well as digital sound files. It can take advantage of particular features of your system, such as sound redirection over the network. And due to its modular nature, the library can be extended to support more sound or module formats, as well as new hardware or other sound output capabilities, as they appear.
    [Show full text]
  • Software on Berserk
    - -4pc - -4pc Berserk User’s Guide Eric Nodwell Scott Webster Copyright © 2002-2004 Eric NodwellScott Webster This document can be freely redistributed according to the terms of the GNU General Public License. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". Table of Contents Introduction ..................................................................................... 3 What is the Berserk computer system? ........................................................ 3 Introduction to Command Line Linux ......................................................... 3 Guidelines - Getting Along With Other Users .................................................. 4 Use the cluster Luke! ....................................................................... 4 Berserk Features ................................................................................. 4 Printing .................................................................................... 4 Setting default print options ............................................................ 4 Setting print options from the command line .............................................. 6 Using xpp or kprinter instead of lpr .....................................................
    [Show full text]
  • Desejado=U=Desconhecido/Instalar
    Desejado=U=Desconhecido/Instalar/Remover/exPurgar/H=Reter Estado=Não/Inst/arqsCfg/U=Descomp/Falhoucfg/H=semiinst/W=trigadiado/Trig pend / Erro?=(nenhum)/H=Ret/precisaReinst/X=ambosproblemas (Est,Err: maiúsculas=r uim) / Nome Versão Descrição +++=========================================================================== ========================================================= ii acl 2.2.472 Access control list utilities ii acpi 1.21ubuntu1 displays information on ACPI devices ii acpisupport 0.121 scripts for handling many ACPI events ii acpid 1.0.69ubuntu4.9.04.3 Utilities for using ACPI power management ii adduser 3.110ubuntu5 add and remove users and groups ii aish 1.135 ish/base64/uuencoded_file converter ii alacarte 0.11.100ubuntu1 easy GNOME menu editing tool ii alsabase 1.0.18.dfsg1ubuntu8 ALSA driver configuration files ii alsautils 1.0.181ubuntu11 ALSA utilities ii anacron 2.313.1ubuntu6 cronlike program that doesn't go by time ii anyeventperl 1.020.2 provide framework for multiple event loops ii apache2 2.2.112ubuntu2.2 Apache HTTP Server metapackage ii apache2mpmworker 2.2.112ubuntu2.2 Apache HTTP Server high speed threaded mod ii apache2utils 2.2.112ubuntu2.2 utility programs for webservers ii apache2.2common 2.2.112ubuntu2.2 Apache HTTP Server common files ii apmd 3.2.212ubuntu3 Utilities for Advanced Power Management (APM ii appinstalldatapartner 11.9.04.2 Application Installer (data files for partne ii apport 1.00ubuntu5.2 automatically generate crash reports for deb ii apportgtk 1.00ubuntu5.2 GTK+ frontend for the
    [Show full text]