# PPP-Script 1.0.1
# Written by (Karsten Johansson) ksaj@ims.pcscav.com
# Sat Dec 2, 1995

WHY USE THESE SCRIPTS INSTEAD OF THE DEFAULT ONES FROM THE PPPD DISTRIBUTION?

Because they are set up for a one-shot connection only.  If the modem lost
carrier for any reason, the script would just exit instead of trying to
re-establish the connection.

As well as that, the script stays in memory, using up 2 more processes than 
necessary.


WHAT MAKES THESE SCRIPTS BETTER?

These scripts execute pppd as a daemon should be -- in the background as a
single process with no strings attached.  If the modem disconnects for any
reason (except an explicit shutdown), a reconnect is attempted every 5 
minutes until it is successful.

/etc/ppp/ppp-down shuts down the ppp daemon, and then adds a 0-byte file
called ppp-down to your /etc directory.  DO NOT REMOVE THIS FILE.  It is
automatically removed when ppp-up is executed.


INSTALLATION:

1: Make sure your PPP setup is already working.
2: Put these scripts in /etc/ppp directory, and make sure ppp-up is
   readable by root ONLY.
3: Edit the scripts for MODEM and DEVICE, and the 'chat' script in ppp-up.
   Also edit paths to pppd, chat and the lock files if they are different.
4: Remove '-detach' from the the options file if it exists.  The modem will
   hang up every time the script exits if you don't.
5: Add the following entry to root's crontab:

   0,5,10,15,20,25,30,35,40,45,50,55 * * * *     /etc/ppp/uptest

6: Run /etc/ppp/ppp-up to test it out.
7: When you have it working, add /etc/ppp/ppp-up to your rc.local or rc.net
   file.
8: Viola!  You are done.


SUPPORT:

This software is FreeWare.  All rights remain the author's (mine).  You may
modify it to your heart's content, but do not upload a modified version
ANYWHERE.  If you have a really cool modification or addition, email me the
info, and maybe, just maybe it will appear in a future version of this
software.

Send kudos, or at least a brief 'hello' to tell me what you think of these
scripts, and how you've found them useful.  I'm interested in knowing
who is using these scripts, and where.


BUGS:

1.0.0	- one of the scripts had a procedure repeated.  Editor snuck it in
          when I wasn't looking.  Caused the cron script to fail.

1.0.1   - none known...

                               --- end ---
