📄 installation.sgml
字号:
<!-- -*- sgml -*- --><!-- DOCTYPE book PUBLIC "-//Davenport//DTD DocBook//EN" []--><!-- Installation and Configuration of GXSNMP --><sect1 id="installation"> <title>Installation</title> <para> Installation of GxSNMP can be a tedious and time consuming task. If you take your time and follow the instructions contained in this guide you will find that GxSNMP will be a powerful addtion to your network management toolbox. </para> <para> In this chapter we will assume basic knowledge of your chosen opertation system and/or distribution. </para></sect1><sect1 id="obtain-latest"> <title>Obtaining the latest version</title> <para> The latest released versions of GXSNMP shall be available from http://www.gxsnmp.org. </para><sect1 id="prequisites"> <title>Before you install</title> <para> GxSNMP is a complex package and depends on a few other packages to be properly configured and installed before you can build it sucessfully. This section will detail out the packages and version of those packages that GxSNMP depends on. We will not discuss specific installation issues with the external packages as that is beyond the scope of this document. Where needed we will detail out the required settings. </para></sect1><sect1 id="reporting-bugs"> <title>Reporting Bugs</title> <para> If you have found a bug in GXSNMP we need to know about it to fix it. In order to assist us in tracking it down we will need complete information from you. You should detail out the OS version, what version of GXSNMP (as reported by Help->About GXSNMP), and the exact circumstances leading up to the bug. This should include as much detail as possible. Remember the more detailed the report the more likely that it will be fixed. </para> <para> Its recommened that you try and follow all the procedures listed here though if you don't have time please report the bug anyway -- even vague bug reports are better then none at all. </para> <sect2> <title>Compilation Problems</title> <para> While every effort has been made to make GXSNMP compile on as wide a range of operating systems as possible there are times it fails to compile. In order for us to help you resolve the difficulties we will need the following information from you. </para> <para> If you are experiencing problems while running GXSNMP please see <xref linkend="run-time-problems">. </para> <itemizedlist> <listitem> <para>Everything that was printed out when you first ran ./configure.</para> </listitem> <listitem> <para>The complete contents of the 'config.log' file.</para> </listitem> </itemizedlist> <para> If the compilation failed because a required library was not installed and you have installed the required library and its still not finding it make sure you have removed the old config.cache and try the configure again. </para> </sect2> <sect2 id="run-time-problems"> <title>Run-Time Problems</title> <para> Some things to keep in mind when you report run-time problems to us. </para> <itemizedlist> <listitem><para>Compile with debugging info. (make CFLAGS=-g will do this)</para> </listitem> <listitem><para>Also define DEBUG in config.h so that the extra debugging information will get compiled in. A future version will have rutime debuging that will be able to be turned on and off at will.</para> </listitem> <listitem><para>What platform are you running on? Autoconf packages include a neat little config.guess shell script, the output of this will suffice here.</para> </listitem> <listitem><para>What triggers this bug? Please try and be as specific as possible here.</para> </listitem> <listitem><para>If this is related to any of the SNMP functions of GXSNMP we will need information on the remote system as well. This should include: </para> <itemizedlist> <listitem><para>Vendor</para> </listitem> <listitem><para>Software Revision</para> </listitem> <listitem><para>What SNMP version you were using</para> </listitem> </itemizedlist> </listitem> </itemizedlist> <para> When you installed the gnome libraries a script called 'gnome-bug' was installed that will automate all of this for you. It is highly recommended that you use this. </para> </sect2> <sect2 id="known-problems"> <title>Known Problems</title> <para> The list included here is things we currently know about. </para> <itemizedlist> <listitem><para>ping.c fails to compile</para> <para> This is usually caused by an older libc problem, we have tried to insure that this will work everywhere but it still fails on some machines. Unfortantly the only recourse now left is for you to upgrade your libc or provide us with a patch. </para> </listitem> </itemizedlist> </sect2></sect1><sect1 id="configuring"> <title>Configuration</title> <para> After you have sucessfully installed GXSNMP and the first time you run it you will be presented with a window that looks something like what is show in <xref linkend="initial-window.jpg">.</para> <figure id="initial-window.jpg"> <title>Initial GXSNMP window.</title> <screenshot> <graphic fileref="images/initial-window.jpg"></graphic> </screenshot> </figure> <sect2 id="setting-up-database"> <title>Setting up the Database</title> <para> Not written yet. </para> <figure id="database-configuration.jpg"> <title>Configuring the Database</title> <screenshot> <graphic fileref="images/database-configuration.jpg"></graphic> </screenshot> </figure> </sect2> <sect2 id="setting-snmp"> <title>Setting up SNMP configuration</title> <para> Not written yet. </para> <figure id="snmp-configuration.jpg"> <title>SNMP Configuration Dialog</title> <screenshot> <graphic fileref="images/snmp-configuration.jpg"></graphic> </screenshot> </figure> </sect2></sect1><!-- Keep this comment at the end of the fileLocal variables:mode: sgmlsgml-omittag:tsgml-shorttag:tsgml-minimize-attributes:nilsgml-always-quote-attributes:tsgml-indent-step:2sgml-indent-data:tsgml-parent-document:nilsgml-exposed-tags:nilsgml-local-catalogs:nilsgml-local-ecat-files:nilEnd:-->
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -