OS/2 Shareware BBS: 2 BBS/02-BBS.zip/fan_240.zip/tickcfg.doc

Text File | 1992-10-27 | 12KB | 286 lines

 ;-=-=- An Abbreviated Operations Guide & Config for Tick v2.10 -=-=-
 ;  by Bill Whitehouse
 ; (1:323/109.1@fidonet)
 ; -=-=-=-=-=-=-=-=-=-=-
 ;
 ;      When the mailer here exits after accepting inbound files, it
 ; encounters the following line...
 ;
 ; If Exist D:\In\*.Tic TICK.EXE /cD:\Cfg\Tic.Cfg
 ;
 ;      ...which instructs Tick to move any .Tic-attached files and
 ; their accompanying descriptions to predefined directories. At the
 ; same time, Tick also spits out attaches for any defined downstream
 ; file links.
 ;
 ;      Hatch works much the same way, with the same config file,
 ; using the following command line syntax:
 ;
 ; Hatch.EXE /cD:\Path\Tic.Cfg /aAreaTag /f[D:\Path\]Fil2Send.Zip
 ;           [/xFileName] /r0 /dDescription text up to 80 chars.
 ;
 ;      Everything should appear on one line. The "/r0" tells Hatch
 ; to release the file immediately; "/r1" would instruct Hatch to
 ; release the file tomorrow, etc. If the file you are now hatching
 ; is intended to replace another - maybe older - file, designate the
 ; file it replaces (no drives, paths or wildcards allowed) with the
 ; "/x" switch.
 ;
 ;      ...or, with Hatch and the config file in the same directory,
 ; simply type HATCH, and the program will walk you through it.
 ;
 ;>>> TIC.CFG <<<
 ;-=-=-=-=-=-=-=-=-=-=-=-=-=- Addresses -=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 NET 234
 ;     ^Valid Net or a FakeNet address registered with your Zone
 ;     Coordinator. Required.
 NODE 567
 ;     ^Assigned Node address. Required. Tick does not support points.
 AKA 1:34567/8
 AKA 80:4567/8
 ;     ^Optional aka addresses are added to the Seenby list and
 ;     referenced below by ADDRESS line [An] FLAGS when designating
 ;     an AKA address rather than your primary address.
 ;
 ;-=-=-=-=-=-=-=-=-=-=-=- Required Path Names -=-=-=-=-=-=-=-=-=-=-=-
 ZONE 1 d:\out\
 ;    ^Primary outbound. First zone statement must point to your own
 ;    zone.
 ZONE 2 d:\out.002
 ZONE 3 d:\wherever
 ;    ^Declare a directory for each zone you plan to address.
 HOLD d:\hold-tic\
 ;    ^Outbound TICs & FLEs.
 IN d:\in\
 ;    ^Incoming files.
 MAIL d:\netmsg\
 ;    ^Netmail directory.
 QDIR d:\qdir
 ;    ^Pre-release quarantine directory.
 ;
 ;-=-=-=-=-=-=-=-=-=-=-=- Optional Path Names -=-=-=-=-=-=-=-=-=-=-=-
 TEMP d:\ramdisk
 ;    ^Work drive
 REPLACE [d:\oldfiles]
 ;    ^Copy over or move same-named files. Required if you want
 ;    replaced files moved to an "old files" directory. Moved and
 ;    replaced file entries are not removed from files.bbs descrip-
 ;    tion files. Yet.
 ;
 ;-=-=-=-=-=-=-=-=-=- Optional File Attach Methods -=-=-=-=-=-=-=-=-=-
 ; FLEA
 ;    ^.Fle attaches. default = .Tic
 ; FIDO
 ;    ^.Msg attaches. default = .Flo
 ; MailerKills
 ;    ^Tick generates a '#' flag by default, instructing your mailer
 ;    to truncate after sending and to delete altogether on the next
 ;    Tick run. 'MailerKills' produces a '^' flag telling your mailer
 ;    to delete it then and there.
 ;
 ;-=-=-=-=-=-=-=-=-=-=-=-=- Miscellaneous -=-=-=-=-=-=-=-=-=-=-=-=-=-
 TZ EST5EDT
 ;    ^Required timezone spec. This one is for the eastern time zone,
 ;    USA. Consult local listings.
 ; NoWait
 ;    ^Prevents HATCH from hanging a batch file on errors.
 ;
 ;-=-=-=-=-=-=- Optional 'BigDesc' Announcement Messages -=-=-=-=-=-=-
 ;    Designated text filenames (*.SDA *.WNT, *.PDN, say, or any other)
 ;    are snared on an area-by-area basis for description files and
 ;    posted as net or echomail messages while passing into the file
 ;    echo normally. Be advised that mail processors like Squish won't
 ;    toss .PKTs missing SEEN-BYs, so you may want to include the
 PktSeenBy
 ;    ^Keyword. And if you run a secure mail tosser, remember to grant
 ;    your own address access to 'BigDesc'-destined message areas.
 ;
 ; The next 4 keywords are GLOBAL, with no provision for area-by-area
 ; LOCAL definitions below.
 TO File Fiends
 ;    ^Default = All
 SYSOP Your Name
 ;    ^Default = Tick x.xx
 SUBJECT Detailed Upload Description
 ;    ^Default = FileName.Des
 ; `BigDesc' subject lines default to the first filename processed in
 ; that run. If an area not prescribed for 'BigDesc' is scanned first,
 ; none are processed.
 ORIGIN We're all bozos on this bus.
 ;    ^Default =  Lazy Sysop
 ;
 ;-=-=-=-=-=-=-=-=-=-=-  Optional Dupe Tracking -=-=-=-=-=-=-=-=-=-=-
 ; Enable dupe-tracking keywords here globally and/or area-by-area
 ; LOCAL-ly (below).
 ;
 STOPDUP d:\dupfiles\
 ;    ^Dupe file-tracking directory.
 CRC
 ;    ^Compute crc value (cyclical redundancy check) for each file to
 ;    insure its transfer integrity.
 Crc2Dup
 ;    ^Copy crc values to dupe files.
 ;
 ;-=-=-=-=-=-=-=-=-=-=- Optional System Logging -=-=-=-=-=-=-=-=-=-=-
 ; LogPath d:\path\system.log
 ; LogCRC
 ; LogSeen
 ; FDLog
 ;    ^Forces FrontDoor's logfile format.
 ; ListName Files.Bbs
 ;    ^Default description file name & path
 ; ListFmt %3:-13 %1
 ;    ^Default description line format. Consult the doc for its syntax.
 ;
 ;-=-=-=-=-=-=-=-=-=- Defining File Echo AREAS -=-=-=-=-=-=-=-=-=-=-=-
 ; Each file echo is defined by an AREA statement comparable to the
 ; AREAS.BBS format used by many message processing utilities. Include
 ; as many area statements as you have file echos. An AREA ends at the
 ; first line NOT in the area statement format, such as a blank line.
 ;
 ;-=-=-=-=-=-=-=-=-=- Tick Area Statement Format -=-=-=-=-=-=-=-=-=-=-
 ; AREA               Directory        EchoTag [EchoTag]
 ; LOCAL              KeyWord          Options
 ; Zone:Net/Node      Password         <FLAGS [*][&][F][C|H][T][An]>
 ;
 ; (examples below)
 ;-=-=-=-=-=-=-=-=-=-=-=-=-=- AREA Line -=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 ; The first line should consist of the keyword AREA, followed by the
 ; Directory, followed by an EchoTag of 8 characters or less (case-
 ; insensitive), with each field separated by blank space(s).
 ;
 ;-=-=-=-=-=-=-=-=-=-=- LOCAL Line(s) [Optional] -=-=-=-=-=-=-=-=-=-
 ; Lines beginning with the keyword "LOCAL" establish special treat-
 ; ment specific only to that area. If an area appears without a
 ; "LOCAL" definition, it defaults to the default or the format
 ; defined globally.
 ;
 LOCAL              ListName         d:\path\othrname.lst
 LOCAL              ListFmt          (desc. line format. consult doc.)
 ;
 LOCAL              BigDesc          *.??? MsgAreaTag [MsgAreaTag ...]
 ; Using "*" as a message AreaTag triggers a message to your netmail
 ; area. Echo to as many message areas as you want by adding
 ; additional tags.
 ;
 LOCAL              StopDup          d:\path\dupfile
 ; Enable merging of specified echo DUP files into one dupfile.
 ; CAUTION: If a DUP entry generated by echo A stops the same file
 ; from passing in echo B, you may prevent nodes who carry only B
 ; from getting it at all.
 ;
 LOCAL              DupByCRC
 LOCAL              NoDupByCRC
 ; Listed CRC values may no longer match reality if you strip comment
 ; headers from files. The command line switch "/OC" offers a workaround.
 ;
 ; Don't define global "CRC" in TIC.CFG. "/OC" tests the UNMODIFIED
 ; file's CRC against what is present in the TIC, renaming *.TIC to
 ; *.BAD if CRCs don't match. This feature only verifies the
 ; integrity of what you received. Nothing gets sent. Now strip files
 ; as you normally would and run Tick again WITHOUT the /OC switch.
 ; Tick will process normally, ignoring the CRC in inbound TICs.
 ; Outbound TICs will properly list the new CRC for the file as you
 ; are sending it. This will also work if you're inflicting your own
 ; silly headers on the world.
 ;
 LOCAL              NoReplace
 ; Want REPLACE active in MOST areas? Then put a REPLACE line above
 ; and add "LOCAL NoReplace" lines in those protected AREA blocks.
 ;
 LOCAL              Replace
 ; Want REPLACE active in only a FEW areas? Then ignore the REPLACE
 ; keyword and add "LOCAL REPLACE" lines to those unprotected AREA
 ; blocks. This method will not MOVE old files, though.
 ;
 LOCAL              Passthru
 ; PassThru area file attaches are created normally but associated
 ; FILES.BBS are NOT updated. Attaches are tested at each
 ; subsequent run and the file is deleted when Tick no longer finds
 ; an active attach.
 ;
 ;-=-=-=-=-=-=-=-=-=-=-=-=- ADDRESS Line(s) -=-=-=-==-=-=-=-=-=-=-=-
 ; Each AREA supports up to 100 ADDRESS lines and again, ADDRESS,
 ; PASSWORD and FLAG fields are separated by blank space(s).
 ;
 ; Node-specific passwords may total up to 8 (case-insensitive)
 ; characters. The defined node's TIC.CFG file must use the same
 ; password for your address.
 ;
 ; FLAGS [*][&][F][C|H][T][An] defining a node's send/receive status
 ; may appear in any order, upper or lower case, but they must all
 ; display as a single "word".
 ;
 ; "*" FLAGS accept files from the specified node. Without it, files
 ;           from that node are refused, but you may still send it
 ;           files.
 ;
 ; "&" FLAGS tell TICK and HATCH to ignore that node when sending files.
 ;
 ; "&" and "*" FLAGS combined consign that node to "accept-only" status.
 ;
 ; "&" without the "*" FLAG effectively comments out that node, without
 ;           ending the area.
 ;
 ; "C" and "H" FLAGS generate .CLO and .HLO files, respectively. Tick
 ;           defaults .FLO files.
 ;
 ; "C" and "H" FLAGS combined trigger a display warning and mark the
 ;           system HOLD. In FIDO mode, Tick sets the MSG Crash or Hold
 ;           bits accordingly. In the Non-Fido mode, Tick produces .FLO,
 ;           .CLO or .HLO attaches.
 ;
 ; "F" FLAGS instructs Hatch to send Flea-compatible files (.FLE
 ;           extension) instead of TIC files.
 ;
 ; "T" FLAGS send distributed files without associated .TIC attaches,
 ;           for those nodes with no interest in using Tick to pass
 ;           files downstream or in updating their file description
 ;           lists.
 ;
 ; "An" FLAGS designate an AKA address for file exchanges with the
 ;           declared node. The letter "A" is followed immediately by
 ;           a single hex number ranging from "0" to "F". "A0", for
 ;           instance, identifies you by the FIRST listed AKA address.
 ;
 ;-=-=-=-=-=-=-=-=-=-=- Area Statement Example: -=-=-=-=-=-=-=-=-=-=-
 AREA c:\file\softdist SOFTDIST
      LOCAL LISTNAME f:\farm\animal.bbs
      LOCAL LISTFMT %3:-12 Hello there %1
      LOCAL NoReplace
      LOCAL BigDesc *.MOO ARRIVALS *
      1:266/21 password C*
      2:261/662 hitom C*

 ; The example above creates an area with 2 listed nodes. The
 ; "files.bbs" for that area is named "animal.bbs", and written to
 ; the "f:\farm" directory. The description line format will display
 ; the filename in a left-justified 12-character field, followed by
 ; the constant text "Hello there", followed by the description text.
 ; Duplicate files are not replaced and all SOFTDIST files with the
 ; MOO extension are posted in both the ARRIVALS message area and
 ; your netmail area.

 AREA d:\psykotic PSYKOTIC
      LOCAL PassThru
      LOCAL NoDupByCRC
      LOCAL Stopdup Whiners
      1:2345/6 PassWord C*
      1:234/5 Dweeb &THA1

 ; This example is a passthru echo with DupByCRC turned off. Its Dup
 ; file is merged into Whiners.Dup and resides in the Dup directory
 ; indicated on the STOPDUP config line. Node 1:2345/6 is passworded
 ; with the word 'password', his mail is marked Crash and he's free
 ; to pass files into the echo. Mr. Dweeb, over at node 1:234/5, is
 ; not, though we'll consent to send him PSYKOTIC's files, passworded
 ; 'Dweeb' and placed on Hold, without a .Tic attach using the
 ; config's second-listed AKA address. Anything to please, right?-)
 ;
 ; For further description, please consult the doc.
 ;-=-=-=-=-=-=-=-=-=-=-=-=-=-=- The.End -=-=-=-=-=-=-=-=-=-=-=-=-=-=-

--- msgedsq 2.1
 * Origin: Art of the Possible - Providence, Rhode Island, US (1:323/109.1)