|
FAQ Index...
What is "netscript"?
|
NetScript is a programmable, scriptable telnet client. You can create an configuration
which allows netscript to connect to a network service, send commands/data to it, get
responses, react to those responses, etc. The programming can be simple see X and
send Y type, or, you can write a shell or perl script to control it, or even a C
program!
|
Is it for me?
|
Fundamentally, if you like telnet for being excellent at what it is but
can't live without triggers and scripting, then this definitely is for you!
Since netscript is based on telnet it enjoys all the advantages of telnet
but with the extra added features you want!
|
Is my operating system supported?
|
Currently, only UNIX is directly supported, a competent UNIX systems administrator
should be able to make it work on most UNIX types. HOWEVER, if you
download Cygwin you can also
run it with Windows!
|
What features does it have?
|
Triggers
|
A simple "see" X and send Y system.
| |
Scripts
|
You can write a script to respond to mud output and send back commands
(like a trigger). Scripts can be written in anything that can compile
or be interpretted independantly (so that means you can write scripts
in Perl, C, C++, shell and almost endless other languages).
| |
Recording
|
Automatic archive of everything acquired from the network.. for later play back!
|
Is it better than tintin?
|
I could not possibly comment! Try it, and I would be very interested in
your feedback!
|
Who wrote it?
How do I report bugs?
|
Please send email to
netscript-bugs@itechsc.com and remember to say which version
you have, what operating system you are using and what the problem
is. If netscript actually crashs, please send a description (as best
you can, if you can) of what was happening at the time and attach
the core file if one is generated... not that there are any bugs
in it of course...
|
How do I suggest improvements?
How do I configure it?
|
Please see the HOW TO web page.
|
Why isn't my script working?
1. Do you have a ".netscript" directory in your home?
2. Do you have a site inside that?
3. Do you have a task directory inside that?
4. Do you have a "scripts" directory in your task directory?
5. Do you have a "triggers.txt" file in your task directory?
6. Does the "triggers.txt" file have a line like this: see "X" exec "Y"
7. Have you actually included the double quotes, like above?
8. Is Y (above) the name of a file in your "scripts" directory?
9. Is the file "scripts/Y" executable?
If you've done all the above, make sure that netscript is actually
seeing the text required to trigger the script...
Use the "ps" command to see if the script is running. The usage of
"ps" varies from UNIX to UNIX.
|
How can I get more help?
|
Please try using the netscript mailing lists.
Subscribe to the netscript-users list, post your quesion, maybe someone
will be able to help you.
|
|
