This is htick.info, produced by makeinfo version 4.8 from htick.texi. INFO-DIR-SECTION Fidonet Software START-INFO-DIR-ENTRY * HTICK: (htick). HTICK is fidonet fileecho processor END-INFO-DIR-ENTRY  File: htick.info, Node: Top, Next: Overview, Prev: (dir), Up: (dir) HTICK ***** This document describes HTICK 1.0, a Fidonet Fileecho Processor for OS/2, Windows, BeOS and Unix. * Menu: * Overview:: What is HTICK? * Installation:: Installation. _Read this!_ * Command Line:: Command Line OPTIONS and SWITCHES * Configuration Reference:: Explanation of the configuration file. * Support:: Support information. * Keyword Index:: Configuration File Keywords Index  File: htick.info, Node: Overview, Next: Installation, Prev: Top, Up: Top 1 An Overview of HTICK ********************** HTICK is a Fidonet file areas tosser with filefix. Now project supported by Husky Development Team. Features of HTICK: 1. tossing file areas 2. filefix (on the fly, from command line, limit for areas...) 3. autocreate on the fly 4. forward requests 5. posting to net & echo areas 6. pause and autopause for links 7. groups & levels for personal and public access to file areas 8. security check of tossgroup 9. dupe checking 10. link defaults 11. much, much more :) The advantages of HTICK are: 1. Open Source (GPL) 2. many supported platforms & operating systems 3. quick bug fixing  File: htick.info, Node: Installation, Next: Download, Prev: Overview, Up: Top 2 Installation Procedures and Release Notes ******************************************* This chapter provides you with information that is necessary to successfully install and use HTICK. I suppose, that you already has compiled binaries. If not - read "Download" or "Compile the Source Code" chapters. 1. Read FIDOCONFIG documentation about location of config-file 2. Edit config files for your purposes 3. Run `tparser' from FIDOCONFIG package to test your config (read about `PublicGroup' or `AccessGrp' if you want to use groups for `FileEchoAreas') 4. It is simply, isn't it? Enjoy! :-) * Menu: * Download:: Download the Source Code & Binary Files * Compiling:: How to compile the source code * Support:: Support, Contacting the Author, Reporting Bugs, Contributing Code  File: htick.info, Node: Download, Next: Compiling, Prev: Installation, Up: Installation 2.1 Download the Source Code & Binary Files =========================================== Main page (source code, win32 & os/2 releases) - `http://husky.sf.net/htick.html' Win32 bins (current, russian) - `http://hpt-bin.narod.ru'  File: htick.info, Node: Compiling, Next: Support, Prev: Download, Up: Installation 2.2 Compiling the Source Code ============================= 1. The smapi and fidoconf packages are required for htick. 2. Put the fidoconfig ans smapi packages to the directory where the other packages of fido linux reside: /usr/src/packages/ -> smapi/ -> htick/ -> fidoconfig/ 3. Compile and install smapi and fidoconf packages. Use "Makefile" for dynamic executables and makefile.lnx (or what you need) for static ones. 4. Compile and install HTICK: $ make $ make install You should use the _same_ makefiles in smapi, fidoconf and htick.  File: htick.info, Node: Support, Next: Command Line, Prev: Compiling, Up: Installation 2.3 Support =========== There are numerous reasons why you might wish to establish contact with developers. 1. You have decided to use HTICK on a regular basis. In this case, please do send a netmail at the address listed below. 2. You have a general questions on how to configure or on how to use a certain feature of HTICK. In other words, you need support. In this case, you'd best post your question to one of the following echos: `FIDOSOFT.HUSKY' The international Husky conference. English is the preferred language here. `RU.HUSKY' This Russian echo covers Husky Project. If you do not have access to any of these echos, you may of course also contact developers via netmail or e-mail at the addresses listed below. 3. You want to report a bug. There are two sorts of bugs: a. Normal bugs. You think that a certain function of HTICK does not work as expected, e.g. it is producing garbage, or doing strange things, or similar. In this case, either post to the echos listed above, or contact developers via netmail. Please do supply all information that is necessary to understand your problem. b. Fatal bugs. A fatal bug occurs if HTICK crashes. Depending on your operating system, the symptom might be a core dump, or a SYS 3175, or a general protection fault, or a system lockup, or a spontaneous reboot. I do consider a crash untolerable. No matter how stupid things you do, you should not be able to crash HTICK. If you are experienced user and get core dump, you can send developers gdb report. If you have a crash, locate `core' file that has been generated. Then run $ gdb htick core, type where. HTICK must be compiled with debug information (DEBUG=1 in `huskymak.cfg' file). Then send report to addresses below. If you are running any other binary version (like Windows), you will not get a core file on a crash. Write down as much information as you can, try to find a way to reproduce the crash and contact me at the addresses below. We need log-file with `loglevels 1-0A-Za-z'. 4. You want to contribute to HTICK. If you are a programmer and have fixed a problem in HTICK on your own, please submit your changes to me. The preferred way for doing so is to send to developers a difference file in GNU diff format (with -c parameter). Your work will be highly appreciated and honored in an appropriate place. If you want to regularly work on HTICK, we also have a CVS server online that you can have access to if you like. If you want to write a new feature for HTICK, please contact developers beforehand to avoid that we do duplicate work. Again, I will appreciate and honor any efforts done by you. Please note that for writing a HTICK enhancement, you should be familiar with C. Also, HTICK uses a special indentation style throughout the source code, that I would like you to adhere to. So here are developers addresses if you want to get in contact with us: * Fidonet: Max Chernogor @ 2:464/108 * e-mail: mche@ua.fm * Fidonet: Stas Degteff @ 2:5080/102.1 * e-mail: stas_degteff@users.sf.net  File: htick.info, Node: Command Line, Next: Configuration Reference, Prev: Support, Up: Top 3 HTICK 1.0 Command Line OPTIONS and SWITCHES ********************************************* To get help about the command line syntax, use HTICK without any arguments  File: htick.info, Node: Configuration Reference, Next: Keywords, Prev: Command Line, Up: Top 3.1 Configuration Reference =========================== 4 HTICK 1.0 Configuration Reference *********************************** HTICK is based on FIDOCONFIG library, so read documentation of FIDOCONFIG about location of config file and keywords ideology. * Menu: * Keywords:: This chapter describes keywords * Link Keywords:: Keywords, that can be repeated for different links * FileArea Definition:: FileAreas definition  File: htick.info, Node: Keywords, Next: FileAreaBaseDir, Prev: Configuration Reference, Up: Configuration Reference 4.1 Keywords ============ * Menu: * FileAreaBaseDir:: Base directory for FileAreas * PassFileAreaDir:: In this directory shall be put files from Passthrough File areas (and TICs, if not define ticOutbound). * FileDescPos:: The number of spaces to indent long descriptions in FILES.BSS. Recommend: 13 (8.3+space) * fileLDescString:: This string is put before long descriptions in FILES.BBS. (Usually ">" or "+".) Default value: single space. * FileFixHelp:: Help file for FileFix, same as AreaFixHelp for AreaFix * FileArea:: Same as EchoArea, most options are valid * ExecOnFile:: Execute some command on receiving file. Command get full filepath as parameter(space and file pathname to be append to command string before execution). * SaveTic:: Save files with tics * MaxTicLineLength:: Set maximum line length in outgoing TICs to number. * BusyFileDir:: Where shall be put TICs for busy links * ConvertLongNames:: What to do with long names when toss or hatch. * ConvertShortNames:: What to do with short names when toss or hatch. * addDLC:: Add Download counters to files.bbs. * DLCDigits:: How much digits DLC must be. DLC have [000] form. * ticOutbound:: TICs are stored here and killed after transmission * filefixKillReports:: Set kill/sent flag to filefix replies. * filefixKillRequests:: Kill filefix request after processing. * bbsarea:: File area without subscribing, not show in filefix reports. * fileDescName:: If no LDESC defined in tic file, use file from archive fill it (usuallyfile_id.diz). * FileAreaCreatePerms:: Define permissions for newly created filearea directories (UNIX only) * FileFixFromName:: Originator name in filefix replies. * AutoFileCreateFlag:: Create flag when filearea has been autocreated * FileFixNames:: Set of names separated by space on which FileFix will respond  File: htick.info, Node: FileAreaBaseDir, Next: PassFileAreaDir, Prev: Keywords, Up: Keywords 4.1.1 FileAreaBaseDir --------------------- Syntax: `FileAreaBaseDir ' Example: `FileAreaBaseDir /var/spool/fido/fileareas' Where the directories for all Fileareas shall be made at autocreate. Same as MsgBaseDir. This statement cannot be repeated.  File: htick.info, Node: PassFileAreaDir, Next: FileDescPos, Prev: FileAreaBaseDir, Up: Keywords 4.1.2 PassFileAreaDir --------------------- Syntax: `PassFileAreaDir ' Example: `PassFileAreaDir /var/spool/fido/transit' Where shall be put files from Passthrough File areas (and TICs, if ticOutbound is not defined). This statement cannot be repeated.  File: htick.info, Node: FileDescPos, Next: fileLDescString, Prev: PassFileAreaDir, Up: Keywords 4.1.3 FileDescPos ----------------- Syntax: `FileDescPos ' Example: `FileDescPos 13' The number of spaces to indent long descriptions in FILES.BBS. Recommend: 13 (8.3+space) This statement cannot be repeated.  File: htick.info, Node: fileLDescString, Next: FileFixHelp, Prev: FileDescPos, Up: Keywords 4.1.4 fileLDescString --------------------- Syntax: `fileLDescString ' Example: `fileLDescString ">"' This string is put before long descriptions in FILES.BBS (Usually ">" or "+".). Default value: single space. This statement cannot be repeated.  File: htick.info, Node: FileFixHelp, Next: ExecOnFile, Prev: fileLDescString, Up: Keywords 4.1.5 FileFixHelp ----------------- Syntax: `FileFixHelp ' Example: `FileFixHelp /usr/local/fido/filefix.hlp' Help file for FileFix, same as AreaFixHelp for AreaFix This statement cannot be repeated.  File: htick.info, Node: ExecOnFile, Next: SaveTic, Prev: FileFixHelp, Up: Keywords 4.1.6 ExecOnFile ---------------- Syntax: `ExecOnFile ' Example: `ExecOnFile husky *.diff /usr/local/fido/update_source.sh' Execute some command on receiving file. Command gets full filepath as parameter (space and file pathname should be appended to command string before execution). This statement cannot be repeated.  File: htick.info, Node: SaveTic, Next: MaxTicLineLength, Prev: ExecOnFile, Up: Keywords 4.1.7 SaveTic ------------- Syntax: `SaveTic ' Example: `ExecOnFile husky -l /usr/local/husky' where put TIC for fileecho[es] save files with tics. May be: empty files will not be copied `-l' link files from fileechodir to `-c' copy files from fileechodir to Options `-l' and `-c' work only for non-Passthrough file echos This statement cannot be repeated.  File: htick.info, Node: MaxTicLineLength, Next: BusyFileDir, Prev: SaveTic, Up: Keywords 4.1.8 MaxTicLineLength ---------------------- Syntax: `MaxTicLineLength ' Example: `MaxTicLineLength 79' Set maximum line length in outgoing TICs to number. This statement cannot be repeated.  File: htick.info, Node: BusyFileDir, Next: ConvertLongNames, Prev: MaxTicLineLength, Up: Keywords 4.1.9 BusyFileDir ----------------- Syntax: `BusyFileDir ' Example: `BusyFileDir /var/spool/fido/htick.busy/' Where shall be put TICs for busy links (default /busy.htk). This statement cannot be repeated.  File: htick.info, Node: ConvertLongNames, Next: ConvertShortNames, Prev: BusyFileDir, Up: Keywords 4.1.10 ConvertLongNames ----------------------- Syntax: `ConvertLongNames ' Example: `ConvertLongNames DontTouch' What to do with long names when toss or hatch. Saying 'long name' we mean a mixed cased name or a name longer than 8.3 This statement cannot be repeated.  File: htick.info, Node: ConvertShortNames, Next: addDLC, Prev: ConvertLongNames, Up: Keywords 4.1.11 ConvertShortNames ------------------------ Syntax: `ConvertShortNames ' Example: `ConvertShortNames DontTouch' What to do with short names when toss or hatch. Saying 'short name' we mean a DOS-like name: 8.3, without mixed case. This statement cannot be repeated.  File: htick.info, Node: addDLC, Next: DLCDigits, Prev: ConvertShortNames, Up: Keywords 4.1.12 addDLC ------------- Syntax: `addDLC ' Example: `addDLC yes' Add Download counters ([000]) to files.bbs. Use with DLCDigits only! This statement cannot be repeated.  File: htick.info, Node: DLCDigits, Next: ticOutbound, Prev: addDLC, Up: Keywords 4.1.13 DLCDigits ---------------- Syntax: `DLCDigits ' Example: `DLCDigits 4' How much digits DLC must be. DLC has [000] form. This statement cannot be repeated.  File: htick.info, Node: ticOutbound, Next: filefixKillReports, Prev: DLCDigits, Up: Keywords 4.1.14 ticOutbound ------------------ Syntax: `ticOutbound ' Example: `ticOutbound /var/spool/fido/ticOub' TICs are stored here and killed after transmission. Default: use PassFileAreaDir value This statement cannot be repeated.  File: htick.info, Node: filefixKillReports, Next: filefixKillRequests, Prev: ticOutbound, Up: Keywords 4.1.15 filefixKillReports ------------------------- Syntax: `filefixKillReports ' Example: `filefixKillReports yes' Set kill/sent flag to filefix replies. This statement cannot be repeated.  File: htick.info, Node: filefixKillRequests, Next: bbsarea, Prev: filefixKillReports, Up: Keywords 4.1.16 filefixKillRequests -------------------------- Syntax: `filefixKillRequests ' Example: `filefixKillRequests yes' Kill filefix request after processing. This statement cannot be repeated.  File: htick.info, Node: bbsarea, Next: fileDescName, Prev: filefixKillRequests, Up: Keywords 4.1.17 bbsarea -------------- Syntax: `bbsarea ' Example: `bbsarea bbs /var/spool/fido/fileareas/bbsarea' File area without subscribing, not shown in filefix reports. Use for fileleist generation only ("htick filelist" command). This statement cannot be repeated.  File: htick.info, Node: fileDescName, Next: FileAreaCreatePerms, Prev: bbsarea, Up: Keywords 4.1.18 fileDescName ------------------- Syntax: `fileDescName ' Example: `fileDescName file_id.diz' If no LDESC defined in tic file, use file from archive fill it (usually file_id.diz). 'unpack' action should be defined for archive and contain `$f' parameter. This statement cannot be repeated.  File: htick.info, Node: FileAreaCreatePerms, Next: FileFixFromName, Prev: fileDescName, Up: Keywords 4.1.19 FileAreaCreatePerms -------------------------- Syntax: `FileAreaCreatePerms ' Example: `FileAreaCreatePerms 644' Define permissions for newly created filearea directories (UNIX only) This statement cannot be repeated.  File: htick.info, Node: FileFixFromName, Next: AutoFileCreateFlag, Prev: FileAreaCreatePerms, Up: Keywords 4.1.20 FileFixFromName ---------------------- Syntax: `FileFixFromName ' Example: `FileFixFromName ' Originator name in filefix replies. This statement cannot be repeated.  File: htick.info, Node: AutoFileCreateFlag, Next: FileFixNames, Prev: FileFixFromName, Up: Keywords 4.1.21 AutoFileCreateFlag ------------------------- Syntax: `AutoFileCreateFlag ' Example: `AutoFileCreateFlag /usr/local/fido/flags/new_filearea' Create flag when filearea has been autocreated. This statement cannot be repeated.  File: htick.info, Node: FileFixNames, Next: Link Keywords, Prev: AutoFileCreateFlag, Up: Keywords 4.1.22 FileFixNames ------------------- Syntax: `FileFixNames ' Example: `FileFixNames allfix filefix htick' Set of names separated by space on which FileFix will respond This statement cannot be repeated.  File: htick.info, Node: Link Keywords, Next: fileEchoFlavour, Prev: FileFixNames, Up: Configuration Reference 4.2 Link Keywords ================= * Menu: * fileEchoFlavour:: This statement sets the flavour which outgoing files in fileechos for this linkget. * fileAreaDefaults:: Set defaults for filearea definitions that follow. * RemoteFileRobotName:: Name of remote filefix robot (need for FileForwardRequest) * FileFixEchoLimit:: Area subscription limit * noTIC:: Disable TIC file creation * autoFileCreate:: Allow or deny autocreating fileechoes received from this link. * AutoFileCreateFile:: Specifies the file new filearea will be placed into * AutoFileCreateDefaults:: Specifies the new filearea defaults. * AutoFileCreateSubdirs:: Whether to autocreate areas like /filebase/gfd.app.edit (off) or /filebase/gfd/app/edit (on). * delNotRecievedTIC:: If file not received, then remove TIC * FileFixFSC87Subset:: This boolean switch will change on a per link basis how TIC files are processed. * TickerPackToBox:: If link has file box - toss files and tics there * LinkFileBaseDir:: Where autocreated fileareas will be placed * ForwardFileRequests:: Allow file areas subscribe requests forward to this link. * ForwardFilePriority:: Priority in uplinks order for filearea subscribing forward-requests * ForwardFileRequestFile:: List of available fileareas from this link * FileFixEchoLimit:: Area subscribe limit (max fileareas number allowed for this link subscribe)  File: htick.info, Node: fileEchoFlavour, Next: fileAreaDefaults, Prev: Link Keywords, Up: Link Keywords 4.2.1 fileEchoFlavour --------------------- Syntax: `fileEchoFlavour ' Example: `fileEchoFlavour direct' This statement sets the flavour which outgoing files in fileechos for this link get. For example set `fileEchoFlavour' to hold for points and to crash for uplinks. This statement can only be repeated for different links.  File: htick.info, Node: fileAreaDefaults, Next: RemoteFileRobotName, Prev: fileEchoFlavour, Up: Link Keywords 4.2.2 fileAreaDefaults ---------------------- Syntax: `fileAreaDefaults [links]' Example: `fileAreaDefaults -lw 100 -g Z 2:5097/31.1' Set defaults for filearea definitions that follow. All options are possible, Set defaults for filearea definitions that follow. All options are possible, except areatag and path. Settings in the filearea definition override `fileAreaDefaults' See also *Note echoAreaDefaults: (hpt)echoAreaDefaults. Defaults are switched off with empty `fileAreaDefaults'. This statement can only be repeated for different links.  File: htick.info, Node: RemoteFileRobotName, Next: noTIC, Prev: fileAreaDefaults, Up: Link Keywords 4.2.3 RemoteFileRobotName ------------------------- Syntax: `RemoteFileRobotName ' Example: `RemoteFileRobotName allfix' Name of remote filefix robot (need for FileForwardRequest) This statement can only be repeated for different links.  File: htick.info, Node: noTIC, Next: autoFileCreate, Prev: RemoteFileRobotName, Up: Link Keywords 4.2.4 noTIC ----------- Syntax: `noTIC ' Example: `noTIC yes' Disable TIC File Creation This statement can only be repeated for different links.  File: htick.info, Node: autoFileCreate, Next: AutoFileCreateFile, Prev: noTIC, Up: Link Keywords 4.2.5 autoFileCreate -------------------- Syntax: `autoFileCreate ' Example: `autoFileCreate on' Allow or deny autocreating fileechoes received from this link. This statement can only be repeated for different links.  File: htick.info, Node: AutoFileCreateFile, Next: AutoFileCreateDefaults, Prev: autoFileCreate, Up: Link Keywords 4.2.6 AutoFileCreateFile ------------------------ Syntax: `AutoFileCreateFile ' Example: `AutoFileCreateFile /usr/local/fido/hpt/config.filefix' Specifies the file new filearea definitions will be placed into This statement can only be repeated for different links.  File: htick.info, Node: AutoFileCreateDefaults, Next: AutoFileCreateSubdirs, Prev: AutoFileCreateFile, Up: Link Keywords 4.2.7 AutoFileCreateDefaults ---------------------------- Syntax: `AutoFileCreateDefaults ' Example: `AutoFileCreateDefaults -lw 100 -g Z' Specifies the new filearea defaults. This statement can only be repeated for different links.  File: htick.info, Node: AutoFileCreateSubdirs, Next: delNotRecievedTIC, Prev: AutoFileCreateDefaults, Up: Link Keywords 4.2.8 AutoFileCreateSubdirs --------------------------- Syntax: `AutoFileCreateSubdirs ' Example: `AutoFileCreateSubdirs on' Whether to autocreate areas like /filebase/gfd.app.edit (off) or /filebase/gfd/app/edit (on). If you want to configure this globally instead of on per-link basis, set this in the deflink section. For more information see 'AutoAreaCreateSubdirs' in the hpt manual. This statement can only be repeated for different links.  File: htick.info, Node: delNotRecievedTIC, Next: FileFixFSC87Subset, Prev: AutoFileCreateSubdirs, Up: Link Keywords 4.2.9 delNotRecievedTIC ----------------------- Syntax: `delNotRecievedTIC ' Example: `delNotRecievedTIC on' If file not received, then remove TIC This statement can only be repeated for different links.  File: htick.info, Node: FileFixFSC87Subset, Next: TickerPackToBox, Prev: delNotRecievedTIC, Up: Link Keywords 4.2.10 FileFixFSC87Subset ------------------------- Syntax: `FileFixFSC87Subset ' Example: `FileFixFSC87Subset on' This boolean switch will change on a per link basis how TIC files are processed. By default this switch is ON. htick will then operate only on FSC87-compliant keywords and ignore unknown keywords in the TIC file processed. If this switch is set to OFF all implemented keywords will be used which can (and, in interaction with some tick processors, WILL) lead to severe problems. Unknown keywords found in a TIC file will make htick stop processing that file. If you don't know what all this is about set FileFixFSC87Subset to ON for all your links. It won't hurt. This statement can only be repeated for different links.  File: htick.info, Node: TickerPackToBox, Next: LinkFileBaseDir, Prev: FileFixFSC87Subset, Up: Link Keywords 4.2.11 TickerPackToBox ---------------------- Syntax: `TickerPackToBox ' Example: `TickerPackToBox on' If link has file box - toss files and tics there This statement can only be repeated for different links.  File: htick.info, Node: LinkFileBaseDir, Next: ForwardFileRequests, Prev: TickerPackToBox, Up: Link Keywords 4.2.12 LinkFileBaseDir ---------------------- Syntax: `LinkFileBaseDir ' Example: `LinkFileBaseDir /usr/local/fido/fileareas/2.5097.64.0' Where autocreated fileareas will be placed (may be "passthrough") This statement can only be repeated for different links.  File: htick.info, Node: ForwardFileRequests, Next: ForwardFilePriority, Prev: LinkFileBaseDir, Up: Link Keywords 4.2.13 ForwardFileRequests -------------------------- Syntax: `ForwardFileRequests ' Example: `ForwardFileRequests on' Allow file areas subscribe requests forward to this link. This statement can only be repeated for different links.  File: htick.info, Node: ForwardFilePriority, Next: ForwardFileRequestFile, Prev: ForwardFileRequests, Up: Link Keywords 4.2.14 ForwardFilePriority -------------------------- Syntax: `ForwardFilePriority ' Example: `ForwardFilePriority 1' Priority in uplinks order for filearea subscribing forward-requests This statement can only be repeated for different links.  File: htick.info, Node: ForwardFileRequestFile, Next: FileFixEchoLimit, Prev: ForwardFilePriority, Up: Link Keywords 4.2.15 ForwardFileRequestFile ----------------------------- Syntax: `ForwardFileRequestFile ' Example: `ForwardFileRequestFile /usr/local/fido/hpt/uplink1.lst' List of available fileareas from this link This statement can only be repeated for different links.  File: htick.info, Node: FileFixEchoLimit, Next: FileArea Definition, Prev: ForwardFileRequestFile, Up: Link Keywords 4.2.16 FileFixEchoLimit ----------------------- Syntax: `FileFixEchoLimit ' Example: `FileFixEchoLimit 10' Area subscribe limit (max fileareas number this link is allowed to subscribe to) This statement can only be repeated for different links.  File: htick.info, Node: FileArea Definition, Next: FileArea, Prev: FileFixEchoLimit, Up: Configuration Reference 4.3 FileArea Definition ======================= * Menu: * FileArea:: definition of FileArea  File: htick.info, Node: FileArea, Next: Keyword Index, Prev: FileArea Definition, Up: FileArea Definition 4.3.1 FileArea -------------- Syntax: `FileArea [options] ' Example: `FileArea husky /var/spool/fido/fileareas/husky -a 2:5097/31 -p 28 -g Z -d "HUSKY fileecho" 2:5097/64 2:5097/303' Same as EchoArea, most options are valid: a) -a
Our own address b) -lr "Read level": Min link level for sending files from this filearea to this link. c) -lw "Write level": Min link level allowed to post into this filearea files received from link. d) -h Hide area (non visible in %LIST and in announce) e) -manual Disallow remote subscribe (disable subscribe areafix command). f) -mandatory Disallow remote unsubscribe (disable unsubscribe areafix command). g) -sendorig Set: send files from PassFileAreaDir for non passthrough areas. h) -nopause %PAUSE has no effect to this filearea j) -noCRC Disable CRC check for incoming files k) -g Group for this filearea l) -d "" Description for this filearea m) -noreplace Don't replace exisiting files in this filearea. n) -nodiz Do not try to get file description from (for packed files). o) -p Purge after n days. Setting to 0 to disables purging.  File: htick.info, Node: Keyword Index, Prev: FileArea, Up: Top Appendix A Configuration File Keyword Index ******************************************* [index] * Menu: * addDLC: addDLC. (line 6) * autoFileCreate: autoFileCreate. (line 6) * AutoFileCreateDefaults: AutoFileCreateDefaults. (line 6) * AutoFileCreateFile: AutoFileCreateFile. (line 6) * AutoFileCreateFlag: AutoFileCreateFlag. (line 6) * AutoFileCreateSubdirs: AutoFileCreateSubdirs. (line 6) * bbsarea: bbsarea. (line 6) * BusyFileDir: BusyFileDir. (line 6) * ConvertLongNames: ConvertLongNames. (line 6) * ConvertShortNames: ConvertShortNames. (line 6) * delNotRecievedTIC: delNotRecievedTIC. (line 6) * DLCDigits: DLCDigits. (line 6) * ExecOnFile: ExecOnFile. (line 6) * FileArea: FileArea. (line 6) * FileAreaBaseDir: FileAreaBaseDir. (line 6) * FileAreaCreatePerms: FileAreaCreatePerms. (line 6) * fileAreaDefaults: fileAreaDefaults. (line 6) * fileDescName: fileDescName. (line 6) * FileDescPos: FileDescPos. (line 6) * fileEchoFlavour: fileEchoFlavour. (line 6) * FileFixEchoLimit: FileFixEchoLimit. (line 6) * FileFixFromName: FileFixFromName. (line 6) * FileFixFSC87Subset: FileFixFSC87Subset. (line 6) * FileFixHelp: FileFixHelp. (line 6) * filefixKillReports: filefixKillReports. (line 6) * filefixKillRequests: filefixKillRequests. (line 6) * FileFixNames: FileFixNames. (line 6) * fileLDescString: fileLDescString. (line 6) * ForwardFilePriority: ForwardFilePriority. (line 6) * ForwardFileRequestFile: ForwardFileRequestFile. (line 6) * ForwardFileRequests: ForwardFileRequests. (line 6) * LinkFileBaseDir: LinkFileBaseDir. (line 6) * MaxTicLineLength: MaxTicLineLength. (line 6) * noTIC: noTIC. (line 6) * PassFileAreaDir: PassFileAreaDir. (line 6) * RemoteFileRobotName: RemoteFileRobotName. (line 6) * SaveTic: SaveTic. (line 6) * TickerPackToBox: TickerPackToBox. (line 6) * ticOutbound: ticOutbound. (line 6)  Tag Table: Node: Top214 Node: Overview773 Node: Installation1532 Node: Download2456 Node: Compiling2782 Node: Support3441 Node: Command Line6944 Node: Configuration Reference7212 Node: Keywords7780 Node: FileAreaBaseDir10045 Node: PassFileAreaDir10425 Node: FileDescPos10813 Node: fileLDescString11154 Node: FileFixHelp11529 Node: ExecOnFile11856 Node: SaveTic12319 Node: MaxTicLineLength12967 Node: BusyFileDir13284 Node: ConvertLongNames13636 Node: ConvertShortNames14055 Node: addDLC14472 Node: DLCDigits14765 Node: ticOutbound15044 Node: filefixKillReports15405 Node: filefixKillRequests15732 Node: bbsarea16059 Node: fileDescName16465 Node: FileAreaCreatePerms16894 Node: FileFixFromName17254 Node: AutoFileCreateFlag17577 Node: FileFixNames17941 Node: Link Keywords18281 Node: fileEchoFlavour19895 Node: fileAreaDefaults20390 Node: RemoteFileRobotName21086 Node: noTIC21457 Node: autoFileCreate21734 Node: AutoFileCreateFile22084 Node: AutoFileCreateDefaults22498 Node: AutoFileCreateSubdirs22888 Node: delNotRecievedTIC23491 Node: FileFixFSC87Subset23847 Node: TickerPackToBox24730 Node: LinkFileBaseDir25083 Node: ForwardFileRequests25492 Node: ForwardFilePriority25875 Node: ForwardFileRequestFile26274 Node: FileFixEchoLimit26685 Node: FileArea Definition27083 Node: FileArea27318 Node: Keyword Index28744  End Tag Table