home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Black Box 4
/
BlackBox.cdr
/
bbs_mail
/
rec_110.arj
/
RECUSER.DOC
< prev
next >
Wrap
Text File
|
1991-04-20
|
9KB
|
256 lines
Remote Echo Control (REC)
Version 1.10
User Documentation
Copyrighted (c) 1990, 1991 by Daniel S. Fitch
All Rights Reserved
INTRODUCTION
Remote Echo Control (REC) is a program that allows you to
remotely control which echos you receive from your echo hub.
It was written with multiple zones in mind, which is a major
limitation in other software packages that perform this
function. This eliminates the manual intervention required
when added or deleting echos from your feed. Your echo hub
sysop installs this program, defines your system to REC, and
assigns you a password. From then on, it is all up to you.
USING REC
To use REC, all you do is send a net-mail message to
your echo hub's system. You address the message to "Remote
Control" and put your password on the subject line. Make sure
you mark the message private. You then list the echos you want
to start or stop. After the last echo, you put in three
dashes starting in column 1, or "---". This tells REC to
ignore the rest of the message, which allows you to enter
comments after the dashed line. You can put up to 50 commands in
one message, any more after that will be ignored without crashing
REC on your echo hub's system.
Your echo hub will receive the message and process it. A
reply message will be sent back to you with the results of what
REC did with your message. There are various possible replies,
which will be out-lined a little bit later.
For this example, we will assume that you are already
receiving 5 echos: BARONS, SYSOP, GAMING, AD&D, and SCI_FI.
None of your users seem to interested in SCI_FI, but several
have asked that you get the echo for Star Trek and Ham Radio.
You would sent a message that would look like this:
-SCI_FI
TREK
HAM_RADIO
---
Add trek and Ham echos, remove Science Fictions echo.
By putting a single dash in front of the echo, you are
telling your echo hub to stop the echo. By simply listing the
echo name, you are telling your echo hub to start sending you
the echo. The dash line, sometimes called a "tear line", just
tells REC to ignore the rest of the message.
After your echo hub receives the message, you will be sent a
reply telling you what happened. Such a reply might look like
this:
SCI_FI............Removed TREK..............Added
HAM_RADIO.........Added
---
This message created by Remote Echo Control (REC) version
1.00
That is really all there is to it. Once you have your
password, you can begin to start and stop your echos just this
easily. However, there are some security concerns that should
be discussed at this point.
SECURITY
As I stated before, REC was designed to work in
multiple zones at the same time. As such, it will only allow you
to access echos in your own zone, within your security level, and
that you have not been locked out of. However, there is an
exception.
CrossZone is the exception to the above rule. If you echo
hub so chooses, you can be allowed to access echos in other
zones. Which echos you will be allowed to get from "foreign
zones" is dependent on the Security and Lockout options shown
next. These can be used for either CrossZone or non-CrossZone
situations.
Echo Security and Echo Lockouts are at the option of
your Echo Hub. Your echo hub is required to assign your system
an echo security level. The echo hub then has the option of
assigning security levels to individuals echos. If you request
an echo with a required security higher than your own system, you
are not allowed that echo.
The echo hub can also setup an echo lockout. This is
simply a listing of which echos are not to be sent to a
particular system. If you request an echo that you are locked
out of, you will not be allowed access to the echo.
REQUEST FORWARDING
It is possible that you may request an echo from your
echo hub that is not already being received by your echo hub.
At the option of your echo hub, your request can be either
denied or accepted with the request also being passed on to
the echo hub's feed for that zone. This is called Request
Forwarding.
If this happens, you will receive a reply indicating that
the echo was added and it was also forwarded. This is
important because a forwarded request may take longer to start
entering your system.
ECHO REPORTS
There are two reports that you can request from REC. They
can be sent by themselves or as part of an echo request. One
report is the Acitve Echo Report. This report lists all the
echos that are currently being sent to your system. The
second report is the Available Echo Report. This report lists
all the echos currently being received by your echo hub that you
are allowed to receive.
Requesting a report is very easy. You send a message off
the REC just like you were changing your echos. A report
request is indicated by a colon, ":", in column 1 followed by
a single letter indicating which report you want. The Active
Echo Report is the letter "R" and the Available echo Report is
the letter "L".
COMPLETE EXAMPLE
Below follows a complete example of an REC message. This
example will show all the possible commands, and which messages
they produce.
to: Remote Control on 1:104/435, The REC Room
fr: Dan Fitch on 1:104/453, My Test Site
re: password
STTNG
TREK
-STINKY
:R
-APPLES
PLAY_TIME
FANTASY
-FUNKY
HACKER
TROUBLE_MAKER
---
This is a complete example.
The reply may look something like this:
to: Dan Fitch on 1:104/453, My Test Site
fr: Remote Control on 1:104/435, The REC Room
re: Echo Change Request
STTNG..................Added
TREK...................Already Active
STINKY.................Removed
Report R...............Requested report follows
APPLES.................Not Active
PLAY_TIME..............Access Denied, Not in your Zone
FANTASY................Added, Request forwarded
FUNKY..................Not Processed
HACKER.................Access Denied, Invalid Security
TROUBLE_MAKER..........Access Denied, Lockout
---
Below is a report of all echos active for 1:104/453:
AD&D
BARONS
FANTASY
GAMING
HAM_RADIO
SYSOP
TREK
---
This message was produced by Remote Echo Control (REC) 1.00
The STTNG echo was added without any problem, but the
TREK echo was already being sent. The STINKY echo is no longer
being sent down to you. You asked to stop the APPLES echo, but
it wasn't being sent to you from this echo hub. The PLAY_TIME
echo was in a different zone from in which you are located.
The FANTASY echo was added, but a request had to be sent off
to the echo hub feed to recieve the echo. You asked to delete
the FUNKY echo, but that echo was not found on the echo hub's
system. You didn't have enough security to get the HACKER echo,
and you are locked out of TROUBLE_MAKER. A report of all your
currently active echos is attached to list reply.
POINT SYSTEMS
How a point system will be handled is up to the sysop of you
echo hub. However, you MUST be careful about one concern. Make
sure you send the change request to the correct address. You
will receive the reply from whatever address you send the request
to. If you send the request to the wrong address, your echo hub
may not be able to route the reply back to you.
CONCLUSION
That is all there is to it. The program is fast and easy
to use, for both the echo hub and the echo node. If you have
any problems or suggestions, please send them to your echo hub
first. If necessary, your echo hub will forward them off to the
author.
I hope you enjoy using the program, and find that it
saves your much time and headache in controlling your echo feed.
Later!
Dan Fitch
Author of Remote Echo Control (REC)
Sysop of The Rec Room
1:104/435@FidoNet
200:5000/211@MetroNet
Denver, Colorado
revised April 20, 1991.