head 1.10; access; symbols; locks; strict; comment @# @; 1.10 date 98.08.27.15.22.16; author alexis; state Exp; branches; next 1.9; 1.9 date 98.03.01.14.57.11; author alexis; state Exp; branches; next 1.8; 1.8 date 98.03.01.14.26.48; author alexis; state Exp; branches; next 1.7; 1.7 date 98.02.28.14.45.48; author alexis; state Exp; branches; next 1.6; 1.6 date 97.11.24.16.05.42; author alexis; state Exp; branches; next 1.5; 1.5 date 97.11.12.13.48.19; author alexis; state Exp; branches; next 1.4; 1.4 date 97.11.11.12.07.18; author alexis; state Exp; branches; next 1.3; 1.3 date 97.10.26.20.55.35; author alexis; state Exp; branches; next 1.2; 1.2 date 97.10.26.20.12.57; author alexis; state Exp; branches; next 1.1; 1.1 date 97.10.26.18.54.40; author alexis; state Exp; branches; next ; desc @read me file for ppplc @ 1.10 log @*** empty log message *** @ text @------------------------------------------------------------------------------ Title: INSTALLATION INSTRUCTIONS FOR FAD RELEASE PATCHLEVEL_MARKER Version: $Id: INSTALL.in,v 1.9 1998/03/01 14:57:11 alexis Exp alexis $ ------------------------------------------------------------------------------ 0a. These instructions contain absolute and relative pathnames. The relative pathnames are relative with respect to the subdirectory created by the unpacking process (i.e. cd to where this INSTALL file is and then cd up one. View this file as doc/INSTALL. 0b. If you are a source distribution of ppplc, then don't bother printing these instructions yet. The first couple of instructions actually modify this file! 0c. If you have a binary distribution of ppplc, then go straight to step 3b. 1. Work your way through ./Makefile.defs changing things as instructed there. 2. As non-root run: make If you are viewing file ./doc/INSTALL.in, then at this point, quit out of your viewer and view ./doc/INSTALL instead, continuing at instruction 3a. (this 'make' instruction actually alters *this* file!) 3a. As root run: make install 3b. As root run: mv /etc/ppp /etc/ppp.old mkdir /etc/ppp ln -s PRGLIBDIR_MARKER/ip-up /etc/ppp/ip-up ln -s PRGLIBDIR_MARKER/ip-down /etc/ppp/ip-down ln -s PRGLIBDIR_MARKER/options /etc/ppp/options cp doc/examples/ppplc.cfg /usr/local/etc 4. If you run a System V style 'init' (does /etc/init.d exist?) then: you may run the following as root cp doc/examples/local-ppplc /etc/init.d ln -s /etc/init.d/local-ppplc /etc/rc0.d/K01local-ppplc ln -s /etc/init.d/local-ppplc /etc/rc6.d/K01local-ppplc As root run the following commands (if the runlevels to invoke the daemon on are not '2' and '3' then modify) : ln -s /etc/init.d/local-ppplc /etc/rc2.d/S99local-ppplc ln -s /etc/init.d/local-ppplc /etc/rc3.d/S99local-ppplc 5. If you are running a 'simple style 'init' (does /etc/rc.local or /etc/rc.d/rc.local exist?) then: Add the following lines to that file: PPPLCD=LCLSBINDIR_MARKER/ppplcd CONFIG=PRGCFGDIR_MARKER/ppplc.cfg echo "Starting ppplcd" rm -f LOCKDIR_MARKER/ppplcd.* if [ ! -x $PPPLCD ]; then echo "$PPPLCD: not found" elif [ ! -r $CONFIG ]; then echo "$CONFIG: not found" else $PPPLCD $CONFIG > /dev/null 2>&1 fi 6. After that there is only one more step, and that is review the configuration file - PRGCFGDIR_MARKER/ppplc.cfg - checking and possibly changing certain parts. Consult the manual pages for ppplc.cfg(4) for further information. Note that if your modem is *NOT* a US Robotics Courier or your ISP is *NOT* Demon, then this configuration will require you to write chat scripts for your modem or ISP, but that will become clearer as you work through the config file. (Please please please send any new modem or ISP configuration files you write to the author for inclusion in the next release.) 7. Consult the manual page for ppplcc(1) for further information on actually connecting. 8. An example crontab entry you may wish to add to root's crontab can be found in ./doc/examples. ------------------------------------------------------------------------------ @ 1.9 log @moved ppplcd from bin to sbin @ text @d3 1 a3 1 Version: $Id: INSTALL.in,v 1.8 1998/03/01 14:26:48 alexis Exp alexis $ d6 7 a12 1 0) Don't bother printing these instructions yet. The first couple of d15 3 d25 5 a29 2 After doing this, resume following instructions from ./doc/README (which will have changed as a result of this step). d31 1 a31 1 3. As root run: d34 5 a38 2 mkdir /etc/ppp/old cp /etc/ppp/* /etc/ppp/old d44 1 a44 1 4. If you run a System V style 'init' (does /etc/rc.init exist?) then: @ 1.8 log @split README.1ST and INSTALL apart as is for other sources @ text @d3 1 a3 1 Version: $Id: INSTALL,v 1.12 1998/02/12 12:28:54 alexis Exp $ d48 1 a48 1 PPPLCD=LCLBINDIR_MARKER/ppplcd @ 1.7 log @added brief documentation about the scripts that support 'suck' @ text @d1 4 a4 2 README.1ST FILE FOR PPPLC RELEASE PATCHLEVEL_MARKER --------------------------------------------------- a5 75 Identification -------------- $Id: README.in,v 1.6 1997/11/24 16:05:42 alexis Exp alexis $ Description ----------- This is an alpha release of the PPPLC package - a pppd wrapper daemon and control client. It comprises the following programs: ppplcd: (the PPP link control daemon) This is responsible for invoking other programs in a timely manner - e.g. for the transfer of news and mail, to perform regular quality checks on the phone line etc. sndmsg: (lightweight IPC message dispatcher) This program simply puts instructional messages onto a IPC message queue which are then read off by ppplcd. These messages tell ppplcd to do various things, like hanging up the phone, connecting, etc. ppplcc: (menu driven wrapper for sndmsg) This is a simple shell script that displays a menu of actions and then invokes sndmsg with the correct parameters which then instructs ppplcd to take the specified action. qtest,announce: (link quality tester and connection status reporter) These are two scripts included as part of the distribution. You don't have to use them but it is likely you will want to. Further information on these will be found in the configuration file, which is explained later. sndnews-nntpxmit,getnews-slurp: (news transfer programs) It is very unlikely that these will suit you - they are written for transfer of news in a "C News" news database via NNTP. They rely on the existence of 'xmitnews' and 'slurp'. If you wish to make news transfer automatic using this system and you don't have 'slurp' and 'xmitnews' then you're going to have to write your own scripts to transfer news. You might be able to hack bits out of your existing /etc/ppp/ip-up in order to do this. sndnews-suck,getnews-suck: (news transfer programs) Written for 'suck'. Beware that getnews-suck calls get-news; which (in Debian/GNU Linux) is a wrapper for suck *AND* rpost, performing both getting and sending. (Therefore sndnews-suck actually does nothing.) sndmail,getmail: (news transfer programs) It is also unlikey that these will suit you - unless your ISP is Demon. 'sndmail' simply invokes sendmail to flush the mail queue. 'getmail' does absolutely nothing - which is fine for Demon, who *push* mail out without explicit request. They rely on 'sendmail'. So if you use don't use sendmail or your ISP is not Demon or you send and retrieve your email via SMTP they you will have to write you own versions of these scripts. ip-up, ip-down: (replacement ip-up and ip-down programs) These are effectively copied to /etc/ppp. All they do is invoke 'sndmsg' to inform ppplcd that they have been called. Copyright Policy ---------------- It is distributed under the terms of the GNU Public License, the conditions of which can be found in the file ./doc/COPYING. Installation ------------ d9 2 a10 1 1) Modify Makefile.defs as instructed in that file. d12 1 a12 1 2) Run as yourself: d14 1 a14 1 make d16 2 a17 1 After doing this, resume following instructions from ./doc/README. d19 1 a19 1 3) Run as root: d21 7 a27 7 make install mkdir /etc/ppp/old cp /etc/ppp/* /etc/ppp/old ln -s PPPLCLIBDIR_MARKER/ip-up /etc/ppp/ip-up ln -s PPPLCLIBDIR_MARKER/ip-down /etc/ppp/ip-down ln -s PPPLCLIBDIR_MARKER/options /etc/ppp/options cp doc/examples/ppplc.cfg /usr/local/etc d29 1 a29 1 4) If you run a System V style 'init' (does /etc/rc.init exist?) then: d43 1 a43 1 5) If you are running a 'simple style 'init' (does /etc/rc.local or a47 1 d49 1 a49 1 CONFIG=PPPLCCFGDIR_MARKER/ppplc.cfg d60 19 a78 15 6) After that there is only one more step, and that is review the configuration file - PPPLCCFGDIR_MARKER/ppplc.cfg - checking and possibly changing certain parts. Note that if your modem is *NOT* a US Robotics Courier or your ISP is *NOT* Demon, then this configuration will require you to write chat scripts for your modem or ISP, but that will become clearer as you work through the config file. Bugs etc -------- Mail the author. Author ------ Alexis Huxley @ 1.6 log @more comments @ text @d6 1 a6 1 $Id: README.in,v 1.5 1997/11/12 13:48:19 alexis Exp alexis $ d39 1 a39 1 sndnews,getnews: (news transfer programs) d50 7 @ 1.5 log @minor fixes. @ text @d6 1 a6 1 $Id: README.in,v 1.4 1997/11/11 12:07:18 alexis Exp alexis $ d11 53 a63 1 control client. d73 1 a73 1 instructions actuaally modify this file! d86 2 d116 1 @ 1.4 log @corrected installation instructions to depend on whether using simple init or Sys V init. @ text @d6 1 a6 1 $Id: README.in,v 1.3 1997/10/26 20:55:35 alexis Exp alexis $ d20 3 d29 2 a60 1 SNDMSG=LCLBINDIR_MARKER/sndmsg d67 1 a67 1 $PPPLCD $CONFIG d70 7 a76 3 Configuration ------------- Edit PPPLCCFGDIR_MARKER/ppplc.cfg and modify as instructed there. @ 1.3 log @more directory changes @ text @d6 1 a6 1 $Id: README.in,v 1.2 1997/10/26 20:12:57 alexis Exp alexis $ a12 3 Manifest -------- d20 45 a64 9 1) Modify Makefile.defs as instructed in that file 2) make install 3) ln -s LCLLIBDIR_MARKER/ppplc/ip-up /etc/ppp/ip-up ln -s LCLLIBDIR_MARKER/ppplc/ip-down /etc/ppp/ip-down ln -s LCLLIBDIR_MARKER/ppplc/options /etc/ppp/options 4) cp doc/examples/local-ppplc /etc/init.d 5) cp doc/examples/ppplc.cfg /usr/local/etc 6) ln -s /etc/init.d/local-ppplc /etc/rc.d/S99local-ppplc ln -s /etc/init.d/local-ppplc /etc/rc.d/K01local-ppplc @ 1.2 log @more directory reorg fixes @ text @d6 1 a6 1 $Id: README,v 1.1 1997/10/26 18:54:40 alexis Exp alexis $ d35 1 a35 1 Edit PPPLCDCFGDIR_MARKER/ppplc.cfg and modify as instructed there. @ 1.1 log @Initial revision @ text @d6 1 a6 1 $Id$ d25 3 a27 1 3) cp doc/examples/ip* /etc/ppp d29 2 a30 1 5) ln -s /etc/init.d/local-ppplc /etc/rc.d/S99local-ppplc a31 1 6) cp doc/examples/ppplc.cfg /usr/local/etc d35 1 a35 1 Edit /usr/local/etc/ppplc.cfg and modify as instructed there. d39 1 a39 3 Bugs, suggestions for further development, etc should be sent to me at the address below. Also I would be very interested to hear from anyone who finds novel uses for these tools. d41 2 a42 2 Contact ------- @