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.49: Information, files and useful programs</TITLE>
6 <LINK HREF="adminmanual-7.html" REL=next>
7 <LINK HREF="adminmanual-5.html" REL=previous>
8 <LINK HREF="adminmanual.html#toc6" REL=contents>
9 <link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
12 <A HREF="adminmanual-7.html">Next</A>
13 <A HREF="adminmanual-5.html">Previous</A>
14 <A HREF="adminmanual.html#toc6">Contents</A>
16 <H2><A NAME="s6">6. Information, files and useful programs</A></H2>
18 <H2><A NAME="ss6.1">6.1 MOTD</A>
21 <P>One of the more important things a cluster sysop needs to do is to get
22 information to his users. The simplest way to do this is to have a banner
23 that is sent to the user on login. This is know as a "message of the day"
24 or "motd". To set this up, simply create a file in /spider/data called motd
25 and edit it to say whatever you want. It is purely a text file and will be
26 sent automatically to anyone logging in to the cluster.
28 <H2><A NAME="ss6.2">6.2 MOTD_NOR</A>
31 <P>This message of the day file lives in the same directory as the standard
32 motd file but is only sent to non-registered users. Once registered they
33 will receive the same message as any other user.
35 <H2><A NAME="ss6.3">6.3 Downtime message</A>
38 <P>If for any reason the cluster is down, maybe for upgrade or maintenance but
39 the machine is still running, a message can be sent to the user advising them
40 of the fact. This message lives in the /spider/data directory and is called
41 "offline". Simply create the file and edit it to say whatever you wish.
42 This file will be sent to a user attempting to log into the cluster when
43 DXSpider is not actually running.
45 <H2><A NAME="ss6.4">6.4 Other text messages</A>
48 <P>You can set other text messages to be read by the user if they input the file
49 name. This could be for news items or maybe information for new users.
50 To set this up, make a directory under /spider called <EM>packclus</EM>.
51 Under this directory you can create files called <EM>news</EM> or <EM>newuser</EM>
52 for example. In fact you can create files with any names you like. These can
53 be listed by the user with the command ....
60 <P>They can be read by the user by typing the command ....
67 <P>If the file they want to read is called <EM>news</EM>. You could also set
68 an alias for this in the Alias file to allow them just to type <EM>news</EM>
70 <P>You can also store other information in this directory, either directly or
71 nested under directories. One use for this would be to store DX bulletins
72 such as the OPDX bulletins. These can be listed and read by the user.
73 To keep things tidy, make a directory under /spider/packclus called
74 <EM>bulletin</EM>. Now copy any OPDX or similar bulletins into it. These
75 can be listed by the user in the same way as above using the <EM>show/files</EM>
76 command with an extension for the bulletin directory you have just created,
85 <P>An example would look like this ....
90 bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
93 <P>You can see that in the files area (basically the packclus directory) there is a
94 file called <EM>news</EM> and a directory called <EM>bulletin</EM>. You can
95 also see that dates they were created. In the case of the file <EM>news</EM>,
96 you can also see the time it was last modified, a good clue as to whether the
97 file has been updated since you last read it. To read the file called
98 <EM>news</EM> you would simply issue the command ....
105 <P>To look what is in the bulletin directory you issue the command ....
110 opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
111 opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
112 opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
113 opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
114 opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
115 opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
116 opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
117 opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
118 opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
119 opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
120 opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
121 opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
122 opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
123 Press Enter to continue, A to abort (16 lines) >
126 <P>You can now read any file in this directory using the type command, like this ....
130 type bulletin/opdx391
131 Ohio/Penn DX Bulletin No. 391
132 The Ohio/Penn Dx PacketCluster
136 Editor Tedd Mirgliotta, KB8NW
137 Provided by BARF-80 BBS Cleveland, Ohio
138 Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
139 Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
140 Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
141 & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
142 Press Enter to continue, A to abort (508 lines) >
145 <P>The page length will of course depend on what you have it set to!
147 <H2><A NAME="ss6.5">6.5 The Aliases file</A>
150 <P>You will find a file in /spider/cmd/ called Aliases. First, copy this file to
151 /spider/local_cmd/Aliases and edit this file. You will see something like this ...
158 # provide some standard aliases for commands for terminally
159 # helpless ak1a user (helpless in the sense that they never
160 # read nor understand help files)
162 # This file is automagically reloaded if its modification time is
163 # later than the one stored in CmdAlias.pm
165 # PLEASE make this file consistant with reality! (the patterns MUST
166 # match the filenames!)
168 # Don't alter this file, copy it into the local_cmd tree and modify it.
169 # This file will be replaced everytime I issue a new release.
171 # You only need to put aliases in here for commands that don't work as
172 # you desire naturally, e.g sh/dx on its own just works as you expect
173 # so you need not add it as an alias.
181 '^\?', 'apropos', 'apropos',
184 '^ann.*/full', 'announce full', 'announce',
185 '^ann.*/sysop', 'announce sysop', 'announce',
186 '^ann.*/(.*)$', 'announce $1', 'announce',
193 '^del', 'kill', 'kill',
194 '^del\w*/fu', 'kill full', 'kill',
195 '^di\w*/a\w*', 'directory all', 'directory',
196 '^di\w*/b\w*', 'directory bulletins', 'directory',
197 '^di\w*/n\w*', 'directory new', 'directory',
198 '^di\w*/o\w*', 'directory own', 'directory',
199 '^di\w*/s\w*', 'directory subject', 'directory',
200 '^di\w*/t\w*', 'directory to', 'directory',
201 '^di\w*/f\w*', 'directory from', 'directory',
202 '^di\w*/(\d+)', 'directory $1', 'directory',
219 '^l$', 'directory', 'directory',
220 '^ll$', 'directory', 'directory',
221 '^ll/(\d+)', 'directory $1', 'directory',
226 '^news', 'type news', 'type',
236 '^r$', 'read', 'read',
237 '^rcmd/(\S+)', 'rcmd $1', 'rcmd',
240 '^s/p$', 'send', 'send',
241 '^sb$', 'send noprivate', 'send',
242 '^set/home$', 'set/homenode', 'set/homenode',
243 '^set/nobe', 'unset/beep', 'unset/beep',
244 '^set/nohe', 'unset/here', 'unset/here',
245 '^set/noan', 'unset/announce', 'unset/announce',
246 '^set/nodx', 'unset/dx', 'unset/dx',
247 '^set/nota', 'unset/talk', 'unset/talk',
248 '^set/noww', 'unset/wwv', 'unset/wwv',
249 '^set/nowx', 'unset/wx', 'unset/wx',
250 '^sh$', 'show', 'show',
251 '^sh\w*/buck', 'dbshow buck', 'dbshow',
252 '^sh\w*/bu', 'show/files bulletins', 'show/files',
253 '^sh\w*/c/n', 'show/configuration nodes', 'show/configuration',
254 '^sh\w*/c$', 'show/configuration', 'show/configuration',
255 '^sh\w*/com', 'dbavail', 'dbavail',
256 '^sh\w*/dx/(\d+)-(\d+)', 'show/dx $1-$2', 'show/dx',
257 '^sh\w*/dx/(\d+)', 'show/dx $1', 'show/dx',
258 '^sh\w*/dx/d(\d+)', 'show/dx from $1', 'show/dx',
259 '^sh\w*/email', 'dbshow email', 'dbshow',
260 '^sh\w*/hftest', 'dbshow hftest', 'dbshow',
261 '^sh\w*/vhftest', 'dbshow vhftest', 'dbshow',
262 '^sh\w*/qsl', 'dbshow qsl', 'dbshow',
263 '^sh\w*/tnc', 'who', 'who',
264 '^sh\w*/up', 'show/cluster', 'show/cluster',
265 '^sh\w*/w\w*/(\d+)-(\d+)', 'show/wwv $1-$2', 'show/wwv',
266 '^sh\w*/w\w*/(\d+)', 'show/wwv $1', 'show/wwv',
267 '^sp$', 'send', 'send',
271 '^ta$', 'talk', 'talk',
272 '^t$', 'talk', 'talk',
279 '^wx/full', 'wx full', 'wx',
280 '^wx/sysop', 'wx sysop', 'wx',
291 <P>You can create aliases for commands at will. Beware though, these may not
292 always turn out as you think. Care is needed and you need to test the
293 results once you have set an alias.
295 <H2><A NAME="ss6.6">6.6 Console.pl</A>
298 <P>In later versions of Spider a simple console program is provided for the sysop.
299 This has a type ahead buffer with line editing facilities and colour for spots,
300 announces etc. To use this program, simply use console.pl instead of client.
302 <P>To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the
303 file with your favourite editor.
305 <H2><A NAME="ss6.7">6.7 Updating kepler data</A>
308 <P>Spider has a powerful and flexible show/satellite command. In order for
309 this to be accurate, the kepler data has to be updated regularly. In
310 general, this data is available as an email or via cluster mail.
311 Updating it is simple. First you need to export the mail message as a
312 file. You do this with the <EM>export</EM> command from the cluster prompt
313 as the sysop. For example ...
317 export 5467 /spider/perl/keps.in
320 <P>would export message number 5467 as a file called keps.in in the
321 /spider/perl directory.
322 <P>Now login to a VT as sysop and cd /spider/perl. There is a command in
323 the perl directory called <EM>convkeps.pl</EM>. All we need to do now is
324 convert the file like so ...
328 ./convkeps.pl keps.in
331 <P>Now go back to the cluster and issue the command ...
338 <P>That is it! the kepler data has been updated.
340 <H2><A NAME="ss6.8">6.8 The QRZ callbook</A>
343 <P>The command <EM>sh/qrz</EM> will only work once you have followed a few
344 simple steps. First you need to get a user ID and password from qrz.com.
345 Simply go to the site and create one. Secondly you need to copy the file
346 /spider/perl/Internet.pm to /spider/local and alter it to match your user
347 ID and password. You also at this point need to set $allow=1 to complete
348 the setup. Many thanks to Fred Lloyd, the proprieter of
349 <A HREF="http://www.qrz.com">qrz.com</A> for allowing this access.
352 <A HREF="adminmanual-7.html">Next</A>
353 <A HREF="adminmanual-5.html">Previous</A>
354 <A HREF="adminmanual.html#toc6">Contents</A>