mirror of
git://scm.dxcluster.org/scm/spider
synced 2024-09-21 07:47:10 +00:00
updated dxoldtonew.pl to be more modern...
This commit is contained in:
minima
parent
7f77f123e7
commit
ebba9c9a99
7
Changes
7
Changes
@ -1,3 +1,10 @@
|
||||
29Dec03=======================================================================
|
||||
1. updated dxoldtonew.pl so that it takes an AK1A DX.DAT file (argument on
|
||||
command line or a default of /spider/data/DX.DAT and outputs the standard
|
||||
DXSpider format spot files. Please be warned that if any of these files
|
||||
already exist, the data will be appended onto the end of the file. Please
|
||||
make sure you have backups or at least be aware that this may give strange
|
||||
results which may be 'out of order'.
|
||||
24May03=======================================================================
|
||||
1. Added more french translations from Robert (HB9BZA) and we now have some
|
||||
french help as well (also from Robert). A splendid effort. Thank you.
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider Administration Manual v1.50: Routing and Filtering</TITLE>
|
||||
<LINK HREF="adminmanual_en-2.html" REL=next>
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider Administration Manual v1.50: CVS</TITLE>
|
||||
<LINK HREF="adminmanual_en-11.html" REL=next>
|
||||
<LINK HREF="adminmanual_en-9.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider Administration Manual v1.50: The DXSpider Command Reference</TITLE>
|
||||
<LINK HREF="adminmanual_en-10.html" REL=previous>
|
||||
<LINK HREF="adminmanual_en.html#toc11" REL=contents>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider Administration Manual v1.50: Other filters</TITLE>
|
||||
<LINK HREF="adminmanual_en-3.html" REL=next>
|
||||
<LINK HREF="adminmanual_en-1.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider Administration Manual v1.50: Mail</TITLE>
|
||||
<LINK HREF="adminmanual_en-4.html" REL=next>
|
||||
<LINK HREF="adminmanual_en-2.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider Administration Manual v1.50: Scripts</TITLE>
|
||||
<LINK HREF="adminmanual_en-5.html" REL=next>
|
||||
<LINK HREF="adminmanual_en-3.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider Administration Manual v1.50: Databases</TITLE>
|
||||
<LINK HREF="adminmanual_en-6.html" REL=next>
|
||||
<LINK HREF="adminmanual_en-4.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider Administration Manual v1.50: Information, files and useful programs</TITLE>
|
||||
<LINK HREF="adminmanual_en-7.html" REL=next>
|
||||
<LINK HREF="adminmanual_en-5.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider Administration Manual v1.50: Java Web applet</TITLE>
|
||||
<LINK HREF="adminmanual_en-8.html" REL=next>
|
||||
<LINK HREF="adminmanual_en-6.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider Administration Manual v1.50: Web based statistics</TITLE>
|
||||
<LINK HREF="adminmanual_en-9.html" REL=next>
|
||||
<LINK HREF="adminmanual_en-7.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider Administration Manual v1.50: Security</TITLE>
|
||||
<LINK HREF="adminmanual_en-10.html" REL=next>
|
||||
<LINK HREF="adminmanual_en-8.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider Administration Manual v1.50</TITLE>
|
||||
<LINK HREF="adminmanual_en-1.html" REL=next>
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider User Filtering Primer v1.0: Introduction.</TITLE>
|
||||
<LINK HREF="filtering_en-2.html" REL=next>
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider User Filtering Primer v1.0: Contacts</TITLE>
|
||||
<LINK HREF="filtering_en-9.html" REL=previous>
|
||||
<LINK HREF="filtering_en.html#toc10" REL=contents>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider User Filtering Primer v1.0: Foreword</TITLE>
|
||||
<LINK HREF="filtering_en-3.html" REL=next>
|
||||
<LINK HREF="filtering_en-1.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider User Filtering Primer v1.0: Configuring Spot Filters</TITLE>
|
||||
<LINK HREF="filtering_en-4.html" REL=next>
|
||||
<LINK HREF="filtering_en-2.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider User Filtering Primer v1.0: Types of spot filters used in DXSpider </TITLE>
|
||||
<LINK HREF="filtering_en-5.html" REL=next>
|
||||
<LINK HREF="filtering_en-3.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider User Filtering Primer v1.0: Reject filters </TITLE>
|
||||
<LINK HREF="filtering_en-6.html" REL=next>
|
||||
<LINK HREF="filtering_en-4.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider User Filtering Primer v1.0: Filters to reject spots based on frequency</TITLE>
|
||||
<LINK HREF="filtering_en-7.html" REL=next>
|
||||
<LINK HREF="filtering_en-5.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider User Filtering Primer v1.0: Accept filters </TITLE>
|
||||
<LINK HREF="filtering_en-8.html" REL=next>
|
||||
<LINK HREF="filtering_en-6.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider User Filtering Primer v1.0: Clear filters </TITLE>
|
||||
<LINK HREF="filtering_en-9.html" REL=next>
|
||||
<LINK HREF="filtering_en-7.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider User Filtering Primer v1.0: Some Practice Examples </TITLE>
|
||||
<LINK HREF="filtering_en-10.html" REL=next>
|
||||
<LINK HREF="filtering_en-8.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider User Filtering Primer v1.0</TITLE>
|
||||
<LINK HREF="filtering_en-1.html" REL=next>
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider Installation Manual v1.50: Linux Installation </TITLE>
|
||||
<LINK HREF="installation_en-2.html" REL=next>
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider Installation Manual v1.50: Linux quick installation guide</TITLE>
|
||||
<LINK HREF="installation_en-3.html" REL=next>
|
||||
<LINK HREF="installation_en-1.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider Installation Manual v1.50: Setting up the AX25 Utilities</TITLE>
|
||||
<LINK HREF="installation_en-4.html" REL=next>
|
||||
<LINK HREF="installation_en-2.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider Installation Manual v1.50: Configuration</TITLE>
|
||||
<LINK HREF="installation_en-5.html" REL=next>
|
||||
<LINK HREF="installation_en-3.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider Installation Manual v1.50: Microsoft Windows Installation</TITLE>
|
||||
<LINK HREF="installation_en-6.html" REL=next>
|
||||
<LINK HREF="installation_en-4.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider Installation Manual v1.50: Installing the software</TITLE>
|
||||
<LINK HREF="installation_en-7.html" REL=next>
|
||||
<LINK HREF="installation_en-5.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider Installation Manual v1.50: General Information</TITLE>
|
||||
<LINK HREF="installation_en-6.html" REL=previous>
|
||||
<LINK HREF="installation_en.html#toc7" REL=contents>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider Installation Manual v1.50</TITLE>
|
||||
<LINK HREF="installation_en-1.html" REL=next>
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider CVS Changes Addendum v1.50</TITLE>
|
||||
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider FAQ: Installation </TITLE>
|
||||
<LINK HREF="spiderFAQ_en-2.html" REL=next>
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider FAQ: Administration</TITLE>
|
||||
<LINK HREF="spiderFAQ_en-1.html" REL=previous>
|
||||
<LINK HREF="spiderFAQ_en.html#toc2" REL=contents>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider FAQ</TITLE>
|
||||
<LINK HREF="spiderFAQ_en-1.html" REL=next>
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider User Manual v1.50: Introduction</TITLE>
|
||||
<LINK HREF="usermanual_en-2.html" REL=next>
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider User Manual v1.50: Filtering (From version 1.45)</TITLE>
|
||||
<LINK HREF="usermanual_en-11.html" REL=next>
|
||||
<LINK HREF="usermanual_en-9.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider User Manual v1.50: Hints, tips and common questions.</TITLE>
|
||||
<LINK HREF="usermanual_en-12.html" REL=next>
|
||||
<LINK HREF="usermanual_en-10.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider User Manual v1.50: The DXSpider Command Reference</TITLE>
|
||||
<LINK HREF="usermanual_en-11.html" REL=previous>
|
||||
<LINK HREF="usermanual_en.html#toc12" REL=contents>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider User Manual v1.50: Logins and logouts.</TITLE>
|
||||
<LINK HREF="usermanual_en-3.html" REL=next>
|
||||
<LINK HREF="usermanual_en-1.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider User Manual v1.50: Setting your personal details.</TITLE>
|
||||
<LINK HREF="usermanual_en-4.html" REL=next>
|
||||
<LINK HREF="usermanual_en-2.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider User Manual v1.50: Getting and posting DX.</TITLE>
|
||||
<LINK HREF="usermanual_en-5.html" REL=next>
|
||||
<LINK HREF="usermanual_en-3.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider User Manual v1.50: Headings and propagation</TITLE>
|
||||
<LINK HREF="usermanual_en-6.html" REL=next>
|
||||
<LINK HREF="usermanual_en-4.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider User Manual v1.50: Announcements.</TITLE>
|
||||
<LINK HREF="usermanual_en-7.html" REL=next>
|
||||
<LINK HREF="usermanual_en-5.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider User Manual v1.50: Nodes and users.</TITLE>
|
||||
<LINK HREF="usermanual_en-8.html" REL=next>
|
||||
<LINK HREF="usermanual_en-6.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider User Manual v1.50: Talk mode.</TITLE>
|
||||
<LINK HREF="usermanual_en-9.html" REL=next>
|
||||
<LINK HREF="usermanual_en-7.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider User Manual v1.50: Mail.</TITLE>
|
||||
<LINK HREF="usermanual_en-10.html" REL=next>
|
||||
<LINK HREF="usermanual_en-8.html" REL=previous>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
|
||||
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
|
||||
<TITLE>The DXSpider User Manual v1.50</TITLE>
|
||||
<LINK HREF="usermanual_en-1.html" REL=next>
|
||||
|
||||
|
||||
@ -1,34 +1,56 @@
|
||||
#!/usr/bin/perl
|
||||
#
|
||||
# convert an Ak1a DX.DAT file to comma delimited form
|
||||
# convert an AK1A DX.DAT file to comma delimited form
|
||||
#
|
||||
# PLEASE BE WARNED:
|
||||
#
|
||||
# This routine is really designed for archive data. It will create and add to
|
||||
# standard DXSpider spot files. If those spot files already exist (because you
|
||||
# were running DXSpider at the same time as collecting this 'old' data) then
|
||||
# this will simply append the data onto the end of the appropriate spot file
|
||||
# for that day. This may then give strange 'out of order' results when viewed
|
||||
# with the show/dx command
|
||||
#
|
||||
# $Id$
|
||||
#
|
||||
# Copyright (c) 1998-2003 Dirk Koopman G1TLH
|
||||
#
|
||||
|
||||
use Date::Parse;
|
||||
# search local then perl directories
|
||||
BEGIN {
|
||||
# root of directory tree for this system
|
||||
$root = "/spider";
|
||||
$root = $ENV{'DXSPIDER_ROOT'} if $ENV{'DXSPIDER_ROOT'};
|
||||
|
||||
unshift @INC, "$root/perl"; # this IS the right way round!
|
||||
unshift @INC, "$root/local";
|
||||
}
|
||||
|
||||
use DXUtil;
|
||||
use Spot;
|
||||
use Prefix;
|
||||
|
||||
sysopen(IN, "../data/DX.DAT", 0) or die "can't open DX.DAT ($!)";
|
||||
open(OUT, ">../data/dxcomma") or die "can't open dxcomma ($!)";
|
||||
$ifn = "$root/data/DX.DAT";
|
||||
$ifn = shift if @ARGV;
|
||||
print "Using: $ifn as input... \n";
|
||||
|
||||
Prefix::load();
|
||||
sysopen(IN, $ifn, 0) or die "can't open $ifn ($!)";
|
||||
|
||||
$fn = Spot::prefix();
|
||||
system("rm -rf $fn/*");
|
||||
Prefix::init();
|
||||
Spot::init();
|
||||
|
||||
while (sysread(IN, $buf, 86)) {
|
||||
($freq,$call,$date,$time,$comment,$spotter) = unpack 'A10A13A12A6A31A14', $buf;
|
||||
$d = $date =~ s/^\s*(\d+)-(\w\w\w)-(19\d\d)$/$1 $2 $3/o;
|
||||
$t = $time =~ s/^(\d\d)(\d\d)Z$/$1:$2 +0000/o;
|
||||
$dt = undef;
|
||||
$dt = str2time("$date $time") if $d && $t;
|
||||
# printf "%-13s %10.1f %s %s by %s %s\n", $call, $freq, $date, $time, $spotter, $comment;
|
||||
|
||||
$dt = cltounix($date, $time);
|
||||
$comment =~ s/^\s+//o;
|
||||
if ($dt ) {
|
||||
Spot::add($freq, $call, $dt, $comment, $spotter);
|
||||
my @spot = Spot::prepare($freq, $call, $dt, $comment, $spotter);
|
||||
Spot::add(@spot);
|
||||
} else {
|
||||
print "$call $freq $date $time\n";
|
||||
print "ERROR: $call $freq $date $time by $spotter $comment\n";
|
||||
}
|
||||
}
|
||||
|
||||
close(IN);
|
||||
close(OUT);
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -57,7 +57,7 @@
|
||||
|
||||
______________________________________________________________________
|
||||
|
||||
1. Introduction.
|
||||
[1m1. Introduction.[0m
|
||||
|
||||
The PacketCluster software written in the mid-80s by Dick Newell,
|
||||
AK1A, has served us well. Dick has moved on though and has not
|
||||
@ -125,7 +125,7 @@
|
||||
|
||||
|
||||
|
||||
2. Foreword
|
||||
[1m2. Foreword[0m
|
||||
|
||||
While attempting to learn how DXSpider filters work, I found that I
|
||||
had to glean bits and pieces of information from the DXSpider User
|
||||
@ -139,9 +139,9 @@
|
||||
|
||||
|
||||
|
||||
3. Configuring Spot Filters
|
||||
[1m3. Configuring Spot Filters[0m
|
||||
|
||||
3.1. What is a spot filter?
|
||||
[1m3.1. What is a spot filter?[0m
|
||||
|
||||
A spot filter is one rule (a one line spot filter) or multiple rules
|
||||
(multiple line spot filters) that a user can setup within DXSpider to
|
||||
@ -166,7 +166,7 @@
|
||||
|
||||
|
||||
|
||||
3.2. How can filters be used?
|
||||
[1m3.2. How can filters be used?[0m
|
||||
|
||||
For example, let's say our local user has never owned a microphone in
|
||||
his life and definitely doesn't want to see any of those useless SSB
|
||||
@ -180,7 +180,7 @@
|
||||
|
||||
|
||||
|
||||
4. Types of spot filters used in DXSpider
|
||||
[1m4. Types of spot filters used in DXSpider[0m
|
||||
|
||||
Basic filter types are "accept", "reject", and "clear" where the
|
||||
following applies ...
|
||||
@ -203,7 +203,7 @@
|
||||
of reject filters are usually easier to administer and change.
|
||||
|
||||
|
||||
4.1. Numbering lines and slots
|
||||
[1m4.1. Numbering lines and slots[0m
|
||||
|
||||
There are ten usable filter slots in DXSpider. Each slot holds one
|
||||
reject and one accept rule. Therefore, each type filter can have up to
|
||||
@ -217,7 +217,7 @@
|
||||
works.)
|
||||
|
||||
|
||||
Important: The filter rules are applied in sequence, i.e., 0-9. If a
|
||||
[4mImportant:[24m The filter rules are applied in sequence, i.e., 0-9. If a
|
||||
line matches, action is taken on that line. The filter sequence acts
|
||||
on rules in the order listed. It acts on the reject filter in each
|
||||
slot before acting on the accept filter contained in that slot. If the
|
||||
@ -240,7 +240,7 @@
|
||||
|
||||
|
||||
|
||||
4.2. Reject before accept
|
||||
[1m4.2. Reject before accept[0m
|
||||
|
||||
This is not a good rule for life, but it makes sense for DXSpider
|
||||
filters. As a general rule, reject filter rules within a slot are
|
||||
@ -249,7 +249,7 @@
|
||||
passed to the next filter line in the set. However, if a spot matches
|
||||
an accept filter, it is sent immediately to the user.
|
||||
|
||||
4.3. Using Multiple Reject Filter Rules
|
||||
[1m4.3. Using Multiple Reject Filter Rules[0m
|
||||
|
||||
Another important concept to know is that you can do everything you
|
||||
want to do with multiple reject filters AND NO ACCEPT FILTERS. By
|
||||
@ -321,7 +321,7 @@
|
||||
|
||||
|
||||
|
||||
4.4. A very useful command
|
||||
[1m4.4. A very useful command[0m
|
||||
|
||||
To see all active filters in use at any time, just type the following
|
||||
command ...
|
||||
@ -332,13 +332,13 @@
|
||||
|
||||
|
||||
|
||||
4.5. Case does not matter
|
||||
[1m4.5. Case does not matter[0m
|
||||
|
||||
In entering any filter - case does not matter. Upper, lower, or mixed
|
||||
case will not effect how filters work or perform.
|
||||
|
||||
|
||||
4.6. Qualifiers
|
||||
[1m4.6. Qualifiers[0m
|
||||
|
||||
Logical operands can be used in rule sets to combine multiple actions
|
||||
or qualify others. These are ...
|
||||
@ -355,7 +355,7 @@
|
||||
(). We will see how these can be used in examples later.
|
||||
|
||||
|
||||
4.7. Comma Separation
|
||||
[1m4.7. Comma Separation[0m
|
||||
|
||||
Any command can have multiple pattern variables if commas separate
|
||||
them. For example ...
|
||||
@ -366,7 +366,7 @@
|
||||
|
||||
|
||||
|
||||
5. Reject filters
|
||||
[1m5. Reject filters[0m
|
||||
|
||||
A reject filter line means that if a spot matches, send it to the
|
||||
trash, dump it, do not send it down the line to the next rule or to
|
||||
@ -398,7 +398,7 @@
|
||||
|
||||
|
||||
|
||||
6. Filters to reject spots based on frequency
|
||||
[1m6. Filters to reject spots based on frequency[0m
|
||||
|
||||
|
||||
|
||||
@ -410,8 +410,8 @@
|
||||
|
||||
|
||||
|
||||
Important: both freq and on are exactly the same and can be used
|
||||
interchangeably - most persons use on (less typing.)
|
||||
Important: both [4mfreq[24m and [4mon[24m are exactly the same and can be used
|
||||
interchangeably - most persons use [4mon[24m (less typing.)
|
||||
|
||||
|
||||
For range, you can specify a frequency like 7040, a range of
|
||||
@ -419,7 +419,7 @@
|
||||
or "region" names defined in the show/bands command.
|
||||
|
||||
|
||||
6.1. Bands Available
|
||||
[1m6.1. Bands Available[0m
|
||||
|
||||
|
||||
|
||||
@ -461,7 +461,7 @@
|
||||
|
||||
|
||||
|
||||
6.2. Regions Available
|
||||
[1m6.2. Regions Available[0m
|
||||
|
||||
|
||||
|
||||
@ -482,7 +482,7 @@
|
||||
|
||||
|
||||
|
||||
6.3. Examples
|
||||
[1m6.3. Examples[0m
|
||||
|
||||
The following line will reject spots on 7,040 kHz and pass all others.
|
||||
|
||||
@ -538,7 +538,7 @@
|
||||
|
||||
|
||||
|
||||
6.4. Sub-bands as part of range
|
||||
[1m6.4. Sub-bands as part of range[0m
|
||||
|
||||
In conjunction with range, you can use the following sub-band names,
|
||||
|
||||
@ -569,7 +569,7 @@
|
||||
|
||||
|
||||
|
||||
6.5. Filters to reject spots based on the "info" data in the spot
|
||||
[1m6.5. Filters to reject spots based on the "info" data in the spot[0m
|
||||
|
||||
|
||||
|
||||
@ -614,12 +614,12 @@
|
||||
|
||||
|
||||
|
||||
Note: The following series of filters are based on call and by. Call
|
||||
Note: The following series of filters are based on [4mcall[24m and [4mby[24m. Call
|
||||
always references the callsign of the spotted DX station. By always
|
||||
references the callsign of the spotting station.
|
||||
|
||||
|
||||
6.6. Filters to reject spots based on call
|
||||
[1m6.6. Filters to reject spots based on call[0m
|
||||
|
||||
|
||||
|
||||
@ -662,7 +662,7 @@
|
||||
|
||||
|
||||
|
||||
6.7. Filters to reject spots based on call_dxcc
|
||||
[1m6.7. Filters to reject spots based on call_dxcc[0m
|
||||
|
||||
|
||||
|
||||
@ -672,7 +672,7 @@
|
||||
|
||||
This filter is based on DXCC entities and uses either the country
|
||||
prefix or the DXCC entity number, found by using the command
|
||||
show/prefix.
|
||||
[4mshow/prefix[24m.
|
||||
|
||||
|
||||
As in ...
|
||||
@ -720,7 +720,7 @@
|
||||
|
||||
|
||||
|
||||
6.8. Filters to reject spots based on call_itu
|
||||
[1m6.8. Filters to reject spots based on call_itu[0m
|
||||
|
||||
Similarly, call_itu and call_zone use ITU regions that can also be
|
||||
obtained using the show/prefix <prefix> command (see above.)
|
||||
@ -743,7 +743,7 @@
|
||||
|
||||
|
||||
|
||||
6.9. Filters to reject spots based on call_zone
|
||||
[1m6.9. Filters to reject spots based on call_zone[0m
|
||||
|
||||
|
||||
|
||||
@ -752,7 +752,7 @@
|
||||
|
||||
|
||||
This filter is based on CQ zones and uses the CQ zone number found by
|
||||
using the command show/prefix (see above.)
|
||||
using the command [4mshow/prefix[24m (see above.)
|
||||
|
||||
|
||||
Example ...
|
||||
@ -767,7 +767,7 @@
|
||||
|
||||
|
||||
|
||||
6.10. Filters to reject spots based on call_state
|
||||
[1m6.10. Filters to reject spots based on call_state[0m
|
||||
|
||||
|
||||
|
||||
@ -775,7 +775,7 @@
|
||||
|
||||
|
||||
This filter is based on the state of the call spotted, for those
|
||||
callsigns contained in the usdb database. Use the command show/usdb
|
||||
callsigns contained in the usdb database. Use the command [4mshow/usdb[0m
|
||||
to see an example of a listing in the database, like this ...
|
||||
|
||||
|
||||
@ -797,9 +797,9 @@
|
||||
|
||||
|
||||
|
||||
6.11. Filters to reject spots based on by
|
||||
[1m6.11. Filters to reject spots based on by[0m
|
||||
|
||||
by filters are similar to and function exactly as call filters except
|
||||
[4mby[24m filters are similar to and function exactly as call filters except
|
||||
that they act on the spotting station callsign and not the spotted
|
||||
callsign.
|
||||
|
||||
@ -829,7 +829,7 @@
|
||||
|
||||
|
||||
This next filter is based on ITU regions and uses the ITU region
|
||||
number found by using the command show/prefix (see above), except that
|
||||
number found by using the command [4mshow/prefix[24m (see above), except that
|
||||
it rejects spots generated by a spotting callsign within the ITU
|
||||
region and passes all other spots.
|
||||
|
||||
@ -840,7 +840,7 @@
|
||||
|
||||
|
||||
This filter is based on CQ zones and uses the CQ zone number found by
|
||||
using the command show/prefix (see above), except that it rejects
|
||||
using the command [4mshow/prefix[24m (see above), except that it rejects
|
||||
spots generated by a spotting callsign within the CQ zone and passes
|
||||
all other spots.
|
||||
|
||||
@ -851,7 +851,7 @@
|
||||
|
||||
|
||||
This filter is based on the state of the spotting station found by
|
||||
using the command show/usdb and passes all other spots.
|
||||
using the command [4mshow/usdb[24m and passes all other spots.
|
||||
|
||||
|
||||
|
||||
@ -859,7 +859,7 @@
|
||||
|
||||
|
||||
|
||||
7. Accept filters
|
||||
[1m7. Accept filters[0m
|
||||
|
||||
An accept filter line means that if a spot matches pass it on to the
|
||||
user, send it down the line to the next rule or to the user, and
|
||||
@ -905,7 +905,7 @@
|
||||
|
||||
|
||||
|
||||
7.1. Filters to accept spots based on frequency
|
||||
[1m7.1. Filters to accept spots based on frequency[0m
|
||||
|
||||
|
||||
|
||||
@ -917,7 +917,7 @@
|
||||
|
||||
|
||||
|
||||
Important: as noted before, both freq and on are exactly the same and
|
||||
Important: as noted before, both [4mfreq[24m and [4mon[24m are exactly the same and
|
||||
can be used interchangeably.
|
||||
|
||||
|
||||
@ -965,7 +965,7 @@
|
||||
|
||||
|
||||
|
||||
7.2. Sub-bands as part of range
|
||||
[1m7.2. Sub-bands as part of range[0m
|
||||
|
||||
In conjunction with range, you can use the following sub-band names:
|
||||
CW, RTTY, DATA, SSB, and SSTV by using a back-slash [(band or
|
||||
@ -994,7 +994,7 @@
|
||||
|
||||
|
||||
|
||||
7.3. Filters to accept spots based on info
|
||||
[1m7.3. Filters to accept spots based on info[0m
|
||||
|
||||
|
||||
|
||||
@ -1037,12 +1037,12 @@
|
||||
|
||||
|
||||
|
||||
Note: The following series of filters are based on call and by. Call
|
||||
Note: The following series of filters are based on [4mcall[24m and [4mby[24m. Call
|
||||
always references the callsign of the spotted DX station. By always
|
||||
references the callsign of the spotting station.
|
||||
|
||||
|
||||
7.4. Filters to accept spots based on call
|
||||
[1m7.4. Filters to accept spots based on call[0m
|
||||
|
||||
|
||||
|
||||
@ -1085,7 +1085,7 @@
|
||||
|
||||
|
||||
|
||||
7.5. Filters to accept spots based on call_dxcc
|
||||
[1m7.5. Filters to accept spots based on call_dxcc[0m
|
||||
|
||||
|
||||
|
||||
@ -1095,7 +1095,7 @@
|
||||
|
||||
This filter is based on DXCC entities and uses either the country
|
||||
prefixes or the DXCC entity number found by using the command
|
||||
show/prefix. See example of show/prefix above.
|
||||
[4mshow/prefix[24m. See example of [4mshow/prefix[24m above.
|
||||
|
||||
|
||||
Examples ...
|
||||
@ -1124,10 +1124,10 @@
|
||||
|
||||
|
||||
|
||||
7.6. Filters to accept spots based on call_itu
|
||||
[1m7.6. Filters to accept spots based on call_itu[0m
|
||||
|
||||
Similarly, call_itu and call_zone use ITU regions that can also be
|
||||
obtained using the show/prefix command (see above.)
|
||||
obtained using the [4mshow/prefix[24m command (see above.)
|
||||
|
||||
|
||||
|
||||
@ -1147,7 +1147,7 @@
|
||||
|
||||
|
||||
|
||||
7.7. Filters to accept spots based on call_zone
|
||||
[1m7.7. Filters to accept spots based on call_zone[0m
|
||||
|
||||
|
||||
|
||||
@ -1156,7 +1156,7 @@
|
||||
|
||||
|
||||
This filter is based on CQ zones and uses the CQ zone number found by
|
||||
using the command show/prefix (see above.)
|
||||
using the command [4mshow/prefix[24m (see above.)
|
||||
|
||||
|
||||
Example ...
|
||||
@ -1171,7 +1171,7 @@
|
||||
|
||||
|
||||
|
||||
7.8. Filters to accept spots based on call_state
|
||||
[1m7.8. Filters to accept spots based on call_state[0m
|
||||
|
||||
|
||||
|
||||
@ -1195,9 +1195,9 @@
|
||||
accept/spot 0 call_state pa
|
||||
|
||||
|
||||
7.9. Filters to accept spots based on by
|
||||
[1m7.9. Filters to accept spots based on by[0m
|
||||
|
||||
by filters are similar to and function exactly as call filters except
|
||||
[4mby[24m filters are similar to and function exactly as call filters except
|
||||
that they act on the spotting station callsign and not the spotted
|
||||
callsign
|
||||
|
||||
@ -1216,7 +1216,7 @@
|
||||
|
||||
|
||||
This filter is based on DXCC entities and uses the DXCC entity number
|
||||
found by using the command show/prefix and it accepts spots generated
|
||||
found by using the command [4mshow/prefix[24m and it accepts spots generated
|
||||
within the spotting DXCC entity and rejects other spots.
|
||||
|
||||
|
||||
@ -1226,7 +1226,7 @@
|
||||
|
||||
|
||||
This next filter is based on ITU regions and uses the ITU region
|
||||
number found by using the command show/prefix (see above), except that
|
||||
number found by using the command [4mshow/prefix[24m (see above), except that
|
||||
it accepts spots generated by a spotting callsign within the ITU
|
||||
region and rejects all other spots.
|
||||
|
||||
@ -1237,7 +1237,7 @@
|
||||
|
||||
|
||||
This filter is based on CQ zones and uses the CQ zone number found by
|
||||
using the command show/prefix (see above), except that it accepts
|
||||
using the command [4mshow/prefix[24m (see above), except that it accepts
|
||||
spots generated by a spotting callsign within the CQ zone and rejects
|
||||
all other spots.
|
||||
|
||||
@ -1248,7 +1248,7 @@
|
||||
|
||||
|
||||
This filters is based on the state location of the spotting station
|
||||
found by using the command show/usdb and accepts only those spots
|
||||
found by using the command [4mshow/usdb[24m and accepts only those spots
|
||||
generated by stations from the states(s) specified rejecting all other
|
||||
spots.
|
||||
|
||||
@ -1257,7 +1257,7 @@
|
||||
Syntax: accept/spot [0-9] by_state <state2-letter postal codes>
|
||||
|
||||
|
||||
8. Clear filters
|
||||
[1m8. Clear filters[0m
|
||||
|
||||
A clear filter line will delete the slot number specified or all slots
|
||||
and consequently all filters that have been created by a user.
|
||||
@ -1298,7 +1298,7 @@
|
||||
slot 1 by default.
|
||||
|
||||
|
||||
9. Some Practice Examples
|
||||
[1m9. Some Practice Examples[0m
|
||||
|
||||
The proceeding sections have discussed the basics of DXSpider filters.
|
||||
The following are some examples utilizing basic filters and some not
|
||||
@ -1414,7 +1414,7 @@
|
||||
were not used, slot 1 is assumed.
|
||||
|
||||
|
||||
10. Contacts
|
||||
[1m10. Contacts[0m
|
||||
|
||||
This Primer is a work in progress. Additional features and filters are
|
||||
added from time to time by Dirk Koopman, G1TLH, the developer behind
|
||||
|
||||
@ -64,9 +64,9 @@
|
||||
|
||||
|
||||
|
||||
1. Linux Installation
|
||||
[1m1. Linux Installation[0m
|
||||
|
||||
1.1. Introduction
|
||||
[1m1.1. Introduction[0m
|
||||
|
||||
This section describes the installation of DX Spider v1.50 on a RedHat
|
||||
Linux Distribution. Wherever possible I will try to include
|
||||
@ -74,12 +74,12 @@
|
||||
|
||||
|
||||
I am assuming a general knowledge of Linux and its commands. You
|
||||
should know how to use tar and how to edit files using your favourite
|
||||
should know how to use [4mtar[24m and how to edit files using your favourite
|
||||
editor.
|
||||
|
||||
|
||||
The crucial ingredient for all of this is Perl. Earlier versions of
|
||||
Spider required perl 5.004, however it is now STRONGLY recommended
|
||||
Spider required perl 5.004, however it is now [4mSTRONGLY[24m recommended
|
||||
that you use at least version 5.005_03 as this is the version being
|
||||
used in the development of Spider.
|
||||
|
||||
@ -172,11 +172,11 @@
|
||||
|
||||
Do not fall into the trap of thinking they're all the same, just
|
||||
because they nearly are! Pay particular attention to the instructions
|
||||
of IO, above.
|
||||
of [4mIO[24m, above.
|
||||
|
||||
|
||||
|
||||
1.2. Preparation
|
||||
[1m1.2. Preparation[0m
|
||||
|
||||
I will assume that you have already downloaded the latest tarball of
|
||||
the DXSpider software and are ready to install it. I am assuming
|
||||
@ -184,9 +184,9 @@
|
||||
version.
|
||||
|
||||
|
||||
Login as root and create a user to run the cluster under. UNDER NO
|
||||
CIRCUMSTANCES USE ROOT AS THIS USER!. I am going to use the name
|
||||
sysop. You can call it anything you wish. Depending on your security
|
||||
Login as root and create a user to run the cluster under. [4mUNDER[24m [4mNO[0m
|
||||
[4mCIRCUMSTANCES[24m [4mUSE[24m [4mROOT[24m [4mAS[24m [4mTHIS[24m [4mUSER![24m. I am going to use the name
|
||||
[4msysop[24m. You can call it anything you wish. Depending on your security
|
||||
requirements you may wish to use an existing user, however this is
|
||||
your own choice.
|
||||
|
||||
@ -215,7 +215,7 @@
|
||||
|
||||
|
||||
|
||||
1.3. Installing the software
|
||||
[1m1.3. Installing the software[0m
|
||||
|
||||
Now to unpack the DX Spider distribution, set symbolic links and group
|
||||
permissions. Copy the tarball to /home/sysop and do the following.
|
||||
@ -229,7 +229,7 @@
|
||||
|
||||
|
||||
|
||||
If you do not have the command groupadd available to you simply add a
|
||||
If you do not have the command [4mgroupadd[24m available to you simply add a
|
||||
line in /etc/group by hand.
|
||||
|
||||
|
||||
@ -256,14 +256,14 @@
|
||||
|
||||
|
||||
|
||||
This last step allows various users of the group spider to have write
|
||||
This last step allows various users of the group [4mspider[24m to have write
|
||||
access to all the directories. This is not really needed just yet but
|
||||
will be useful when web interfaces start to appear.
|
||||
|
||||
|
||||
Finally, you need to fix the permissions on the ax25_call and
|
||||
netrom_call programs. Check where they are with the locate command
|
||||
and alter the permissions with the chmod command like this ..
|
||||
netrom_call programs. Check where they are with the [4mlocate[24m command
|
||||
and alter the permissions with the [4mchmod[24m command like this ..
|
||||
|
||||
|
||||
|
||||
@ -272,10 +272,10 @@
|
||||
|
||||
|
||||
|
||||
1.4. Setting callsigns etc
|
||||
[1m1.4. Setting callsigns etc[0m
|
||||
|
||||
Now login to your machine as the user you created earlier. In my case
|
||||
that user is called sysop. Once logged in, issue the following
|
||||
that user is called [4msysop[24m. Once logged in, issue the following
|
||||
commands ....
|
||||
|
||||
|
||||
@ -311,7 +311,7 @@
|
||||
This is the sysop user callsign, normally your own.
|
||||
|
||||
|
||||
PLEASE USE CAPITAL LETTERS FOR CALLSIGNS
|
||||
[1mPLEASE USE CAPITAL LETTERS FOR CALLSIGNS[0m
|
||||
|
||||
|
||||
Note that this a perl file which will be parsed and executed as part
|
||||
@ -350,16 +350,16 @@
|
||||
|
||||
|
||||
|
||||
1.5. The client program
|
||||
[1m1.5. The client program[0m
|
||||
|
||||
In earlier versions of Spider, all the processes were Perl scripts.
|
||||
This was fine but with a lot of users your computer memory would soon
|
||||
be used up. To combat this a new client was written in "C". This
|
||||
client only works for incoming connects at the moment. Before you can
|
||||
use it though it has to be "made". CD to /spider/src and type make.
|
||||
client only works for [4mincoming[24m connects at the moment. Before you can
|
||||
use it though it has to be "made". CD to /spider/src and type [4mmake[24m.
|
||||
You should see the output on your screen and hopefully now have a
|
||||
small C program called client. Leave it in this directory.
|
||||
1.6. Starting up for the first time
|
||||
small C program called [4mclient[24m. Leave it in this directory.
|
||||
[1m1.6. Starting up for the first time[0m
|
||||
|
||||
We can now bring spider up for the first time and see if all is well
|
||||
or not! It should look something like this ...
|
||||
@ -379,7 +379,7 @@
|
||||
|
||||
|
||||
|
||||
If all is well then login on another term or console as sysop and cd
|
||||
If all is well then login on another term or console as [4msysop[24m and cd
|
||||
to /spider/src. Now issue the following command ...
|
||||
|
||||
|
||||
@ -414,7 +414,7 @@
|
||||
|
||||
|
||||
|
||||
2. Linux quick installation guide
|
||||
[1m2. Linux quick installation guide[0m
|
||||
|
||||
This section is designed for experienced Spider sysops who want to
|
||||
install Spider from scratch. It is simply a check list of things that
|
||||
@ -497,7 +497,7 @@
|
||||
o Enter the correct line in /etc/inittab (root)
|
||||
|
||||
|
||||
3. Setting up the AX25 Utilities
|
||||
[1m3. Setting up the AX25 Utilities[0m
|
||||
|
||||
The aim of this section is not to fully cover the installation and
|
||||
configuration of all the possible ax25 modules. I will attempt to
|
||||
@ -523,7 +523,7 @@
|
||||
necessarily the best or for that matter, the right way!
|
||||
|
||||
|
||||
3.1. Getting Started
|
||||
[1m3.1. Getting Started[0m
|
||||
|
||||
There are 2 things you need to do initially. You need to get the 3
|
||||
files required for the ax25 installation and you need to make some
|
||||
@ -552,7 +552,7 @@
|
||||
o ax25-apps-0.0.4-9.i386.rpm
|
||||
|
||||
|
||||
3.2. The kernel
|
||||
[1m3.2. The kernel[0m
|
||||
|
||||
First you need to add Amateur Radio Support to your kernel. This is a
|
||||
main menu item and should be easily found. Within this header you
|
||||
@ -571,7 +571,7 @@
|
||||
Now recompile your kernel in the normal way and reboot your system.
|
||||
|
||||
|
||||
3.3. Installing the RPM's
|
||||
[1m3.3. Installing the RPM's[0m
|
||||
|
||||
Now install the RPM's you downloaded, libax25 first, then ax25-tools,
|
||||
then ax25-apps.
|
||||
@ -584,7 +584,7 @@
|
||||
|
||||
|
||||
|
||||
3.4. Configuration
|
||||
[1m3.4. Configuration[0m
|
||||
|
||||
You will find the configuration files in /etc/ax25. These consist of
|
||||
several files ...
|
||||
@ -609,7 +609,7 @@
|
||||
NOTE:- before we start it is important to realise that every interface
|
||||
requires a different SSID. You should be able to follow this in the
|
||||
following examples.
|
||||
3.5. axports
|
||||
[1m3.5. axports[0m
|
||||
|
||||
This file sets up the ax25 ports you want to use. An example is below
|
||||
for a standard TNC2 ...
|
||||
@ -637,7 +637,7 @@
|
||||
|
||||
|
||||
|
||||
3.6. nrports
|
||||
[1m3.6. nrports[0m
|
||||
|
||||
This file sets up the netrom ports you want to use. An example is
|
||||
below and includes a port for both cluster and node. You will see why
|
||||
@ -666,7 +666,7 @@
|
||||
|
||||
|
||||
|
||||
3.7. nrbroadcast
|
||||
[1m3.7. nrbroadcast[0m
|
||||
|
||||
This file sets up the netrom broadcast qualities. An example is below
|
||||
...
|
||||
@ -692,7 +692,7 @@
|
||||
|
||||
|
||||
|
||||
3.8. ax25d.conf
|
||||
[1m3.8. ax25d.conf[0m
|
||||
|
||||
This file controls any incoming ax25 and NET/ROM connections and
|
||||
steers them to the relevant program. There are lots of configuration
|
||||
@ -773,7 +773,7 @@
|
||||
|
||||
|
||||
|
||||
3.9. node.conf
|
||||
[1m3.9. node.conf[0m
|
||||
|
||||
For those of you that wish to run the node, you need to set up the
|
||||
node.conf file. There are a couple of additional files, node.perms is
|
||||
@ -868,7 +868,7 @@
|
||||
This should be fairly obvious I hope.
|
||||
|
||||
|
||||
3.10. Getting it all running
|
||||
[1m3.10. Getting it all running[0m
|
||||
|
||||
Ok, now we have all the relevant files configured, the next step is to
|
||||
get it all running.
|
||||
@ -1000,14 +1000,14 @@
|
||||
stations and receive incoming ax25 and netrom connections.
|
||||
|
||||
|
||||
4. Configuration
|
||||
[1m4. Configuration[0m
|
||||
|
||||
4.1. Allowing ax25 connects from users
|
||||
[1m4.1. Allowing ax25 connects from users[0m
|
||||
|
||||
This is dealt with in the previous section
|
||||
|
||||
|
||||
4.2. Allowing telnet connects from users
|
||||
[1m4.2. Allowing telnet connects from users[0m
|
||||
|
||||
|
||||
>From version 1.47 there is a new (more efficient) way of doing this
|
||||
@ -1039,7 +1039,7 @@
|
||||
|
||||
|
||||
|
||||
Now login as sysop and cd spider/src. You can test that spider is
|
||||
Now login as [4msysop[24m and cd spider/src. You can test that spider is
|
||||
accepting telnet logins by issuing the following command ....
|
||||
|
||||
|
||||
@ -1065,7 +1065,7 @@
|
||||
You should now get the login prompt and be able to login as before.
|
||||
|
||||
|
||||
4.3. Setting up telnet connects (from 1.47 onwards)
|
||||
[1m4.3. Setting up telnet connects (from 1.47 onwards)[0m
|
||||
|
||||
>From version 1.47 you can choose to allow the perl cluster.pl program
|
||||
to allow connections directly (i.e. not via the /spider/src/client
|
||||
@ -1085,8 +1085,8 @@
|
||||
to make the change happen...
|
||||
|
||||
|
||||
Having done that, you need to copy the file /spider/perl/Listeners.pm
|
||||
to /spider/local and then edit it. You will need to uncomment the line
|
||||
Having done that, you need to copy the file [4m/spider/perl/Listeners.pm[0m
|
||||
to [4m/spider/local[24m and then edit it. You will need to uncomment the line
|
||||
containing "0.0.0.0" and select the correct port to listen on. So that
|
||||
it looks like this:-
|
||||
|
||||
@ -1126,14 +1126,14 @@
|
||||
users.
|
||||
|
||||
|
||||
4.4. Setting up for AGW Engine (1.47 onwards)
|
||||
[1m4.4. Setting up for AGW Engine (1.47 onwards)[0m
|
||||
|
||||
AGW Engine is a Windows based ax25 stack. You can connect to an AGW
|
||||
engine from Linux as well as Windows based machines.
|
||||
|
||||
|
||||
In order to enable access to an AGW Engine you need to copy
|
||||
/spider/perl/AGWConnect.pm to /spider/local and edit it. Specifically
|
||||
[4m/spider/perl/AGWConnect.pm[24m to [4m/spider/local[24m and edit it. Specifically
|
||||
you must:-
|
||||
|
||||
|
||||
@ -1151,7 +1151,7 @@
|
||||
|
||||
|
||||
|
||||
4.5. Setting up node connects
|
||||
[1m4.5. Setting up node connects[0m
|
||||
|
||||
In order to allow cluster node connections, spider needs to know that
|
||||
the connecting callsign is a cluster node. This is the case whether
|
||||
@ -1228,7 +1228,7 @@
|
||||
|
||||
|
||||
|
||||
4.6. Connection scripts
|
||||
[1m4.6. Connection scripts[0m
|
||||
|
||||
Because DXSpider operates under Linux, connections can be made using
|
||||
just about any protocol; AX25, NETRom, tcp/ip, ROSE etc are all
|
||||
@ -1242,23 +1242,23 @@
|
||||
|
||||
|
||||
|
||||
# All lines starting with a # are ignored, as are completely blank
|
||||
[1m# [22mAll lines starting with a # are ignored, as are completely blank
|
||||
lines.
|
||||
|
||||
|
||||
timeout
|
||||
[1mtimeout[0m
|
||||
timeout followed by a number is the number of seconds to wait
|
||||
for a command to complete. If there is no timeout specified in
|
||||
the script then the default is 60 seconds.
|
||||
|
||||
|
||||
abort
|
||||
[1mabort[0m
|
||||
abort is a regular expression containing one or more strings to
|
||||
look for to abort a connection. This is a perl regular
|
||||
expression and is executed ignoring case.
|
||||
|
||||
|
||||
connect
|
||||
[1mconnect[0m
|
||||
connect followed by ax25, agw (for Windows users) or telnet and
|
||||
some type dependent information. In the case of a telnet
|
||||
connection, there can be up to two parameters. The first is the
|
||||
@ -1271,18 +1271,19 @@
|
||||
down this route!
|
||||
|
||||
|
||||
' line in a chat type script. The words/phrases normally come in
|
||||
pairs, either can be empty. Each line reads input from the
|
||||
connection until it sees the string (or perl regular expression)
|
||||
contained in the left hand string. If the left hand string is
|
||||
empty then it doesn't read or wait for anything. The comparison
|
||||
is done ignoring case. When the left hand string has found what
|
||||
it is looking for (if it is) then the right hand string is sent
|
||||
to the connection. This process is repeated for every line of
|
||||
chat script.
|
||||
[1m' [22m' is the delimiting character for a word or phrase of an
|
||||
expect/send line in a chat type script. The words/phrases
|
||||
normally come in pairs, either can be empty. Each line reads
|
||||
input from the connection until it sees the string (or perl
|
||||
regular expression) contained in the left hand string. If the
|
||||
left hand string is empty then it doesn't read or wait for
|
||||
anything. The comparison is done ignoring case. When the left
|
||||
hand string has found what it is looking for (if it is) then the
|
||||
right hand string is sent to the connection. This process is
|
||||
repeated for every line of chat script.
|
||||
|
||||
|
||||
client
|
||||
[1mclient[0m
|
||||
client starts the connection, put the arguments you would want
|
||||
here if you were starting the client program manually. You only
|
||||
need this if the script has a different name to the callsign you
|
||||
@ -1322,16 +1323,15 @@
|
||||
# you can leave this out if you call this script 'gb7djk'
|
||||
client gb7djk telnet
|
||||
|
||||
|
||||
Both these examples assume that everything is set up properly at the
|
||||
other end. You will find other examples in the /spider/examples
|
||||
directory.
|
||||
|
||||
|
||||
4.7. Starting the connection
|
||||
[1m4.7. Starting the connection[0m
|
||||
|
||||
You start the connection, from within a sysop enabled cluster login,
|
||||
by typing in the word connect followed by a script name like this ....
|
||||
by typing in the word [4mconnect[24m followed by a script name like this ....
|
||||
|
||||
|
||||
|
||||
@ -1341,9 +1341,9 @@
|
||||
|
||||
|
||||
|
||||
This will start a connection using the script called gb7djk-1. You
|
||||
This will start a connection using the script called [4mgb7djk-1[24m. You
|
||||
can follow the connection by watching the term or console from where
|
||||
you started cluster.pl. From version 1.47 onwards, you will need to
|
||||
you started [4mcluster.pl[24m. From version 1.47 onwards, you will need to
|
||||
set/debug connect first. You should see something like this ...
|
||||
|
||||
|
||||
@ -1381,7 +1381,7 @@
|
||||
This tells them when a user or node logs in or out. If you do not add
|
||||
a line to your scripts after the final line (or before the client line
|
||||
which should always be last if needed) then the login/logout
|
||||
information will be sent to users before the login actually completes.
|
||||
information will be sent to users [4mbefore[24m the login actually completes.
|
||||
This means if a node is unreachable, it will continue sending logins
|
||||
and logouts to users even though it is not actually connecting. To
|
||||
avoid this use the following line ...
|
||||
@ -1395,7 +1395,7 @@
|
||||
|
||||
|
||||
|
||||
4.8. Telnet echo
|
||||
[1m4.8. Telnet echo[0m
|
||||
|
||||
Cluster links in particular suffer greatly from the presence of telnet
|
||||
echo. This is caused by the telnet negotiation itself and can create
|
||||
@ -1438,7 +1438,7 @@
|
||||
|
||||
|
||||
|
||||
4.9. Autostarting the cluster
|
||||
[1m4.9. Autostarting the cluster[0m
|
||||
|
||||
Ok, you should now have DXSpider running nicely and allowing connects
|
||||
by cluster nodes or users. However, it has to be shutdown and
|
||||
@ -1491,16 +1491,16 @@
|
||||
tty you run it on.
|
||||
|
||||
|
||||
As root type the command telinit q. DXSpider should start up
|
||||
As root type the command [4mtelinit[24m [4mq[24m. DXSpider should start up
|
||||
immediately. You will see the output on tty7 and if you login as
|
||||
sysop you should find everything running nicely.
|
||||
[4msysop[24m you should find everything running nicely.
|
||||
|
||||
|
||||
5. Microsoft Windows Installation
|
||||
[1m5. Microsoft Windows Installation[0m
|
||||
|
||||
5.1. Introduction
|
||||
[1m5.1. Introduction[0m
|
||||
|
||||
IMPORTANT:
|
||||
[1mIMPORTANT:[0m
|
||||
|
||||
What you'll be left with once you've followed these instructions is
|
||||
(hopefully) a working DX Spider v1.50 system that is capable of
|
||||
@ -1521,7 +1521,7 @@
|
||||
connections.
|
||||
|
||||
|
||||
5.2. The requirements
|
||||
[1m5.2. The requirements[0m
|
||||
|
||||
The very first things you're going to need are (in order of
|
||||
importance):-
|
||||
@ -1540,7 +1540,7 @@
|
||||
o Plenty of good, strong tea
|
||||
|
||||
|
||||
5.3. The system
|
||||
[1m5.3. The system[0m
|
||||
|
||||
The platform I used to generate these instructions was a "vanilla"
|
||||
Microsoft Windows Me 4.90.3000 system, with a 700MHz AMD Athlon
|
||||
@ -1563,7 +1563,7 @@
|
||||
zero intention of trying to make them say otherwise.
|
||||
|
||||
|
||||
5.4. Perl
|
||||
[1m5.4. Perl[0m
|
||||
|
||||
Install your chosen Perl environment. Unless you have a very good
|
||||
reason for not doing so, I strongly suggest that you use ActivePerl
|
||||
@ -1601,7 +1601,7 @@
|
||||
passed. Assuming it did work, you may now move on.
|
||||
|
||||
|
||||
5.5. Additional packages
|
||||
[1m5.5. Additional packages[0m
|
||||
|
||||
Some extensions ("packages") need to be added to the base Perl
|
||||
distribution, and we'll do this next. If you're using the Perl I
|
||||
@ -1670,7 +1670,7 @@
|
||||
because it suits me.
|
||||
|
||||
|
||||
5.6. Getting Spider
|
||||
[1m5.6. Getting Spider[0m
|
||||
|
||||
Get the current version of the DX Spider distribution. This needs to
|
||||
be v1.50 or later. You've got two ways (currently) of getting this;
|
||||
@ -1691,9 +1691,9 @@
|
||||
|
||||
|
||||
The only difference between "CVSlatest.tgz" and the latest "official"
|
||||
release version is that it is more up to date. Do not confuse the
|
||||
"CVSlatest.tgz" file with "Downloading from Sourceforge with CVS" -
|
||||
they are two quite different things. "Downloading from Sourceforge
|
||||
release version is that it is more up to date. [1mDo not confuse the[0m
|
||||
[1m"CVSlatest.tgz" file with "Downloading from Sourceforge with CVS" -[0m
|
||||
[1mthey are two quite different things. [22m"Downloading from Sourceforge
|
||||
with CVS" is explained in a section within the Admin manual.
|
||||
|
||||
|
||||
@ -1713,7 +1713,7 @@
|
||||
"C:\", for convenience.
|
||||
|
||||
|
||||
6. Installing the software
|
||||
[1m6. Installing the software[0m
|
||||
|
||||
At this point you will need to create 2 additional directories under
|
||||
"C:\Spider." Make directories "C:\spider\local" and
|
||||
@ -1773,7 +1773,7 @@
|
||||
you must write them as "\@" or "\$".
|
||||
|
||||
|
||||
6.1. Incoming telnets
|
||||
[1m6.1. Incoming telnets[0m
|
||||
|
||||
If you want to enable inbound "TELNET" connections (or you are running
|
||||
Windows 98, NT, 2000 or XP), you've got a little more work to do. From
|
||||
@ -1798,8 +1798,8 @@
|
||||
On my machine, I've simply uncommented the "0.0.0.0" entry by removing
|
||||
the '#' from the front of the line.
|
||||
|
||||
You MUST carry out this step if you are running on a Windows 98, NT,
|
||||
2000 or XP based system
|
||||
[1mYou MUST carry out this step if you are running on a Windows 98, NT,[0m
|
||||
[1m2000 or XP based system[0m
|
||||
|
||||
If you don't have a static hostname for your machine, and you intend
|
||||
to allow folk to connect to your machine across the internet, then I'd
|
||||
@ -1809,16 +1809,16 @@
|
||||
up.
|
||||
|
||||
|
||||
If your machine is connected to the internet and you don't want to
|
||||
If your machine is connected to the internet [1mand [22myou don't want to
|
||||
allow your machine to be visible to the outside world you should
|
||||
change the "0.0.0.0" to "127.0.0.1" [which is "localhost"]. This will
|
||||
then only allow connections from inside your machine. As was said
|
||||
earlier: if you aren't running Win9x (or you want to use DXTelnet or
|
||||
somesuch), then you need to have the machine listening at least to
|
||||
"127.0.0.1" ("0.0.0.0" means all IP addresses).
|
||||
"127.0.0.1" ("0.0.0.0" means [1mall [22mIP addresses).
|
||||
|
||||
|
||||
6.2. The AGW packet engine
|
||||
[1m6.2. The AGW packet engine[0m
|
||||
|
||||
On the assumption that you'll be using the SV2AGW Packet Engine to
|
||||
interface your radios to the cluster, it would be a good idea to
|
||||
@ -1872,7 +1872,7 @@
|
||||
needed for use with DXSpider.
|
||||
|
||||
|
||||
6.3. Setting up the initial user files
|
||||
[1m6.3. Setting up the initial user files[0m
|
||||
|
||||
Next you need to create the initial user files, etc. A tool is
|
||||
supplied which will do this for you. To run the tool:-
|
||||
@ -1951,9 +1951,9 @@
|
||||
|
||||
|
||||
|
||||
On getting the login: prompt, enter your sysop callsign (the one you
|
||||
On getting the [1mlogin: [22mprompt, enter your sysop callsign (the one you
|
||||
put in DXVars.pm as $myalias).
|
||||
I would recommend strongly that you obtain a better telnet client than
|
||||
I would recommend [1mstrongly [22mthat you obtain a better telnet client than
|
||||
that which comes with windows (I use PuTTY).
|
||||
|
||||
|
||||
@ -1981,7 +1981,7 @@
|
||||
7300). I recommend packages like DXTelnet.
|
||||
|
||||
|
||||
6.4. Connecting to other clusters
|
||||
[1m6.4. Connecting to other clusters[0m
|
||||
|
||||
If you want to connect this to another cluster, then you'll want to
|
||||
negotiate a link with someone. For experimental purposes, I'm happy to
|
||||
@ -1991,15 +1991,15 @@
|
||||
me by Email if you want me to set up a connection for you.
|
||||
|
||||
|
||||
7. General Information
|
||||
[1m7. General Information[0m
|
||||
|
||||
The following relates to all versions of DXSpider and is not platform
|
||||
related.
|
||||
|
||||
|
||||
7.1. The crontab file
|
||||
[1m7.1. The crontab file[0m
|
||||
|
||||
Login as sysop and create a file in /spider/local_cmd called crontab.
|
||||
Login as [4msysop[24m and create a file in /spider/local_cmd called crontab.
|
||||
Edit it with your favourite editor and add a line like this (I have
|
||||
included a comment)
|
||||
|
||||
|
||||
@ -31,15 +31,15 @@
|
||||
|
||||
|
||||
|
||||
1. Installation
|
||||
[1m1. Installation[0m
|
||||
|
||||
1.1. Where do I get DXSpider?
|
||||
[1m1.1. Where do I get DXSpider?[0m
|
||||
|
||||
All things Spider can be found at www.dxcluster.org and the actual
|
||||
program and patches can be found in the download area.
|
||||
|
||||
|
||||
1.2. How do I use the patches?
|
||||
[1m1.2. How do I use the patches?[0m
|
||||
|
||||
Patching is done in the standard linux way ...
|
||||
|
||||
@ -57,16 +57,16 @@
|
||||
first need to apply patch-1.39 and then patch-1.40.
|
||||
|
||||
|
||||
1.3. If I use a tarball to overwrite my installation, what happens to
|
||||
my configuration?
|
||||
[1m1.3. If I use a tarball to overwrite my installation, what happens to[0m
|
||||
[1mmy configuration?[0m
|
||||
|
||||
The tarballs are designed to not overwrite your existing configuration
|
||||
and can be used at any time to update your Spider software. All the
|
||||
key files have the suffix .issue (eg. DXVars.pm.issue) at default.
|
||||
|
||||
|
||||
1.4. I am running RedHat 5.2 and I am getting strange errors, what is
|
||||
wrong?
|
||||
[1m1.4. I am running RedHat 5.2 and I am getting strange errors, what is[0m
|
||||
[1mwrong?[0m
|
||||
|
||||
The version of Perl that comes with 5.2 seems to be some kind of pre-
|
||||
release and is broken. You can get a new version of perl from
|
||||
@ -74,9 +74,9 @@
|
||||
it with the CPAN modules.
|
||||
|
||||
|
||||
2. Administration
|
||||
[1m2. Administration[0m
|
||||
|
||||
2.1. How can I get Spider to restart automatically if it crashes?
|
||||
[1m2.1. How can I get Spider to restart automatically if it crashes?[0m
|
||||
|
||||
Put this line into /etc/inittab ..
|
||||
|
||||
@ -86,14 +86,14 @@
|
||||
|
||||
|
||||
|
||||
Run telinit q as root. Spider will restart so be aware. However, any
|
||||
Run [4mtelinit[24m [4mq[24m as root. Spider will restart so be aware. However, any
|
||||
time you reboot, cluster.pl will start in tty7 and if it crashes, it
|
||||
should restart ok.
|
||||
|
||||
|
||||
2.2. How can I monitor traffic to and from a node or user?
|
||||
[1m2.2. How can I monitor traffic to and from a node or user?[0m
|
||||
|
||||
There are 2 ways to achieve this. You can use the tail command like
|
||||
There are 2 ways to achieve this. You can use the [4mtail[24m command like
|
||||
this ..
|
||||
|
||||
|
||||
@ -102,7 +102,7 @@
|
||||
|
||||
|
||||
|
||||
or in later versions of Spider, there is a command called watchdbg in
|
||||
or in later versions of Spider, there is a command called [4mwatchdbg[24m in
|
||||
which case you simply type ..
|
||||
|
||||
|
||||
@ -111,12 +111,12 @@
|
||||
|
||||
|
||||
|
||||
2.3. My neighbouring node cannot use the RCMD command to me, he just
|
||||
keeps getting the "tut tut" message.
|
||||
[1m2.3. My neighbouring node cannot use the RCMD command to me, he just[0m
|
||||
[1mkeeps getting the "tut tut" message.[0m
|
||||
|
||||
Assuming that the permissions are set correctly (perm level 5
|
||||
required), it could be that the home_node is set incorrectly. You can
|
||||
reset the home_node using the spoof command like this ..
|
||||
reset the home_node using the [4mspoof[24m command like this ..
|
||||
|
||||
|
||||
|
||||
@ -127,17 +127,17 @@
|
||||
Assuming that the node_call you are changing is gb7adx.
|
||||
|
||||
|
||||
2.4. I do not seem to be sending any bulletin mail to my link part-
|
||||
ners, what is wrong?
|
||||
[1m2.4. I do not seem to be sending any bulletin mail to my link part-[0m
|
||||
[1mners, what is wrong?[0m
|
||||
|
||||
There is a file in /spider/msg called forward.pl.issue. Rename this
|
||||
to forward.pl and edit it to meet your requirements. You will need to
|
||||
issue the command load/forward or restart Spider for the changes to
|
||||
issue the command [4mload/forward[24m or restart Spider for the changes to
|
||||
take effect.
|
||||
|
||||
|
||||
2.5. How can I automatically limit the amount of debug logfiles that
|
||||
are stored?
|
||||
[1m2.5. How can I automatically limit the amount of debug logfiles that[0m
|
||||
[1mare stored?[0m
|
||||
|
||||
Use the tmpwatch command. Create a file in /etc/cron.daily/
|
||||
containing the line ...
|
||||
@ -153,8 +153,8 @@
|
||||
This will limit your debug data down to the last 10 days
|
||||
|
||||
|
||||
2.6. I updated my Linux distribution and now Spider cannot read the
|
||||
users file or the dupefile, what is the problem?
|
||||
[1m2.6. I updated my Linux distribution and now Spider cannot read the[0m
|
||||
[1musers file or the dupefile, what is the problem?[0m
|
||||
|
||||
Almost certainly this is a change in the db format of perl. Follow
|
||||
these few steps to correct the problem.
|
||||
@ -171,8 +171,8 @@
|
||||
That should solve the problem.
|
||||
|
||||
|
||||
2.7. Since I last updated I seem to be getting duplicate spots
|
||||
appearing.
|
||||
[1m2.7. Since I last updated I seem to be getting duplicate spots[0m
|
||||
[1mappearing.[0m
|
||||
|
||||
What has probably happened is that the dupefile has got corrupted in
|
||||
some way. Simply delete the /spider/data/dupefile and restart the
|
||||
@ -180,13 +180,13 @@
|
||||
should solve your problem.
|
||||
|
||||
|
||||
2.8. I have deleted a message but it is still there, why?
|
||||
[1m2.8. I have deleted a message but it is still there, why?[0m
|
||||
|
||||
This is now the way messages are handled for deletion in Spider. If
|
||||
you look closely you will see a 'D' following the message number.
|
||||
This message is marked for deletion and will be deleted in 2 days if
|
||||
nothing further is done. Optionally you can use the command
|
||||
delete/expunge to delete it immediately.
|
||||
[4mdelete/expunge[24m to delete it immediately.
|
||||
|
||||
|
||||
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
Loading…
Reference in New Issue
Block a user