[Top] | [Contents] | [Index] | [ ? ] |
1. An Overview of HTICK What is HTICK? 2. Installation Procedures and Release Notes Installation. Read this! 3. HTICK 1.1.0 Command Line OPTIONS and SWITCHES Command Line OPTIONS and SWITCHES 4. HTICK 1.1.0 Configuration Reference Explanation of the configuration file. 2.3 Support Support information. A. Configuration File Keyword Index Configuration File Keywords Index
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
HTICK is a Fidonet file areas tosser with filefix. Now project is supported by Husky Development Team (see http://husk.sf.net/team.html).
HTICK features:
The advantages of HTICK are:
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
I suppose, that you already has compiled binaries. If not - read "Download" or "Compile the Source Code" chapters.
tparser
from FIDOCONFIG package to test your config
(read about PublicGroup
or AccessGrp
if you want to use
groups for FileEchoAreas
)
2.1 Download the Source Code & Binary Files 2.2 Compiling the Source Code How to compile the source code 2.3 Support Support, Contacting the Author, Reporting Bugs, Contributing Code
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
1. The smapi and fidoconf packages are required for htick.
2. Put the fidoconfig and smapi packages to the directory where the other packages of fido linux reside:
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:
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
There are numerous reasons why you might wish to establish contact with developers.
FIDOSOFT.HUSKY
RU.HUSKY
If you have access to Internet, you may of course post your support request or bug report into form on husky development site: http://sourceforge.net/projects/husky, click to "Bugs" link if you have post bug report.
If you do not have access to any of these echos and internet, you may of course also contact developers via netmail or e-mail at the addresses listed below.
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 autors at the addresses
below. Please attach log-file with loglevels 1-0A-Za-z
(all numbers
and letters).
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:
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
htick [options] <command>
<command>
is:
command
from command line
@BBS
@DIZ
@<file>
@@BBS
@@DIZ
@@<file>
<file>
filename for write output to.
<dirlist>
list of paths to files from filelist.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
HTICK is based on FIDOCONFIG library, so read documentation of FIDOCONFIG about location of config file and keywords ideology.
4.1 Keywords This chapter describes keywords 4.2 Link Keywords Keywords that can be repeated for different links 4.3 FileArea Definition FileAreas definition 4.4 Announce System Announces definition
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
4.1.1 FileAreaBaseDir Base directory for FileAreas. 4.1.2 PassFileAreaDir In this directory shall be put files from Passthrough File areas. 4.1.3 FileDescPos Indent position for long descriptions in FILES.BSS. 4.1.4 fileLDescString Prefix string for long descriptions in FILES.BBS. 4.1.5 FileFixHelp Help file for FileFix. 4.3.1 FileArea File area definition. 4.1.6 ExecOnFile Execute some command on receiving file. 4.1.7 SaveTic Save files with tics 4.1.8 MaxTicLineLength Set maximum line length in outgoing TICs to number. 4.1.9 BusyFileDir Where shall be put TICs for busy links 4.1.10 ConvertLongNames What to do with long names when toss or hatch. 4.1.11 ConvertShortNames What to do with short names when toss or hatch. 4.1.12 addDLC Add Download counters to FILES.BBS. 4.1.13 DLCDigits How much digits DLC must be. 4.1.14 ticOutbound TICs are stored here and killed after transmission 4.1.15 filefixKillRequests Kill filefix request after processing. 4.1.16 filefixReportsAttr Set kill/sent flag to filefix replies. 4.1.17 BBSarea File area without subscribing (for `htick filelist`). 4.1.18 fileDescName If no LDESC defined in tic file, use <name> file from archive fill it. 4.1.20 FileAreaCreatePerms Set permissions for newly created filearea directories 4.1.21 FileFixFromName Originator name in filefix replies. 4.1.22 AutoFileCreateFlag Create flag when filearea has been autocreated. 4.1.23 FileFixNames Set of names on which FileFix will respond.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
FileAreaBaseDir <directory>
FileAreaBaseDir /var/spool/fido/fileareas
Where the directories for all Fileareas shall be made at autocreate. Same as MsgBaseDir.
This statement cannot be repeated.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
PassFileAreaDir <directory>
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.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
FileDescPos <number>
FileDescPos 13
The number of spaces to indent long descriptions in FILES.BBS. Recommend: 13 (8.3+space)
This statement cannot be repeated.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
fileLDescString <string>
fileLDescString ">"
This string is put before long descriptions in FILES.BBS (Usually ">" or "+".). Default value: single space.
This statement cannot be repeated.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
FileFixHelp <string>
FileFixHelp /usr/local/fido/filefix.hlp
Help file for FileFix, same as AreaFixHelp for HPT's AreaFix
This statement cannot be repeated.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
ExecOnFile <filearea> <filemask> <command>
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.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
SaveTic <FileEchoMask> <FileOption> <DirToSaveTic>
ExecOnFile husky -l /usr/local/husky
Options `-l' and `-c' work only for non-Passthrough file echos
This statement cannot be repeated.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
MaxTicLineLength <number>
MaxTicLineLength 79
Set maximum line length in outgoing TICs to number.
This statement cannot be repeated.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
BusyFileDir <directory>
BusyFileDir /var/spool/fido/htick.busy/
Where shall be put TICs for busy links (default <outbound>/busy.htk).
This statement cannot be repeated.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
ConvertLongNames <Upper|Lower|DontTouch>
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.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
ConvertShortNames <Upper|Lower|DontTouch>
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.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
addDLC <bool>
addDLC yes
Add Download counters ([000]) to files.bbs. Use with DLCDigits only!
This statement cannot be repeated.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
DLCDigits <number>
DLCDigits 4
How much digits DLC must be. DLC has [000] form.
This statement cannot be repeated.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
ticOutbound <directory>
ticOutbound /var/spool/fido/ticOub
TICs are stored here and killed after transmission. Default: use PassFileAreaDir value
This statement cannot be repeated.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
filefixKillRequests <bool>
filefixKillRequests yes
Kill filefix request after processing.
This statement cannot be repeated.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
filefixReportsAttr <attr>
filefixReportsAttr pvt,kill,loc
Set flags to filefix replies.
Valid attributes are:
Default is "pvt loc k/s npd".
This statement cannot be repeated.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
BBSarea <name> <bbsareapath>
bbsarea bbs /var/spool/fido/bbsareas/bbs
File area without subscribing, not shown in filefix reports. Use for filelist generation only (`htick filelist` command).
This statement cannot be repeated.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
fileDescName <name>
fileDescName file_id.diz
If LDESC is not defined in tic file, use <name> file from archive to fill it (usually file_id.diz).
This statement cannot be repeated.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
unpack
action should be defined for archive and contain `$f' parameter
(`$f' is replaced with file name while unpacking).
Examples:
Unpack "/path/to/unrar e -y -c- -o+ -inul $a $p $f" 0 52617221 # *.rar Unpack "d:\path\unrar e -y -c- -o+ -inul $a $p $f" 28 52534658 # rar-sfx/DOS Unpack "\path\pkzipc -ext -dir=none -over=all -nozip -silent $a $p $f" 0 504b0304 Unpack "unzip -joLqq $a -d $p" 0 504b0304 Unpack "pkunzip -njCL $a -d $p $f" 0 504b0304 Unpack "pkzip25 -ext -silent -over=all -nofix -nozip $a $p $f" 0 |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
FileAreaCreatePerms <mode>
FileAreaCreatePerms 644
Define permissions for newly created filearea directories (UNIX only)
This statement cannot be repeated.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
FileFixFromName <string>
FileFixFromName <string>
Originator name in filefix replies.
This statement cannot be repeated.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
AutoFileCreateFlag <file>
AutoFileCreateFlag /usr/local/fido/flags/new_filearea
Create flag when filearea has been autocreated.
This statement cannot be repeated.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
FileFixNames <string>
FileFixNames allfix filefix htick
Set of names separated by space on which FileFix will respond
This statement cannot be repeated.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
(off) or /files/gfd/app/edit (on).
4.2.1 fileEchoFlavour This statement sets the flavour which outgoing files in fileechos for this linkget. 4.2.2 fileAreaDefaults Set defaults for filearea definitions that follow. 4.2.3 RemoteFileRobotName Name of remote filefix robot (need for FileForwardRequest). 4.2.16 FileFixEchoLimit Area subscription limit. 4.2.4 noTIC Disable TIC file creation. 4.2.5 autoFileCreate Allow or deny autocreating fileechoes received from this link. 4.2.6 AutoFileCreateFile Specifies the file new filearea will be placed into 4.2.7 AutoFileCreateDefaults Specifies the new filearea defaults. 4.2.8 AutoFileCreateSubdirs Whether to autocreate areas like /fils/gfd.app.edit
4.2.9 delNotReceivedTIC If file not received, then remove TIC. 4.2.10 FileFixFSC87Subset This boolean switch will change on a per link basis how TIC files are processed. 4.2.11 TickerPackToBox If link has file box - toss files and tics there. 4.2.12 LinkFileBaseDir Where autocreated fileareas will be placed. 4.2.13 ForwardFileRequests Allow file areas subscribe requests forward to link 4.2.14 ForwardFilePriority Priority in uplinks order for filearea subscribing forward-requests. 4.2.15 ForwardFileRequestFile List of available fileareas from this link. 4.2.16 FileFixEchoLimit Area subscribe limit.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
fileEchoFlavour <hold|normal|crash|direct|immediate>
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.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
fileAreaDefaults <options> [links]
fileAreaDefaults -lw 100 -g Z 2:5097/31.1
Set defaults for filearea definitions that follow. All options are possible,
except areatag and path.
Settings in the filearea definition override fileAreaDefaults
See also @xref{echoAreaDefaults,,,hpt}. Defaults are switched off
with empty fileAreaDefaults
.
This statement can only be repeated for different links.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
RemoteFileRobotName <name>
RemoteFileRobotName allfix
Name of remote filefix robot (needed for FileForwardRequest)
This statement can only be repeated for different links.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
noTIC <bool>
noTIC yes
Disable TIC File Creation
This statement can only be repeated for different links.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
autoFileCreate <on|off>
autoFileCreate on
Allow or deny autocreating fileechoes received from this link.
This statement can only be repeated for different links.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
AutoFileCreateFile <file>
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.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
AutoFileCreateDefaults <string>
AutoFileCreateDefaults -lw 100 -g Z
Specifies the new filearea defaults.
This statement can only be repeated for different links.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
AutoFileCreateSubdirs <on|off>
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.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
delNotReceivedTIC <on|off>
delNotReceivedTIC on
Remove TIC if file was not received
This statement can only be repeated for different links.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
FileFixFSC87Subset <on|off>
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.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
TickerPackToBox <on|off>
TickerPackToBox on
If link has file box - toss files and tics there
This statement can only be repeated for different links.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
LinkFileBaseDir <directory>
LinkFileBaseDir /usr/local/fido/fileareas/2.5097.64.0
Where autocreated fileareas will be placed to (may be "passthrough")
This statement can only be repeated for different links.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
ForwardFileRequests <on|off>
ForwardFileRequests on
Allow fileareas forward-requests to this link.
This statement can only be repeated for different links.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
ForwardFilePriority <number>
ForwardFileRequests 1
Priority in uplinks order for filearea subscribing forward-requests
This statement can only be repeated for different links.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
ForwardFileRequestFile <file>
ForwardFileRequestFile /usr/local/fido/hpt/uplink1.lst
List of available fileareas from this link
This statement can only be repeated for different links.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
FileFixEchoLimit <number>
FileFixEchoLimit 10
Area subscribe limit (max fileareas number this link is allowed to subscribe to)
This statement can only be repeated for different links.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
4.3.1 FileArea definition of FileArea
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
FileArea <name> <fileareapath> [options] <uplink> <downlinks>
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:
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Htick announcements are selective, they can be different for different
fileareas.
Token AnnAreaTag
starts a new section of announce definition,
other tokens define lists of fileareas included into announcement
and describe announce message.
To post announcements run htick announce
.
You may turn announcements off: just remove AnnounceSpool
definition from config.
4.4.1 AnnounceSpool Directory for accumulating report information. 4.4.2 AnnAreaTag Name of area of file where annouce will be placed. 4.4.3 AnnInclude Array of fileecho masks that will be announced in this annAreaTag. 4.4.4 AnnExclude Array of filearea masks that won't be announced in this annAreaTag. 4.4.5 AnnTo Announce message destination name. 4.4.6 AnnFrom Announce message originator name. 4.4.7 AnnSubj Announce message subject. 4.4.8 AnnAddrTo Announce message destination address (use for netmail area only) 4.4.9 AnnAddrFrom Announce message originate address. 4.4.10 AnnOrigin Origin line in announce message. 4.4.11 AnnMessFlags Announce message attributes (k/s loc hld ...). 4.4.12 AnnFileRFrom Show in announcement: address of system which file received from 4.4.13 AnnFileOrigin Show in announce: address of system who hatched file. 4.4.14 Announcements example Example for understanding announces (from real config)
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
AnnounceSpool <path>
AnnounceSpool /var/spool/fido/announce
Directory for accumulating report information.
This statement cannot be repeated.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
AnnAreaTag <AREATAG|@filename>
AnnounceSpool local.announce
Begins new announce definition section. <AREATAG> is name of an area where annoucement will be placed to <@filename> is filename with leading '@' where annoucement will be placed to.
This statement can be repeated.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
AnnInclude <fileecho mask list>
AnnInclude *
Array of fileecho names|masks that will be announced in this annAreaTag. Default: all fileareas.
This statement can be repeated only for different AnnAreaTag.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
AnnExclude <fileecho mask list>
AnnExclude aftnged
Array of filearea names|masks that won't be announced in this annAreaTag
This statement can be repeated only for different AnnAreaTag.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
AnnTo <string>
AnnTo All
Announce message destination name.
This statement can be repeated only for different AnnAreaTag.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
AnnFrom <string>
AnnFrom Announce Robot
Announce message originator name.
This statement can be repeated only for different AnnAreaTag.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
AnnSubj <string>
AnnSubj New files arrived
Announce message subject.
This statement can be repeated only for different AnnAreaTag.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
AnnAddrTo <address>
AnnAddrTo 2:5097/31.1
Announce message destination address (use for netmail area).
This statement can be repeated only for different AnnAreaTag.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
AnnAddrFrom <address>
AnnAddrFrom 2:5097/31
Announce message originate address.
This statement can be repeated only for different AnnAreaTag.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
AnnOrigin <string>
AnnOrigin News files!
Origin line in announce message
This statement can be repeated only for different AnnAreaTag.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
AnnMessFlags <string>
AnnMessFlags loc hld
Announce message flags (k/s loc hld ...)
This statement can be repeated only for different AnnAreaTag.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
AnnFileRFrom <on|off>
AnnFileRFrom on
Show in announce: address of system which file is received from
This statement can be repeated only for different AnnAreaTag.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
AnnFileOrigin <on|off>
AnnFileOrigin on
Show in announce: address of system that hatched file
This statement can be repeated only for different AnnAreaTag.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The following text is taken from a real config file.
#= Announcements definitions ===================================== AnnounceSpool E:\FIDO\EXCH\report # report all arrived files to file e:\fido\rep.txt AnnAreaTag @e:\fido\rep.txt AnnFileOrigin on # report into area 'seumbieky.news' # files posted to 'union.*' group of fileechos AnnAreaTag seumbieky.news AnnInclude union.* AnnSubj New mp3's arrives AnnTo United mp3 fans AnnFrom Fullfeed Distribution Site AnnOrigin *** seumbieky forever *** AnnFileOrigin on AnnFileRfrom on # report 'uue.*' group of fileechos into area 'seumbieky.news' AnnAreaTag seumbieky.news AnnInclude uue.* # report into area 'seumbieky.news' # all other exept of 'uue.* and union.*' groups AnnAreaTag seumbieky.news AnnExclude uue.* union.* # report via netmail to defined address AnnAreaTag netmail AnnInclude union.* AnnSubj New mp3's arrives AnnTo Max Inda Houze Annaddrto 2:464/108 AnnFrom Fullfeed Distribution Site Annaddrfrom 2:464/910.108 AnnOrigin *** seumbieky forever *** AnnMessFlags k/s loc hld AnnFileOrigin on AnnFileRfrom on #= Announces definitions ends ================================ |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Jump to: | A B C D E F L M N P R S T |
---|
Jump to: | A B C D E F L M N P R S T |
---|
[Top] | [Contents] | [Index] | [ ? ] |
[Top] | [Contents] | [Index] | [ ? ] |
1. An Overview of HTICK
2. Installation Procedures and Release Notes
3. HTICK 1.1.0 Command Line OPTIONS and SWITCHES
4. HTICK 1.1.0 Configuration Reference
A. Configuration File Keyword Index
[Top] | [Contents] | [Index] | [ ? ] |
Button | Name | Go to | From 1.2.3 go to |
---|---|---|---|
[ < ] | Back | previous section in reading order | 1.2.2 |
[ > ] | Forward | next section in reading order | 1.2.4 |
[ << ] | FastBack | previous or up-and-previous section | 1.1 |
[ Up ] | Up | up section | 1.2 |
[ >> ] | FastForward | next or up-and-next section | 1.3 |
[Top] | Top | cover (top) of document | |
[Contents] | Contents | table of contents | |
[Index] | Index | concept index | |
[ ? ] | About | this page |