1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
4 <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
5 <TITLE>The DXSpider Administration Manual v1.48: Scripts</TITLE>
6 <LINK HREF="adminmanual-5.html" REL=next>
7 <LINK HREF="adminmanual-3.html" REL=previous>
8 <LINK HREF="adminmanual.html#toc4" REL=contents>
9 <link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
12 <A HREF="adminmanual-5.html">Next</A>
13 <A HREF="adminmanual-3.html">Previous</A>
14 <A HREF="adminmanual.html#toc4">Contents</A>
16 <H2><A NAME="s4">4. Scripts</A></H2>
18 <P>From 1.48 onwards it will become increasingly possible to control DXSpider's
19 operation with scripts of various kinds.
21 <P>In the first instance, in 1.48, the sysop can create, with their favorite
22 text editor, files in the directory <EM>/spider/scripts</EM> which contain
23 any legal command for a callsign or class of connection which will be executed
27 The filename are the callsign of the connection that you want the script to
28 operate on, eg: <EM>/spider/scripts/g1tlh</EM>. The filenames are always in
29 lower case on those architectures where this makes a difference.
31 <P>In addition to the callsign specific scripts there are three others:-
40 <P>The <EM>startup</EM> script is executed immediately after all
41 initialisation of the node is done, but before any connections are
44 <P>The <EM>user_default</EM> script is executed for every user that does
45 <B>NOT</B> already have a specific script.
47 <P>The <EM>node_default</EM> script is executed for every node that doesn't
48 have a specific script.
50 <P>There are a couple of examples in the <EM>/spider/scripts</EM> directory.
53 <A HREF="adminmanual-5.html">Next</A>
54 <A HREF="adminmanual-3.html">Previous</A>
55 <A HREF="adminmanual.html#toc4">Contents</A>