*************************************************************************** * * * LogMan * * * * by Bob Rye * * * * Public Release: Friday 25/09/1992 * * * *************************************************************************** Everything contained in this release of LogMan for the Amiga is USE-AT-OWN-RISK. We, the authors, make no guarantee as to the fitness for use of this software. We accept no responsibility for possible damages incurred before, during or after execution of this software. #### # #### #### #### #### #### #### #### ### ##### # # # #### # # # # # # # # # # # # # # # # # # # # # # #### # ### #### #### ### #### ### #### # # # #### # #### # # # # # # # # # # # # # # # # # # # # # #### #### # # #### #### # # #### # # ### # # # # #### # ***************************************************************************** DID YOU PAY MONEY FOR THIS SOFTWARE? LogMan is FREEWARE This software is FREEWARE. This software is free. If you have paid money for this software, then you have been ripped off. I have written this program for you, for free. If you paid for "support" from where you got this file, then you are also being ripped off. There is only one person who can fully help you with the operation of this program: ME (Bob Rye, the guy who wrote this program.) You cannot obtain support from some unqualified desk-doofus hiding behind the facade of "a support specialist". All that these people are doing is making money from you, the innocent end-user, and ripping me off by immorally making money from *MY* programs. Please take a stand against these companies. Please don't buy *FREE* software from these companies. If you would like copies of any (or all) of MY software (anything by Bob Rye) you can have them for *FREE*. That's right, for nothing. All I ask for is a blank disk, to copy the programs onto, and the cost of return postage (and your address!) Then if you want "support" for my programs, send Fido Netmail to me (addresses are at the bottom of this document) or snail-mail me and you'll get real support. STAND UP AND BE COUNTED. Say NO! to costly FREE software. ***************************************************************************** If you represent a PD/Shareware/Freeware library or electronic distribution system, then please feel free to contact me to gain written permission to allow you to legally include this software in your library, for distribution. The "ADS" electronic distribution system has my written permission to redistribute this software, as does Fred Fish. You may copy and transfer copies of this package to whoever you like, provided that this package is transferred completely intact, with all documentation and executables unmodified therein (modification of copyrighted works is called "contributory copyright infringement" and persons found infringing copyright are liable to legal action); however, if you represent a registered (or otherwise) company, and you wish to redistribute this package, you MUST obtain my written permission. The copyright to LogMan, the documentation, the source-code, and the actual software remains the explicit property of Bob Rye, İ 1988-1992 inclusive. ANY commercial distribution of this package without the prior written consent of the author (Bob Rye) is expressly prohibited. DISCLAIMER ŻŻŻŻŻŻŻŻŻŻ ALTHOUGH OUTSTANDING BUGS IN THE CODE HAVE BEEN ELIMINATED, THERE REMAINS THE POSSIBILITY OF UNFORESEEN PROBLEMS. WE RESERVE THE RIGHT TO REFUTE THE EXISTENCE OF SUCH 'BUGS', BUT IF FOUND, WE WILL ATTEMPT TO FIX SUCH PROBLEM(S). IF, HOWEVER, UNFORESEEN BUGS ARE FOUND TO CAUSE YOU MENTAL AND/OR PHYSICAL ANGUISH, THEN THAT IS AS THEY SAY IN THE CLASSICS, BAD LUCK! WE ACCEPT NO BLAME FOR ANY LOSS OR INCONVENIENCE FOUND TO ARISE FROM THE (MIS)USAGE OF THIS PROGRAM. WE RESERVE THE RIGHT TO WITHDRAW SUPPORT AND UPGRADES AT ANY TIME. WE PROBABLY WON'T DO THIS, BUT WE HAVE THIS RIGHT. ALL INSTANCES OF COMPANY AND/OR PRODUCT NAMES ARE (C), (R) AND (TM) RESPECTIVELY, WHERE APPLICABLE. "LogMan" ARE COPYRIGHT BOB RYE, 1988 - 1992 INCLUSIVE. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ LOGMAN is a little tool which keeps it's eye on your logfiles. If you're running a BBS, Foozle, or GCC (shame!) and/or Trapdoor, and you have multitudes of logfiles floating around your system, then LOGMAN is for you! If you're like me, and you run a little point with Foozle and Trapdoor, then you're likely to have a logfile entry for at least one of these great programs. The logfiles can be fairly useful, once in a while, and to BBS sysops, they can be VERY important. But what if you don't check your logfiles for some time, and like me, you stumble onto them out of the blue? The logfiles can be HUMONGOUS, WHOPPING or just *AMAZING*. You know the one I mean. The 3-month old "TRAPDOOR.LOG" in your MAIL:LOGS/ directory. The one that weighs 340 kilobytes... Anyhow, if you run a maintenance script at midnight, or lunch time or whenever, LOGMAN can slip right into your background activities without any need for checking by you. What you need to do is this. You need to check your logfiles, and you need to figure out what you want to do with them when they hit a certain size. For instance, I want my "TRAPDOOR.LOG" archived away in my DH1:BAK directory, under the name of "TDLOGS.LHA" every time the "TRAPDOOR.LOG" file hits 128000 bytes of size. The "TRAPDOOR.LOG" file is found in my MAIL:LOGS/ directory. I would then write a config file (by default titled "S:LOGMAN.cfg", case non-specific) and enter all of this information into it: ; ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ; ** This is the name of the logfile I want checked MAIL:LOGS/TRAPDOOR.LOG ; ** This is the size comparison that I want done (ie. 128000 bytes or bigger) >127999 ; ** Here are the action lines to be executed upon the above being TRUE lha -q a DH1:BAK/TDLOGS MAIL:LOGS/TRAPDOOR.LOG delete >nil: MAIL:LOGS/TRAPDOOR.LOG echo "Trapdoor's logfile is now under control!" echo "LOGMAN is GreetingWare!" ; When you're finished describing actions to LOGMAN, end with "#" # So, if my current "TRAPDOOR.LOG" is 126000 bytes in size, it wont be acted upon, during this pass. If you run Trapdoor later, and you get the busy signal for 39 minutes, and your TRAPDOOR.LOG file grows to 128334 bytes in size, LOGMAN will then act upon the TRAPDOOR.LOG actions when you later run LOGMAN. Usage for LOGMAN is as follows: 1> LOGMAN {logman-cfg-name} NOTE: You don't have to supply a cfg filename, as LOGMAN will first search for S:LOGMAN.cfg, although, if you DO specify a cfg filename, LOGMAN will attempt to use that cfg file instead. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ * The first "non-comment", and "non-blank" line must be the first logfile's name, including the full path structure! * The second such line must begin with a "<" or a ">" sign, which tells LOGMAN just which way to act, and straight after this sign, you must include your logfile-size preference. This works in this way: - you may specify that you want actions taken on the preferred logfile if the preferred logfile is SMALLER in size than the size that you have nominated, or; - you may specify that you want actions taken on the preferred logfile if the preferred logfile is LARGER in size than the size that you have nominated. * This means that in the example below, the actions will only be made if the file "vd0:trapdoor.log" is smaller than 40000 bytes. * Only one entry per line is allowed. * Also take care to include only one action per line. * You can have as many actions per logfile as you like, so long as each action line is a viable "executable" action line. That is, that the action can be used in an AmigaDOS scriptfile and executed without error. * You can stack more than one LOGFILE entry per cfg file. * The "#" character tells LOGMAN to stop taking/making actions based on the current logfile, and to continue with the next logfile, if one exists. vd0:trapdoor.log <40000 lha -q a ram:logs vd0:trapdoor.log delete >nil: vd0:trapdoor.log # * In this next example, the string "Hello! Look what happened" will be echoed to the screen only if the file "LOGS:tick.log" is LARGER than 10000 bytes. * The "#" character tells LOGMAN to stop taking/making actions based on the current logfile, and to continue with the next logfile, if one exists. LOGS:tick.log >10000 echo "Hello! Look what happened!" # ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ THINGS YOU MUST REMEMBER! 1. Comment lines and blank lines are allowed. A comment line is a line which starts (in column 1) with the ";" semi-colon character. A blank line is any line which ONLY contains a line-feed (the {return} key). 2. LOGNAME, SIZE, ACTION and END lines *must* start in column 1 of the config file. 3. I personally run LOGMAN in a script like this: ;;;;;;;;;;;;;;;;;; cd MAIL: LOGMAN if WARN quit 0 endif run foozle ;;;;;;;;;;;;;;;;;; If LOGMAN fails to execute correctly, it will return WARN. 4. LOGMAN is pure, re-entrant, and residentable. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Author contacts/bug reports etc. -------------------------------- Snail-Mail: BOB RYE 11 BEAVER STREET ST. ALBANS, VICTORIA AUSTRALIA, 3021 Bob's electronic mail addresses: Bob_Rye@guru.apana.org.au (preferred) 3:633/359.7@fido (preferred) 41:300/359.7@amiganet 42:8699/8.7@trinet bobrye@csource.oz.au CRAZY DIAMOND 3:633/359@fido Phone: [Intl. +61 3 5698873] [National 03 5698873] up to 14.4k SysOp: Chris Quonoey The latest PUBLIC version of LogMan will always be available on this BBS, in the Amiga files section.