Menu
▾
▴
[Seq-cvs-commit] showeq AUTHORS,1.1,1.2 ChangeLog,1.1,1.2 Doxyfile,1.1,1.2 NEWS,1.1,1.2 doxygen.am,1.1,1.2 doxygen.cfg,1.1,1.2 showeq.kdevelop,1.1,1.2 BUGS,1.1.1.1,1.2 COPYING,1.1,1.2 FAQ,1.1,1.2 INSTALL,1.5,1.6 INSTALL.newbies,1.5,1.6 Makefile.am,1.1.1.1,1.2 Makefile.dist,1.3,1.4 README,1.3,1.4 ROADMAP,1.2,1.3 TODO,1.2,1.3 acinclude.m4,1.9,1.10 configure.in,1.54,1.55 CHANGES,1.139,NONE conf.h.in,1.8,NONE install-sh,1.1.1.1,NONE missing,1.1.1.1,NONE mkinstalldirs,1.1.1.1,NONE showeq.kdevprj,1.1,NONE
Update of /cvsroot/seq/showeq In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv14505 Modified Files: BUGS COPYING FAQ INSTALL INSTALL.newbies Makefile.am Makefile.dist README ROADMAP TODO acinclude.m4 configure.in Added Files: AUTHORS ChangeLog Doxyfile NEWS doxygen.am doxygen.cfg showeq.kdevelop Removed Files: CHANGES conf.h.in install-sh missing mkinstalldirs showeq.kdevprj Log Message: Merged pre_5_0_beta down to the trunk. pre_5_0_beta should be treated as closed. All future development will occur on the branch. Updated version to 5.1.0.0 in preparation for new expansion release pending fixes for live compatibility. --- mkinstalldirs DELETED --- Index: Makefile.dist =================================================================== RCS file: /cvsroot/seq/showeq/Makefile.dist,v retrieving revision 1.3 retrieving revision 1.4 diff -u -d -r1.3 -r1.4 --- Makefile.dist 21 Feb 2003 20:55:47 -0000 1.3 +++ Makefile.dist 13 Sep 2005 15:23:08 -0000 1.4 @@ -1,13 +1,174 @@ -#!/bin/bash -=- Ignore this, it's here so that VIM will format colors correctly. -default: all +LIBTOOLIZE = libtoolize +ACLOCAL = aclocal +AUTOHEADER = autoheader +AUTOMAKE = automake +AUTOCONF = autoconf +LIBTOOLIZE_ARGS = --force --copy --automake +ACLOCAL_ARGS = -I m4 +AUTOHEADER_ARGS = --force +AUTOMAKE_ARGS = --add-missing --copy --include-deps +AUTOCONF_ARGS = -all: +default: + @echo "***************************************************************" + @echo "Are you really sure you want to be running this makefile?" + @echo "Unless your are a developer you probably don't want" + @echo "to use this file. " + @if [ -d CVS ]; then \ + echo ""; \ + echo "In which case you should probably just use the tarball."; \ + echo "and not a direct checkout from CVS like this."; \ + fi + @if [ -f configure ]; then \ + echo ""; \ + echo "You probably just need to run './configure'."; \ + fi + @echo "" + @echo "***************************************************************" + @echo "" + @echo "" + @echo "-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-" + @echo "If you are REALLY sure that you want to make/remake the build" + @echo "system you can do so by using the 'help' target of this " + @echo "makefile to see a list of its supported targets. " + @echo "-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-" + +help: + @echo "***************************************************************" + @echo "Makefile.dist accepts the following targets:" + @echo " help - display this help" + @echo " all - performs a 'backup', and then 'build'" + @echo " backup - backs up the existing 'showeq' executable" + @echo " clean - attempts to remove all generated files" + @echo " build - performs a 'clean', and then builds the" + @echo " entire configuration system" + @echo " configure - builds configure" + @echo " autoconf - alias for 'configure'" + @echo " automake - runs 'automake' to generate 'Makefile.in'" + @echo " autoheader - runs 'autoheader' to generate 'config.h.in'" + @echo " aclocal - runs 'aclocal' to generate 'aclocal.m4'" + @echo " libtoolize - runs 'libtoolize' to setup 'libtool' support" + @echo "***************************************************************" + +all: backup build + +no-backup: build + +build: clean configure +# Pretty success message... Use of '&&' rather than ';' guarntees +# that if one portion of the compile process fails, the successor +# won't be executed. Again, this is another case of common sense. + + @echo "" + @echo "" + @echo "******************************************" + @echo "Success! Please type the following:" + @echo "" + @echo " ./configure && make && make install" + @echo "" + @echo "" + @echo "This will configure, compile, and install" + @echo "showeq " + @echo "******************************************" + @echo "" + +autoconf: configure + +configure: install-sh missing Makefile.in src/Makefile.in conf/Makefile.in configure.in Makefile.dist + @echo -n "Generating configure from configure.in......................" + @echo -e "\n*!* autoconf *!*" >> Makefile.dist.dbg + @-rm -f $@ + @$(AUTOCONF) $(AUTOCONF_ARGS) >> Makefile.dist.dbg 2>&1; + @echo "!*! autoconf !*!" >> Makefile.dist.dbg + @if [ -s "$@" ]; then { \ + echo " done!"; \ + } else { \ + echo " failed! ";\ + echo "See Makefile.dist.dbg for details"; \ + exit -1; \ + } fi + +automake: install-sh missing Makefile.in src/Makefile.in conf/Makefile.in + +install-sh missing Makefile.in src/Makefile.in conf/Makefile.in: config.h.in aclocal.m4 Makefile.dist + @echo -n "Generating Makefile.in from Makefile.am....................." + @echo -e "\n*!* automake ... *!*" >> Makefile.dist.dbg + @$(AUTOMAKE) $(AUTOMAKE_ARGS) >> Makefile.dist.dbg 2>&1 + @echo "!*! automake ... !*!" >> Makefile.dist.dbg + @if [ -s "$@" ]; then { \ + echo " done!"; \ + } else { \ + echo " failed! ";\ + echo "See Makefile.dist.dbg for details"; \ + exit -1; \ + } fi + + +autoheader: config.h.in +config.h.in: aclocal.m4 configure.in Makefile.dist + @echo -n "Generating configure headers (config.h.in).................." + @echo -e "\n*!* $$AUTOHEADER $$AUTOHEADER_ARGS configure.in *!*" >> Makefile.dist.dbg + @-rm -f config.h.in + @$(AUTOHEADER) $(AUTOHEADER_ARGS) configure.in >> Makefile.dist.dbg 2>&1; + @echo "!*! $$AUTOHEADER $$AUTOHEADER_ARGS configure.in !*!" >> Makefile.dist.dbg + @if [ -s "$@" ]; then { \ + echo " done!"; \ + } else { \ + echo " failed! ";\ + echo "See Makefile.dist.dbg for details"; \ + exit -1; \ + } fi + +aclocal: aclocal.m4 + +aclocal.m4: config.guess config.sub ltmain.sh configure.in Makefile.dist + @echo -n "Generating aclocal.m4 from configure.in....................." + @echo -e "\n*!* aclocal *!*" >> Makefile.dist.dbg + @$(ACLOCAL) $(ACLOCAL_ARGS) >> Makefile.dist.dbg 2>&1 + @echo "!*! aclocal !*!" >> Makefile.dist.dbg + @ if [ -s "$@" ]; then { \ + echo " done!"; \ + } else { \ + echo " failed! ";\ + echo "See Makefile.dist.dbg for details"; \ + exit -1; \ + } fi + +libtoolize: config.guess config.sub ltmain.sh + +config.guess config.sub ltmain.sh : configure.in Makefile.am Makefile.dist + @echo -n "Adding libtool support......................................" + @echo -e "\n*!* $$LIBTOOLIZE $$LIBTOOLIZE_ARGS *!*" \ + >> Makefile.dist.dbg + @$(LIBTOOLIZE) $(LIBTOOLIZE_ARGS) >> Makefile.dist.dbg 2>&1 + @echo "!*! $$LIBTOOLIZE $LIBTOOLIZE_ARGS !*!" >> Makefile.dist.dbg + @if [ -s "config.guess" -a "config.sub" -a "ltmain.sh" ]; then { \ + echo " done!"; \ + } else { \ + echo " failed! ";\ + echo "See Makefile.dist.dbg for details"; \ + exit -1; \ + } fi + + +clean: + @echo -n "Removing old files.........................................." + @if [ -f "Makefile" ]; then { \ + $(MAKE) -skf Makefile maintainer-clean >/dev/null; \ + } fi + @-rm -f Makefile.dist.dbg + @-rm -f configure + @-rm -f aclocal.m4 missing install-sh mkinstalldirs + @-rm -f Makefile Makefile.in src/Makefile src/Makefile.in conf/Makefile conf/Makefile.in + @-rm -fr autom4te.cache + @echo " done!" + +backup: # Backup the users current binary and place it in BACKUP/ ... # # This fixes the annoying "Build such and such destroyed my working # copy of ShowEQ!" messages on the SEQ Dev forums :) - @if [ -x "src/showeq" ] && ! [ -e ".no-backup" ]; then \ { \ mkdir -p "BACKUP"; \ @@ -124,311 +285,3 @@ \ echo "!*! BACKUP debug info !*!" >> Makefile.dist.dbg; \ } fi; - - @make -sf Makefile.dist no-backup - - -no-backup: - - @echo "-:- `exec date` -:-" > Makefile.dist.dbg - -# Don't automatically assume that a maintainer-clean is necessary. -# Only attempt to make a maintaner-clean IF the Makefile exists! -# It's a matter of common sense really :) - - @if [ -f "Makefile" ]; then \ - { \ - echo -ne "\nClearing all old Makefile data................" && \ - echo -n ".............."; \ - echo -e "\n*!* make -skf Makefile maintainer-clean *!*" \ - >> Makefile.dist.dbg; \ - make -skf Makefile maintainer-clean >> Makefile.dist.dbg 2>&1; \ - echo "!*! make -skf Makefile maintainer-clean !*!" \ - >> Makefile.dist.dbg; \ - echo " done!"; \ - echo ""; \ - echo ""; \ - } fi - - @echo -n "Adding libtool support......................................" - @echo -e "\n*!* libtoolize --force --copy --automake *!*" \ - >> Makefile.dist.dbg - @libtoolize --force --copy --automake >> Makefile.dist.dbg 2>&1 - @echo "!*! libtoolize --force --copy --automake !*!" \ - >> Makefile.dist.dbg - @echo " done!" - - @echo -n "Generating aclocal.m4 from configure.in and acinclude.m4...." - @echo -e "\n*!* aclocal *!*" >> Makefile.dist.dbg - @aclocal >> Makefile.dist.dbg 2>&1 - @echo "!*! aclocal !*!" >> Makefile.dist.dbg - @echo " done!" - - @echo -e "\n*!* Autoheader version check *!*" >> Makefile.dist.dbg - - @echo -ne "\nChecking Autoheader version...................." && \ - echo -n "............."; - - @if [ "$$AUTOHEADER" ]; then \ - { \ - echo " done!"; \ - \ - echo "!*! Autoheader version check !*!" \ - >> Makefile.dist.dbg; \ - \ - echo "Using user defined \$$AUTOHEADER: '$$AUTOHEADER'"; \ - \ - echo -ne "\nGenerating configure template (config.h)" && \ - echo -n "...................."; \ - \ - echo -e "\n*!* $$AUTOHEADER configure.in *!*" \ - >> Makefile.dist.dbg && \ - $$AUTOHEADER configure.in >> Makefile.dist.dbg 2>&1; \ - \ - echo " done!"; \ - \ - echo "!*! $$AUTOHEADER configure.in !*!" \ - >> Makefile.dist.dbg; \ - \ - } else { \ - \ - ahver=`autoheader --version 2>> Makefile.dist.dbg | \ - awk '{print $$3}'`; \ - \ - if [ "$$ahver" == "2.13" ]; then \ - { \ - ah=`type -p autoheader2.50 2> /dev/null`; \ - \ - if [ "$$ah" ]; then \ - { \ - ahver="2.50"; \ - } else { \ - ah="autoheader"; \ - } fi; \ - \ - AUTOHEADER="$$ah"; \ - \ - echo " done!"; \ - \ - echo "!*! Autoheader version check !*!" \ - >> Makefile.dist.dbg; \ - \ - echo -n ">> Using Autoheader version........" && \ - echo "......................... $$ahver!"; \ - } \ - \ - elif [ "$$ahver" ]; then \ - { \ - AUTOHEADER="autoheader"; \ - \ - echo " done!"; \ - \ - echo "!*! Autoheader version check !*!" \ - >> Makefile.dist.dbg; \ - \ - echo -n ">> Using Autoheader version........" && \ - echo "......................... $$ahver!"; \ - } fi; \ - \ - echo -ne "\nGenerating configure template (config.h)" && \ - echo -n "...................."; \ - \ - echo -e "\n*!* $$AUTOHEADER configure.in *!*" \ - >> Makefile.dist.dbg && \ - $$AUTOHEADER configure.in >> Makefile.dist.dbg 2>&1; \ - \ - echo " done!"; \ - \ - echo "!*! $$AUTOHEADER configure.in !*!" \ - >> Makefile.dist.dbg; \ - } fi; \ - \ - if ! [ -s "aclocal.m4" ]; then \ - { \ - echo ""; \ - echo "Autoheader has failed without warning!"; \ - echo ""; \ - echo "PLEASE NOTE: Your version of Autoheader sucks!"; \ - echo "UPGRADE NOW or face public humiliation..."; \ - echo ""; \ - \ - echo "FATAL ERROR: Autoheader is screwed up!!!" \ - >> Makefile.dist.dbg; \ - \ - exit -1; \ - } fi - - -# Better safe than sorry... Do these one at a time rather than doing -# them all at once. This fixes problems with older automake versions. - - @echo -n "Generating Makefile.in from Makefile.am....................." - @echo -e "\n*!* automake ... *!*" >> Makefile.dist.dbg - @automake --add-missing --foreign --include-deps ./Makefile \ - >> Makefile.dist.dbg 2>&1 - @automake --add-missing --foreign --include-deps src/Makefile \ - >> Makefile.dist.dbg 2>&1 - @automake --add-missing --foreign --include-deps maps/Makefile \ - >> Makefile.dist.dbg 2>&1 - @automake --add-missing --foreign --include-deps conf/Makefile \ - >> Makefile.dist.dbg 2>&1 - @echo "!*! automake ... !*!" >> Makefile.dist.dbg - @echo " done!" - - -# Autoconf is a major pain in the ASS!!! First try using it without -# specifying the output file, if that fails tell it off and give it -# the -o switch. -# -# -# Original script written by prox (for Debian UNSTABLE *ONLY*)... -# -# -# (10-16-2001) [Andon]: -# + Applied to *ALL* machines with the combination of Autoconf 2.13 -# AND Autoconf 2.50... -# - - @echo -e "\n*!* Autoconf version check *!*" >> Makefile.dist.dbg - - @echo -ne "\nChecking Autoconf version......................" && \ - echo -n "............."; - - @if [ "$$AUTOCONF" ]; then \ - { \ - echo " done!"; \ - \ - echo "!*! Autoconf version check !*!" \ - >> Makefile.dist.dbg; \ - \ - echo "Using user defined \$$AUTOCONF: '$$AUTOCONF'"; \ - \ - echo -ne "\nFinalizing Autoconf script (configure).." && \ - echo -n "...................."; \ - \ - echo -e "\n*!* $$AUTOCONF *!*" >> Makefile.dist.dbg && \ - $$AUTOCONF >> Makefile.dist.dbg 2>&1; \ - \ - echo " done!"; \ - \ - echo "!*! $$AUTOCONF !*!" >> Makefile.dist.dbg; \ - \ - } else { \ - \ - acver=`autoconf --version 2>> Makefile.dist.dbg | \ - awk '{print $$3}'`; \ - \ - if [ "$$acver" == "2.13" ]; then \ - { \ - ac=`type -p autoconf2.50 2> /dev/null`; \ - \ - if [ "$$ac" ]; then \ - { \ - acver="2.50"; \ - } else { \ - ac="autoconf"; \ - } fi; \ - \ - AUTOCONF="$$ac"; \ - \ - echo " done!"; \ - \ - echo "!*! Autoconf version check !*!" \ - >> Makefile.dist.dbg; \ - \ - echo -n ">> Using Autoconf version.........." && \ - echo "......................... $$acver!"; \ - } \ - \ - elif [ "$$acver" ]; then \ - { \ - AUTOCONF="autoconf"; \ - \ - echo " done!"; \ - \ - echo "!*! Autoconf version check !*!" \ - >> Makefile.dist.dbg; \ - \ - echo -n ">> Using Autoconf version.........." && \ - echo "......................... $$acver!"; \ - } fi; \ - \ - echo -ne "\nFinalizing Autoconf script (configure).." && \ - echo -n "...................."; \ - \ - echo -e "\n*!* $$AUTOCONF *!*" >> Makefile.dist.dbg && \ - $$AUTOCONF >> Makefile.dist.dbg 2>&1; \ - \ - echo "!*! $$AUTOCONF !*!" >> Makefile.dist.dbg; \ - } fi; \ - \ - if ! [ -s "configure" ]; then \ - { \ - echo -e "\n*!* $$AUTOCONF configure.in *!*" \ - >> Makefile.dist.dbg && \ - $$AUTOCONF configure.in >> Makefile.dist.dbg 2>&1; \ - \ - echo "!*! $$AUTOCONF configure.in !*!" \ - >> Makefile.dist.dbg; \ - } fi; \ - \ - if ! [ -s "configure" ]; then \ - { \ - echo ""; \ - echo "Strange Autoconf config present..."; \ - echo "Consider upgrading."; \ - echo ""; \ - \ - echo -e "\n*!* $$AUTOCONF configure configure.in *!*" \ - >> Makefile.dist.dbg && \ - $$AUTOCONF -o configure configure.in \ - >> Makefile.dist.dbg 2>&1; \ - \ - echo "!*! $$AUTOCONF configure configure.in !*!" \ - >> Makefile.dist.dbg; \ - } fi; \ - \ - if [ -s "configure" ]; then \ - { \ - echo " done!"; \ - } else { \ - echo " failed!"; \ - echo ""; \ - echo "PLEASE NOTE: Your version of Autoconf sucks!"; \ - echo "UPGRADE NOW or face public humiliation..."; \ - echo ""; \ - echo "FATAL ERROR: Autoconf is screwed up!!!" \ - >> Makefile.dist.dbg; \ - exit -1; \ - } fi - - - -# Some files, such as aclocal.m4, have no purpose once the autoconf -# script has been generated. It's a good idea to remove them... - - @echo -n "Releasing temporary file handles............................" - @rm -f aclocal.m4 - @echo " done!" - - - -# Pretty success message... Use of '&&' rather than ';' guarntees -# that if one portion of the compile process fails, the successor -# won't be executed. Again, this is another case of common sense. - - @echo ""; \ - echo ""; \ - echo "******************************************"; \ - echo "Success! Please type the following:"; \ - echo ""; \ - echo " ./configure && make"; \ - echo ""; \ - echo ""; \ - echo "This will configure and compile ShowEQ..."; \ - echo ""; \ - echo "If you are installing ShowEQ for the first"; \ - echo "time, be sure to add '&& make install' to"; \ - echo "the end of the compile process..."; \ - echo "******************************************"; \ - echo ""; Index: INSTALL =================================================================== RCS file: /cvsroot/seq/showeq/INSTALL,v retrieving revision 1.5 retrieving revision 1.6 diff -u -d -r1.5 -r1.6 --- INSTALL 30 Aug 2003 15:51:45 -0000 1.5 +++ INSTALL 13 Sep 2005 15:23:08 -0000 1.6 @@ -1,75 +1,305 @@ -INSTALLATION OVERVIEW: ----------------------- -ShowEQ originated on Redhat 6.1, however, it will compile and -run on all newer Linux distro's. You will need the QT library -from Troll Tech (http://www.troll.no) compiled with multi-threading -support enabled, as well as libpcap from the Lawrence Berkely National -Laboratory (www.tcpdump.org), also the GNU database library gdbm -(ftp.gnu.org), and pthread support (provided via glibc). Also -it can be configured to use Berkeley DB3 instead of gdbm. +Version: $Id$ $Name$ -Additionally, the need for the library libEQ.a has been removed. +Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software Foundation +gives unlimited permissino to copy distribute and modify it. +Portions Copyright 2003, 2004 Zaphod (do...@us...). +Overview +======== +This file describes what prerequisites are needed by ShowEQ and how to +install ShowEQ itself. If you are a new Linux/UNIX user you may also +wish to read INSTALL.newbies. Maps for use within ShowEQ may be found +in the showeq-maps tarball. -PRE-REQUISITES: ---------------- -Below is a list of packages you will need in order to compile ShowEQ: +Prerequisites +================== +Below is a list of packages you will need to have installed in order to +compile ShowEQ: - Name: Minimum: Suggested: - ----------------------------------- - *** 3rd party libraries *** - qt 3.0.5 (Must be compiled with -thread) - qt-devel 3.0.5 (Must be compiled with -thread) - libpcap 0.62 - gdbm 1.8.0 + Name: Minimum: Suggested: Source: + -------------------------------------------------------------------------- + *** 3rd party libraries *** + qt 3.2 Compiled with -thread) http://www.trolltech.com) + libpcap 0.62 http://www.tcpdump.org/ + gdbm 1.8.0 http://www.gnu.org/software/gdbm/ *** Optional 3rd party libraries *** - db3 3.2.9 3.3 (No db4 won't work) + db3 3.2.9 3.3 (Not db4) http://www.sleepycat.com/ *** C++ Compilation *** - glibc 2.2 2.3.2 - libstdc++ 3.0 3.2 - gcc 3.0 3.2 + glibc 2.2 2.3.2 http://www.gnu.org/software/libc/ + gcc 3.0.5 3.2 http://gcc.gnu.org/ + libstdc++ 3.0.5 3.2 http://gcc.gnu.org/ + -------------------------------------------------------------------------- - *** GNU tools *** - libtool 1.3.4-3 Most recent... - autoconf 2.13-1 Most recent... - automake 1.4-6 Most recent... - ----------------------------------- - NOTE: Higher versions of these libraries should work fine... -INSTALL PROCESS: ----------------- -First you must make the configure script, but after that -the basic install is the same as any other GNU package: +Basic Installation +================== - make -f Makefile.dist - ./configure - make - make install + The `configure' shell script attempts to guess correct values for +various system-dependent variables used during compilation. It uses +those values to create a `Makefile' in each directory of the package. +It may also create one or more `.h' files containing system-dependent +definitions. Finally, it creates a shell script `config.status' that +you can run in the future to recreate the current configuration, and a +file `config.log' containing compiler output (useful mainly for +debugging `configure'). -This installs showeq in /usr/local/bin, and puts maps and logs in -/usr/local/share/showeq. make install is important, the program will not -find maps without it. + It can also use an optional file (typically called `config.cache' +and enabled with `--cache-file=config.cache' or simply `-C') that saves +the results of its tests to speed up reconfiguring. (Caching is +disabled by default to prevent problems with accidental use of stale +cache files.) -If you want to make the CGI files, use - ./configure --enable-cgi=<path where cgi-bin files should reside> + If you need to do unusual things to compile the package, please try +to figure out how `configure' could check whether to do them, and mail +diffs or instructions to the address given in the `README' so they can +be considered for the next release. If you are using the cache, and at +some point `config.cache' contains results you don't want to keep, you +may remove or edit it. +To find out more about the options and arguments that the `configure' +script understands, type: + $ ./configure --help +at the command prompt in your ShowEQ source directory. + +The simplest way to compile this package is: -CONFIGURING AND USING: ----------------------- -Please note that ShowEQ requires root privileges, otherwise the pcap library + 1. `cd' to the directory containing the package's source code and type + `./configure' to configure the package for your system. If you're + using `csh' on an old version of System V, you might need to type + `sh ./configure' instead to prevent `csh' from trying to execute + `configure' itself. + + Running `configure' takes awhile. While running, it prints some + messages telling which features it is checking for. + + 2. Type `make' to compile the package. + + 3. Type `make install' to install the programs and any data files and + documentation. + + 4. You can remove the program binaries and object files from the + source code directory by typing `make clean'. To also remove the + files that `configure' created (so you can compile the package for + a different kind of computer), type `make distclean'. There is + also a `make maintainer-clean' target, but that is intended mainly + for the package's developers. If you use it, you may have to get + all sorts of other programs in order to regenerate files that came + with the distribution. + +Using ShowEQ: +====================== + + Please note that ShowEQ requires root privileges, otherwise the pcap library cannot be initialized and ShowEQ will fail to load... You should not use SEQ on a computer where root access presents a security issue. -Configuration values are stored in the file showeq.xml. This file will -be looked for in the local directory first, then the /usr/local/share/showeq -directory. The contents of this file are layed out in a fairly readable form -and comments are provided in the distributed seqdef.xml file. +ShowEQ's command line options can be seen by using the following command line: + showeq --help + +Installation Names +================== + + By default, `make install' will install the package's files in +`/usr/local/bin', `/usr/local/man', '/usr/local/share/showeq', etc. +You can specify an installation prefix other than `/usr/local' by giving +`configure' the option `--prefix=PATH'. + + You can specify separate installation prefixes for +architecture-specific files and architecture-independent files. If you +give `configure' the option `--exec-prefix=PATH', the package will use +PATH as the prefix for installing programs and libraries. +Documentation and other data files will still use the regular prefix. + + In addition, if you use an unusual directory layout you can give +options like `--bindir=PATH' to specify different values for particular +kinds of files. Run `configure --help' for a list of the directories +you can set and what kinds of files go in them. + + You can cause programs to be installed with an extra prefix or suffix on +their names by giving `configure' the option `--program-prefix=PREFIX' or +`--program-suffix=SUFFIX'. + +`configure' Invocation +====================== + + `configure' recognizes the following options to control how it +operates. + +`--help' +`-h' + Print a summary of the options to `configure', and exit. + +`--version' +`-V' + Print the version of Autoconf used to generate the `configure' + script, and exit. + +`--cache-file=FILE' + Enable the cache: use and save the results of the tests in FILE, + traditionally `config.cache'. FILE defaults to `/dev/null' to + disable caching. + +`--config-cache' +`-C' + Alias for `--cache-file=config.cache'. + +`--quiet' +`--silent' +`-q' + Do not print messages saying which checks are being made. To + suppress all normal output, redirect it to `/dev/null' (any error + messages will still be shown). + +`--srcdir=DIR' + Look for the package's source code in directory DIR. Usually + `configure' can determine that directory automatically. + +'--with-qt-dir=DIR' + Look for Qt in the specified directory. DIR defaults to the + value of your QTDIR environtment variable. + +'--with-qt-includes=DIR' + Look for Qt include files in the specified directory. DIR defaults + to $QTDIR/include. + +'--with-qt-libraries=DIR' + Look for Qt library files in the specified directory. DIR defaults + to $QTDIR/lib. + +'--x-includes=DIR' + Look for X include files in the specified directory. + +'--x-libraries=DIR' + Look for X library files in the specified directory. + +`configure' also accepts some other, not widely useful, options. Run +`configure --help' for more details. + +Defining Variables +================== + + Variables not defined in a site shell script can be set in the +environment passed to `configure'. However, some packages may run +configure again during the build, and the customized values of these +variables may be lost. In order to avoid this problem, you should set +them in the `configure' command line, using `VAR=value'. For example: + + ./configure CXX=/usr/local2/bin/g++ + +will cause the specified gcc to be used as the C compiler (unless it is +overridden in the site shell script). + +Some influential variables used in building ShowEQ are: + CXX C++ compiler command + CXXFLAGS C++ compiler flags + CC C compiler command + CFLAGS C compiler flags + LDFLAGS Linker flags + CPP C preprocessor + CPPFLAGS C/C++ preprocessor flags + QTDIR Specifies the base of the Qt installation + +Compilers and Options +===================== + + Some systems require unusual options for compilation or linking that +the `configure' script does not know about. Run `./configure --help' +for details on some of the pertinent environment variables. + + You can give `configure' initial values for configuration parameters +by setting variables in the command line or in the environment. Here +is an example: + + ./configure CC=gcc3 CXX=gcc3 CFLAGS=-O2 CXXFLAGS=-02 + + *Note Defining Variables::, for more details. + +Compiling For Multiple Architectures +==================================== + + You can compile the package for more than one kind of computer at the +same time, by placing the object files for each architecture in their +own directory. To do this, you must use a version of `make' that +supports the `VPATH' variable, such as GNU `make'. `cd' to the +directory where you want the object files and executables to go and run +the `configure' script. `configure' automatically checks for the +source code in the directory that `configure' is in and in `..'. + + If you have to use a `make' that does not support the `VPATH' +variable, you have to compile the package for one architecture at a +time in the source code directory. After you have installed the +package for one architecture, use `make distclean' before reconfiguring +for another architecture. + +Specifying the System Type +========================== + + There may be some features `configure' cannot figure out +automatically, but needs to determine by the type of machine the package +will run on. Usually, assuming the package is built to be run on the +_same_ architectures, `configure' can figure that out, but if it prints +a message saying it cannot guess the machine type, give it the +`--build=TYPE' option. TYPE can either be a short name for the system +type, such as `sun4', or a canonical name which has the form: + + CPU-COMPANY-SYSTEM + +where SYSTEM can have one of these forms: + + OS KERNEL-OS + + See the file `config.sub' for the possible values of each field. If +`config.sub' isn't included in this package, then this package doesn't +need to know the machine type. + + If you are _building_ compiler tools for cross-compiling, you should +use the `--target=TYPE' option to select the type of system they will +produce code for. + + If you want to _use_ a cross compiler, that generates code for a +platform different from the build platform, you should specify the +"host" platform (i.e., that on which the generated programs will +eventually be run) with `--host=TYPE'. + +Sharing Defaults +================ + + If you want to set default values for `configure' scripts to share, +you can create a site shell script called `config.site' that gives +default values for variables like `CC', `cache_file', and `prefix'. +`configure' looks for `PREFIX/share/config.site' if it exists, then +`PREFIX/etc/config.site' if it exists. Or, you can set the +`CONFIG_SITE' environment variable to the location of the site script. +A warning: not all `configure' scripts look for a site script. + +Rebuilding Configuration Files +============================== + +Below is a list of packages needed to generate ShowEQ's build system. + + Name: Minimum: Suggested: Source: + --------------------------------------------------------------------------- + *** GNU tools *** + libtool 1.3.4-3 Most recent... http://www.gnu.org/software/libtool/ + autoconf 2.53 Most recent... http://www.gnu.org/software/autoconf/ + automake 1.9 Most recent... http://www.gnu.org/software/automake/ + perl 5.0 Most recent... http://www.perl.org/ + --------------------------------------------------------------------------- + + The best way to generate/regenerate the configuration files is by running +make on the 'Makefile.dist' included in the CVS repository, find out about it's +options by using the command line: + make -f Makefile.dist help + + The file `configure.in' is used to create `configure' by a program +called `autoconf' and to create config.h.in by a program called 'autoheader'. +You only need `configure.in' if you want to change it or regenerate +`configure' using a newer version of `autoconf'. + + The file 'Makefile.am' in both the top level and sub-directories are used to +create the 'Makefile.in' files by a program called 'automake'. These files +are in turn used by the configure program to generate the 'Makefile' files. -Filters for 'hiding' spawns from the spawnlist and map can be configured via -a file specified in the config file (typically 'filters.conf'). A sample -file has been included in the distribution which should be self explanatory. -Spawn Alert filters can also be configured here. Improving the documentation -of alerts and filters is an area where volunteers may help a lot. Index: configure.in =================================================================== RCS file: /cvsroot/seq/showeq/configure.in,v retrieving revision 1.54 retrieving revision 1.55 diff -u -d -r1.54 -r1.55 --- configure.in 9 Jun 2004 21:37:59 -0000 1.54 +++ configure.in 13 Sep 2005 15:23:08 -0000 1.55 @@ -1,10 +1,26 @@ dnl Process this file with autoconf to produce a configure script. -AC_INIT(src/main.cpp) +dnl $Id$ $Name$ + +AC_PREREQ(2.59) +AC_INIT(showeq, 5.1.0.0) +AC_CONFIG_SRCDIR(src/main.cpp) AC_CANONICAL_SYSTEM -AM_CONFIG_HEADER(conf.h) -AM_INIT_AUTOMAKE(showeq, 4.3.22) + +AM_CONFIG_HEADER(config.h) +AM_INIT_AUTOMAKE(1.9 dist-bzip2) AM_MAINTAINER_MODE +dnl doxygen macros +DX_HTML_FEATURE(ON) +DX_CHM_FEATURE(OFF) +DX_CHI_FEATURE(OFF) +DX_MAN_FEATURE(OFF) +DX_RTF_FEATURE(OFF) +DX_XML_FEATURE(OFF) +DX_PDF_FEATURE(OFF) +DX_PS_FEATURE(OFF) +DX_INIT_DOXYGEN(ShowEQ, doxygen.cfg, dox) + dnl Use CCd/CXXd rather than CC/CXX otherwise it cache's the value dnl and prevents the alternate search from working. Would be better dnl if there was someway to invalidate the cache entry. ?? @@ -27,7 +43,7 @@ ;; esac] ) -AC_DEFUN(CHECK_COMPILER,[ +AC_DEFUN([CHECK_COMPILER],[ ac_save_cxxflags="$CXXFLAGS" if [[ "$ac_cv_showeq_old_compiler" == "yes" ]]; then CXXFLAGS="$CXXFLAGS -DOLDCOMPILER" @@ -135,13 +151,14 @@ ) AC_PATH_QT_MOC +AC_PATH_QT_UIC AC_PATH_QT dnl The below needs to be re-defined since the Qt defines from KDE destroy it AC_LANG_CPLUSPLUS dnl Check taken from SINS 0.5 -AC_DEFUN(SHOWEQ_CHECK_THREADING,[ +AC_DEFUN([SHOWEQ_CHECK_THREADING],[ AC_LANG_CPLUSPLUS USE_THREADS="" LIBGETOPT="" @@ -511,10 +528,10 @@ AC_CHECK_RPATH -CFLAGS="$USE_THREADS $USE_OPT_C $USE_DEBUG_C $USE_INLINE_C $USE_PROFILE_C" -CXXFLAGS="$USE_THREADS $USE_OPT_CXX $USE_DEBUG_CXX $USE_INLINE_CXX $USE_PROFILE_CXX -DQT_THREAD_SUPPORT=1 -DDISPLAY_ICONS=${CGI_ICONS} -DICON_DIR=\\\"${CGI_ICON_DIR}\\\"" +CFLAGS="$USE_THREADS $USE_OPT_C $USE_DEBUG_C $USE_INLINE_C $USE_PROFILE_C $CFLAGS" +CXXFLAGS="$USE_THREADS $USE_OPT_CXX $USE_DEBUG_CXX $USE_INLINE_CXX $USE_PROFILE_CXX -DQT_THREAD_SUPPORT=1 -DDISPLAY_ICONS=${CGI_ICONS} -DICON_DIR=\\\"${CGI_ICON_DIR}\\\" $CXXFLAGS" -AC_DEFUN(SUCCESS,[ +AC_DEFUN([SUCCESS],[ echo "Success!" case $target_os in solaris*) @@ -531,5 +548,5 @@ esac ]) -AC_OUTPUT([Makefile src/Makefile maps/Makefile conf/Makefile]) +AC_OUTPUT([Makefile src/Makefile conf/Makefile]) SUCCESS Index: acinclude.m4 =================================================================== RCS file: /cvsroot/seq/showeq/acinclude.m4,v retrieving revision 1.9 retrieving revision 1.10 diff -u -d -r1.9 -r1.10 --- acinclude.m4 21 Feb 2003 19:16:20 -0000 1.9 +++ acinclude.m4 13 Sep 2005 15:23:08 -0000 1.10 @@ -33,7 +33,7 @@ dnl Find a file (or one of more files in a list of dirs) dnl ------------------------------------------------------------------------ dnl -AC_DEFUN(AC_FIND_FILE, +AC_DEFUN([AC_FIND_FILE], [ $3=NO for i in $2; @@ -48,7 +48,7 @@ done ]) [...1009 lines suppressed...] AC_LANG_SAVE kde_safe_cxxflags=$CXXFLAGS @@ -3020,7 +3168,7 @@ AC_LANG_RESTORE ]) -AC_DEFUN(KDE_CHECK_QWSPRITEFIELD, +AC_DEFUN([KDE_CHECK_QWSPRITEFIELD], [ KDE_CHECK_HEADER(QwSpriteField.h, , [ @@ -3030,7 +3178,7 @@ ]) ]) -AC_DEFUN(KDE_SET_PREFIX, +AC_DEFUN([KDE_SET_PREFIX], [ dnl make $KDEDIR the default for the installation AC_PREFIX_DEFAULT(${KDEDIR:-/usr/local/kde}) --- NEW FILE: doxygen.am --- # Copyright (C) 2004 Oren Ben-Kiki # This file is distributed under the same terms as the Automake macro files. # Generate automatic documentation using Doxygen. Goals and variables values # are controlled by the various DX_COND_??? conditionals set by autoconf. # # The provided goals are: # doxygen-doc: Generate all doxygen documentation. # doxygen-run: Run doxygen, which will generate some of the documentation # (HTML, CHM, CHI, MAN, RTF, XML) but will not do the post # processing required for the rest of it (PS, PDF, and some MAN). # doxygen-man: Rename some doxygen generated man pages. # doxygen-ps: Generate doxygen PostScript documentation. # doxygen-pdf: Generate doxygen PDF documentation. # # Note that by default these are not integrated into the automake goals. If # doxygen is used to generate man pages, you can achieve this integration by # setting man3_MANS to the list of man pages generated and then adding the # dependency: # # $(man3_MANS): doxygen-doc # # This will cause make to run doxygen and generate all the documentation. # # The following variable is intended for use in Makefile.am: # # DX_CLEANFILES = everything to clean. # # This is usually added to MOSTLYCLEANFILES. ## --------------------------------- ## ## Format-independent Doxygen rules. ## ## --------------------------------- ## if DX_COND_doc ## ------------------------------- ## ## Rules specific for HTML output. ## ## ------------------------------- ## if DX_COND_html DX_CLEAN_HTML = @DX_DOCDIR@/html endif DX_COND_html ## ------------------------------ ## ## Rules specific for CHM output. ## ## ------------------------------ ## if DX_COND_chm DX_CLEAN_CHM = @DX_DOCDIR@/chm if DX_COND_chi DX_CLEAN_CHI = @DX_DOCDIR@/@PACKAGE@.chi endif DX_COND_chi endif DX_COND_chm ## ------------------------------ ## ## Rules specific for MAN output. ## ## ------------------------------ ## if DX_COND_man DX_CLEAN_MAN = @DX_DOCDIR@/man endif DX_COND_man ## ------------------------------ ## ## Rules specific for RTF output. ## ## ------------------------------ ## if DX_COND_rtf DX_CLEAN_RTF = @DX_DOCDIR@/rtf endif DX_COND_rtf ## ------------------------------ ## ## Rules specific for XML output. ## ## ------------------------------ ## if DX_COND_xml DX_CLEAN_XML = @DX_DOCDIR@/xml endif DX_COND_xml ## ----------------------------- ## ## Rules specific for PS output. ## ## ----------------------------- ## if DX_COND_ps DX_CLEAN_PS = @DX_DOCDIR@/@PACKAGE@.ps DX_PS_GOAL = doxygen-ps doxygen-ps: @DX_DOCDIR@/@PACKAGE@.ps @DX_DOCDIR@/@PACKAGE@.ps: @DX_DOCDIR@/@PACKAGE@.tag cd @DX_DOCDIR@/latex; \ rm -f *.aux *.toc *.idx *.ind *.ilg *.log *.out; \ $(DX_LATEX) refman.tex; \ $(MAKEINDEX_PATH) refman.idx; \ $(DX_LATEX) refman.tex; \ countdown=5; \ while $(DX_EGREP) 'Rerun (LaTeX|to get cross-references right)' \ refman.log > /dev/null 2>&1 \ && test $$countdown -gt 0; do \ $(DX_LATEX) refman.tex; \ countdown=`expr $$countdown - 1`; \ done; \ $(DX_DVIPS) -o ../@PACKAGE@.ps refman.dvi endif DX_COND_ps ## ------------------------------ ## ## Rules specific for PDF output. ## ## ------------------------------ ## if DX_COND_pdf DX_CLEAN_PDF = @DX_DOCDIR@/@PACKAGE@.pdf DX_PDF_GOAL = doxygen-pdf doxygen-pdf: @DX_DOCDIR@/@PACKAGE@.pdf @DX_DOCDIR@/@PACKAGE@.pdf: @DX_DOCDIR@/@PACKAGE@.tag cd @DX_DOCDIR@/latex; \ rm -f *.aux *.toc *.idx *.ind *.ilg *.log *.out; \ $(DX_PDFLATEX) refman.tex; \ $(DX_MAKEINDEX) refman.idx; \ $(DX_PDFLATEX) refman.tex; \ countdown=5; \ while $(DX_EGREP) 'Rerun (LaTeX|to get cross-references right)' \ refman.log > /dev/null 2>&1 \ && test $$countdown -gt 0; do \ $(DX_PDFLATEX) refman.tex; \ countdown=`expr $$countdown - 1`; \ done; \ mv refman.pdf ../@PACKAGE@.pdf endif DX_COND_pdf ## ------------------------------------------------- ## ## Rules specific for LaTeX (shared for PS and PDF). ## ## ------------------------------------------------- ## if DX_COND_latex DX_CLEAN_LATEX = @DX_DOCDIR@/latex endif DX_COND_latex .PHONY: doxygen-run doxygen-doc $(DX_PS_GOAL) $(DX_PDF_GOAL) .INTERMEDIATE: doxygen-run $(DX_PS_GOAL) $(DX_PDF_GOAL) doxygen-run: @DX_DOCDIR@/@PACKAGE@.tag doxygen-doc: doxygen-run $(DX_PS_GOAL) $(DX_PDF_GOAL) @DX_DOCDIR@/@PACKAGE@.tag: $(DX_CONFIG) $(pkginclude_HEADERS) rm -rf @DX_DOCDIR@ $(DX_ENV) $(DX_DOXYGEN) $(srcdir)/$(DX_CONFIG) DX_CLEANFILES = \ @DX_DOCDIR@/@PACKAGE@.tag \ -r \ $(DX_CLEAN_HTML) \ $(DX_CLEAN_CHM) \ $(DX_CLEAN_CHI) \ $(DX_CLEAN_MAN) \ $(DX_CLEAN_RTF) \ $(DX_CLEAN_XML) \ $(DX_CLEAN_PS) \ $(DX_CLEAN_PDF) \ $(DX_CLEAN_LATEX) endif DX_COND_doc Index: COPYING =================================================================== RCS file: /cvsroot/seq/showeq/COPYING,v retrieving revision 1.1 retrieving revision 1.2 diff -u -d -r1.1 -r1.2 --- COPYING 24 May 2002 19:15:10 -0000 1.1 +++ COPYING 13 Sep 2005 15:23:08 -0000 1.2 @@ -2,7 +2,7 @@ Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. - 675 Mass Ave, Cambridge, MA 02139, USA + 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. @@ -278,3 +278,63 @@ POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + <one line to give the program's name and a brief idea of what it does.> + Copyright (C) <year> <name of author> + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU 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 WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program; if not, write to the Free Software + Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + + +Also add information on how to contact you by electronic and paper mail. + +If the program is interactive, make it output a short notice like this +when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) year name of author + Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, the commands you use may +be called something other than `show w' and `show c'; they could even be +mouse-clicks or menu items--whatever suits your program. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the program, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the program + `Gnomovision' (which makes passes at compilers) written by James Hacker. + + <signature of Ty Coon>, 1 April 1989 + Ty Coon, President of Vice + +This General Public License does not permit incorporating your program into +proprietary programs. If your program is a subroutine library, you may +consider it more useful to permit linking proprietary applications with the +library. If this is what you want to do, use the GNU Library General +Public License instead of this License. --- showeq.kdevprj DELETED --- --- NEW FILE: NEWS --- This is a terse description of the features added to 5.0.0.17 since the release of 5.0.0.16. 1. New network code to support live EverQuest servers after 1/26/2005 patch 2. Updated zoneopcodes.xml and worldopcodes.xml after all opcodes changed with the 1/26/2005 patch -- This is a terse description of the features added to 5.0.0.15 since the release of 5.0.0.14. 1. Made ShowEQ more GNU style friendly (Added this file 'NEWS', renamed CHANGES to ChangeLog, added an extremely incomplete AUTHORS file. 2. Moved the maps into a seperate repository and package 'showeq-maps'. 3. Migrated the distribution of ShowEQ to tarballs and packages, instead of directly off CVS. --- CHANGES DELETED --- Index: FAQ =================================================================== RCS file: /cvsroot/seq/showeq/FAQ,v retrieving revision 1.1 retrieving revision 1.2 diff -u -d -r1.1 -r1.2 --- FAQ 4 Jan 2002 14:35:10 -0000 1.1 +++ FAQ 13 Sep 2005 15:23:08 -0000 1.2 @@ -1,6 +1,12 @@ -ShowEQ Version 4 Frequently Asked Questions +ShowEQ Frequently Asked Questions -FIXME: table of contents :) +1) Hit points always say 65536, 0, 100, etc, what is wrong +2) Why wont ShowEQ show me the loot my mob will drop +3) My faction is broken! It used to tell me my faction numbers when i + conned someone, now i get a number like 4 or 1. +4) What happened to experience? +5) Seq keeps crashing with "!!!! EQPacketFragmentSequence::addFragment(): + buffer overflow adding in new fragment". Why won't you fix this? 1) Hit points always say 65536, 0, 100, etc, what is wrong @@ -37,3 +43,82 @@ should draw the experience bar. We do however know what mob you killed and experience formulas, so what you see in the experience window now will be close estimates of the real exp you have. + + +5) Seq keeps crashing with "!!!! EQPacketFragmentSequence::addFragment(): + buffer overflow adding in new fragment". Why won't you fix this? + +This isn't actually a problem with seq, but rather the result of your +configuration on your linux box. Your linux box is not handling all the packets +it is receiving with its network card in promiscuous mode. + +In order to run, showeq needs the entire packet stream between the EQ client and +the EQ servers. Packets are processed in order and if any packets are dropped, +there may be problems decoding the stream causing showeq to crash or lose sync +with the session. + +Usually this condition is signalled by console messages like: +Warning: SEQ: Giving up on finding arq 0085 in stream zone-client cache, skipping! +Warning: SEQ: Giving up on finding arq 0086 in stream zone-client cache, skipping! +Warning: SEQ: Giving up on finding arq 0087 in stream zone-client cache, skipping! +Warning: SEQ: Giving up on finding arq 0088 in stream zone-client cache, skipping! + +This signifies packets being dropped and being skipped in processing, which may +cause the session stream to corrupt if the skipped packets are important. Other +messages which may result when the stream is corrupted are: + +Warning: Oversized packet fragment requested buffer of size 0 on stream 3 OpCode +0000 seq 00a6 + +Warning: !!!! EQPacketFragmentSequence::addFragment(): buffer overflow adding in +new fragment to buffer with seq 00fb on stream 3, opcode 0000. Buffer is size 3 +8302 and has been filled up to 38302, but tried to add 505 more! + +Both these messages mean that packets are being dropped that are important to +the reconstruction of oversized payloads in the session stream. These messages +may appear like showeq is broken, but in reality, the problem is that packets +are not being provided to showeq because they are being dropped by the kernel +before being made available to the application layer. + +The kernel may drop packets when under heavy loads (either CPU loads or network +loads). + +When under high CPU utilization, the thread in showeq which reads from +the kernel's receive buffers may be starved and not get enough processor time to +empty the kernel receive buffers before those buffers run out of room and drop +packets. To help this, you can set the showeq network thread to run "realtime" +by turning on the Network->Real Time Thread option. + +When under high network traffic, the kernel's receive buffers may overflow +before showeq gets a chance to empty the buffers, causing packets to be missed. +This can happen when you have a lot of network traffic that is seen by the +machine running showeq. The EQ client bursts a lot of traffic during zoning as +well, so usually problems with high network traffic show themselves during +zoning. + +To help this problem, try to narrow down the traffic that showeq watches by +specifying the ip address of your EQ client on the commandline. Also, turn on +Session Tracking using Network->Session Tracking. If problems persist after +turning those options on, you may want to adjust kernel parameters to change how +the kernel manages its receive buffers. Some parameters that may help you are: + +net.core.rmem_default (defaults to 65535, or 64k receive buffers) +net.core.rmem_max (defaults to 131071, or 128k receive buffers) +net.core.netdev_max_backlog (defaults to 300, or 300 packets can be input but + unprocessed before packets start being dropped) + +These parameters should be set with care, and take into account what other +things the linux box you are running showeq on is used for. If it has a lot of +server duties, setting rmem_default will increase system memory usage +significantly. + +Suggested settings for a normally used machine are: +net.core.rmem_default=524288 (512k for default receive buffers) +net.core.rmem_max=2097152 (2M for max receive buffers) +net.core.netdev_max_backlog=3000 (allow 3000 packets to be queued before + processing before dropping packets) + +If you still see problems, you may want to set these higher. Setting these may +be distribution specific. Check to see if you have sysctl (man sysctl) or +/etc/sysctl.conf, or these can be put directly into /proc by looking +in /proc/sys/net/core. --- conf.h.in DELETED --- Index: ROADMAP =================================================================== RCS file: /cvsroot/seq/showeq/ROADMAP,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- ROADMAP 12 Jun 2002 21:34:11 -0000 1.2 +++ ROADMAP 13 Sep 2005 15:23:08 -0000 1.3 @@ -1,3 +1,5 @@ +Version: $Header$ $Name$ + Files: ./ - Base directory of the ShowEQ CVS checkout ROADMAP - This file Index: Makefile.am =================================================================== RCS file: /cvsroot/seq/showeq/Makefile.am,v retrieving revision 1.1.1.1 retrieving revision 1.2 diff -u -d -r1.1.1.1 -r1.2 --- Makefile.am 19 Dec 2001 00:36:35 -0000 1.1.1.1 +++ Makefile.am 13 Sep 2005 15:23:08 -0000 1.2 @@ -1,13 +1,34 @@ -SUBDIRS=maps src conf +ACLOCAL_AMFLAGS = -I m4 +AUTOMAKE_OPTIONS = 1.9 dist-bzip2 -EXTRA_DIST=CHANGES BUGS showeq.1 +SUBDIRS = src conf -MAINTAINERCLEANFILES= aclocal.m4 config.guess config.sub configure Makefile.in \ -ltconfig libqt2.dbg libqt3.dbg Makefile.dist.dbg configure.dbg config.log \ -ltmain.sh stamp-h.in stamp-h +include doxygen.am -CLEANFILES=configure.dbg libqt2.dbg libqt3.dbg +EXTRA_DIST = BUGS ChangeLog FAQ INSTALL.newbies Makefile.dist README.libEQ \ +ROADMAP showeq.1 TODO showeq.kdevelop Doxyfile depcomp $(DX_CONFIG) + +MAINTAINERCLEANFILES = aclocal.m4 config.guess config.sub configure \ +Makefile.in ltconfig libqt2.dbg libqt3.dbg Makefile.dist.dbg \ +configure.dbg config.log ltmain.sh stamp-h.in stamp-h qt.tag depcomp + +@DX_DOCDIR@/@PACKAGE@.tag: qt.tag + +qt.tag: $(QT_DOCS)/index.html $(QT_DOCS)/qobject.html + doxytag -t qt.tag $(QT_DOCS) + +doxygen-installdox: doxygen-doc dox/html/installdox + if [ -x "@DX_DOCDIR@/html/installdox" ]; then \ + cd @DX_DOCDIR@/html; \ + ./installdox -l qt.tag@http://doc.trolltech.com/3.3/ -q; \ + fi + +MOSTLYCLEANFILES = $(DX_CLEANFILES) + +CLEANFILES = configure.dbg libqt2.dbg libqt3.dbg dist-hook: mkdir -p $(distdir)/doc cp -p $(srcdir)/doc/*.txt $(distdir)/doc + cp -p $(srcdir)/doc/*.doc $(distdir)/doc + cp -p $(srcdir)/doc/*.html $(distdir)/doc --- NEW FILE: doxygen.cfg --- # Doxyfile 1.3.7 #--------------------------------------------------------------------------- # Project related configuration options #--------------------------------------------------------------------------- PROJECT_NAME = $(PROJECT)-$(VERSION) PROJECT_NUMBER ... [truncated message content] |
