Short:        Keeps AmiTCP & servers online for you
Author:       vancej@kiimbal.dyn.ml.org (Jim Vance)
Uploader:     vancej kiimbal dyn ml org (Jim Vance)
Type:         comm/misc
Architecture: m68k-amigaos


PURPOSE:
    
    This program is intended to help those of us trying to run servers on our 
    Amiga computers.  I ran into the problem of trying to keep my computer 
    online when I wasn't physically in front of (it does get boring just 
    sitting there sometimes... really).  So I decided to write a program
    to take care of the mundane task for me.
    
IDEA:

    The idea of this program was to keep my computer online, along with the 
    task of helping me figure out which port was causing crashes.  I called 
    it "Movelog" because it was originally intended to move the amitcp.log 
    file to a more permanent storage location, so that when my computer would
    crash, I would have a log to look at and see which program was the faulty 
    one.  
    
    Once I got the program to do that, I decided that it could examine each 
    line in the file for the signal that the modem was offline and reset it.  
    I will probably add a config file to allow users to determine what they 
    want to watch for along with a command to be executed when the
    line is found.
    
REQUIREMENTS:
    
    any AmiTCP version that uses the file "t:amitcp.log"
    any Amiga computer that is running AmiTCP.
    a knowledge of your commands that you use to bring your computer online 
            and take it offline again.

    The programs used by Movelog internally are:
        
        askhost   (to keep the link active by requesting data across the
                    link every 25 minutes)
        copy      (to copy needed commands to T: so that it doesn't need
                    to access the hard drive during run-time)
        status    (to check for another copy of itself running)
        say       (pretty much only if you have the "realms" MUD running
                    on the default port of 4563, AND you have logging turned
                    ON in your inet.access file)
        delete    (to clean up any files it moved to T: during the run)