home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 2 BBS
/
02-BBS.zip
/
sqld100p.lzh
/
SQUALID.DOC
< prev
next >
Wrap
Text File
|
1993-01-24
|
39KB
|
1,281 lines
=================================
SQUALID V0.36b Reference Manual
24 January, 1993
=================================
Squalid is an Areafix replacement for SysOps who wish to dispense
with AREAS.BBS, and use only SQUISH.CFG for area definitions.
FEATURES/QUIRKS:
* zone grouping.
* intelligent request forwarding.
* does not require its own configuration file (uses Squish.Cfg).
* user defined aliases, i.e. "AreaFix", "EchoFix", "Jeeves".
* maintains 3-generation backup of Squish.Cfg.
* ADD, DELETE, CREATE and NOTIFY manual commands.
* subjectline Query, List and Help commands (-Q, -L and -H).
* support for %QUERY, %LIST, %HELP and %RESCAN in request
message.
* ADD + RESCAN for individual areas using area tag prefix (^) in
request message.
* 32 keys (A-Z,1-6) for highly configurable security.
* Wildcard "ALL" supported in request messages.
* Rescan achieved by generation of a batch file.
* Squish format netmail area supported.
Squalid serves no other purpose, and therefore it does not support
AREAS.BBS. Squalid supports fakenet points as normal nodes. Address
remapping must be performed externally (by Squish, for example).
SQUALID V0.36b Reference Manual Page 1
===========
QUICK START
===========
1 Edit SQUISH.CFG to include AT LEAST a User for each of your
downlinks, at least one group definition (Uplinks not
mandatory), and an Info (or BlockInfo) for each echo area that
you want secured. If you run a system where ALL echo areas are
freely available to ALL downlinks (in the appropriate group),
Info does not need to be specified. Also, if rescanning is
enabled, you must specify RescanFile and RescanCmd.
2 If you would like to see Squalid in action before committing
yourself to it, copy SQUISH.CFG to another file (perhaps
SQUALID.CTL), and use the command line option -cSQUALID.CTL so
that Squalid only modifies (and reads) the 'spare' file.
3 Edit your main batch file so that Squalid is called after
incoming mail has been unpacked into the netmail area. You may
need to add a pack command after the invocation of Squalid, so
that any mail created by Squalid is packed to be sent.
4 To let your down (and up) links know their current status, run
"Squalid NOTIFY * -aSDUSRMAN.DOC" (or "Squalid NOTIFY * -
cSQUALID.CTL -aSDUSRMAN.DOC" if you've followed step 2). This
will send a current status message to all links, and attach
the file SDUSRMAN.DOC, which is the Squalid end-user
instruction manual.
5 Other Squalid configuration items worth noting are Sysop,
Elist, Forward, RescanFile, RescanCmd, RescanLock, Query,
Header and Trailer.
The syntax for the Squalid command line is:
SQUALID <action> <modifiers> <parameters> <options>
<action> One of AUTO, NOTIFY, ADD, DELETE, CREATE
<modifiers> Action dependent. See individual actions for
details.
<parameters> Action dependent. See individual actions for
details.
<options> Zero or more of
-a<filespec>
-c<squishcfg>
-q<squalidcfg>
See below for details.
SQUALID V0.36b Reference Manual Page 2
========
ACTIONS:
========
AUTO Read netmail area and search for messages
addressed to "Squalid", or another alias as
defined in the configuration file. Equivalent to
Areafix EC.
Modifiers: -a, -p, -f, -l
No parameters.
NOTIFY Sends a list of all connected (and available)
areas to specified nodes. The same as the subject
line switch 'Q'.
Modifiers: none.
Parameters: <nodelist>
ADD Add the specified nodes to the specified echoes.
Modifiers: -m, -r
Parameters: <echolist> <nodelist>
DELETE Remove the specified node(s) from the specified
echo(es).
Modifiers: -m
Parameters: <echolist> <nodelist>
CREATE Create a new echo, and add the specified nodes to
it.
Modifiers: -m, -p, -f, -l
Parameters: <echotag> <nodelist>
SQUALID V0.36b Reference Manual Page 3
=======================================
OPTIONS (can be used for any <action>):
=======================================
-a<filespec> Create a file attach message to all specifed
nodes, attaching the file <filespec>. Multiple
fileattach messages may appear on the command
line, or you may specify
-c<squishcfg> Use the file <squishcfg> instead of either the
file specified by the SQUISH environment variable
or SQUISH.CFG in the current directory.
-q<squalidcfg> Get Squalid configuration items from the file
<squalidcfg> instead of from SQUISH.CFG. This is
simply an 'additional' file to the normal
configuration file, and items may appear in
either or both files. Squalid will never modify
this file, and any Info lines appropriate to
created areas will be put into the main
configuration file.
SQUALID V0.36b Reference Manual Page 4
==========
MODIFIERS:
==========
-n<netmail> Search only the specified area for messages to
Squalid. Squish format areas are specified by
preceding the path with a $. Only used by the
AUTO action.
-p<path> Use <path> as base for creating new areas. Must
be specified either on the command line or in the
configuration file (configuration item
CreatePath). Only used by the CREATE action.
-f<flags> Use <flags> when creating new areas. The flags
must follow immediately after the 'f', as shown
in the examples below. Multiple flags can be
specified by separating them with one or more
underscores. May be specified either on the
command line or in the configuration file
(configuration item AutoFlags). Used by the
CREATE action, and by the AUTO action if new
areas are created.
-l<locks> Use <locks> when creating new areas. May be
specified either on the command line or in the
configuration file (configuration item
CreateLocks). Used by the CREATE action, and by
the AUTO action if new areas are created. This
could also be used to force the group of the
area, by including @<group> as part of the lock
string, separated from any locks by an
underscore.
-m Create a netmail message informing the specified
nodes of any changes made. May be used with ADD,
DELETE, or CREATE actions.
-r Create a rescan batch file (default SDRESCAN.BAT)
for the areas and nodes given. May be used with
the ADD action only.
SQUALID V0.36b Reference Manual Page 5
===========
PARAMETERS:
===========
<nodelist> <nodelist> specifies one or more network
addresses, separated by spaces. The addresses
must be those of valid Users, as specified in the
configuration file. The wildcard character *
specifies all nodes that have been specified by
User statements.
<echotag> the echo tag used to identify a particular echo.
i.e.
MUFFIN
<echolist> specifies one or more <echotag>s, separated by
white space. The wildcard 'ALL' specifies all
echo areas with locks that may be opened by the
specified node(s) keys. i.e.
WORLDTLK TUB MUFFIN GREEN.029 GREEN_EC_O
ALL
The ADD and DELETE actions can use either, but not both of the
wildcards * and ALL. CREATE and NOTIFY can use the * wildcard
only.
SQUALID V0.36b Reference Manual Page 6
====================
BATCH FILE EXAMPLES:
====================
1. FrontDoor
:loop
fd
if errorlevel 100 goto incomingmail
:incomingmail
squish in out squash link
squalid auto
if not exist sdrescan.bat goto loop
call sdrescan
del sdrescan.bat
goto loop
2. BinkleyTerm
:loop
bt unattended
if errorlevel 100 goto incomingmail
:incomingmail
squish in out squash link
squalid auto
if errorlevel 2 goto sendanswers
goto loop
:sendanswers
if not exist sdrescan.bat goto packit
call sdrescan
del sdrescan.bat
:packit
squish out squash
goto loop
SQUALID V0.36b Reference Manual Page 7
======================
COMMAND LINE EXAMPLES:
======================
Note that the command line syntax for Squalid is order-independent.
SQUALID CREATE BAROQUE -m -f-f_-p83:199/136 631/199
Will create the new echo area 'BAROQUE', using the flags '-f'
(*.msg format) and '-p83:199/136' (use 83:199/136 as alternate
primary address), and add the node 631/199 to the scan list. Send
a message to 631/199 informing per of the new area. The group for
'BAROQUE' will be automatically determined based on your primary
address.
SQUALID -r ADD 631/200 BAROQUE 631/201 -anewsweek.001
will add the nodes 631/200 and 631/201 to the area BAROQUE, and
send the file 'newsweek.001' to each of them. The messages in the
area will be rescanned to both nodes.
SQUALID 631/199 -m BAROQUE DELETE
will remove node 631/199 from the BAROQUE echo, and send a message
informing per of the change.
ERRORLEVELS
Exit errorlevels are bitmapped, for no particular reason at all.
The levels are:
0 Nothing happened
1 New message(s) addressed to Squalid were read
2 Message(s) were sent by Squalid
4 Request(s) were sent to uplink(s)
8 SQUISH.CFG was altered
128 A critical error occurred
The most likely errorlevels for SQUALID AUTO are in fact, 0, 3, 7,
11 or 15 (barring critical errors!).
SQUALID V0.36b Reference Manual Page 8
====================
Configuring Squalid.
====================
Squalid requires an ASCII plain text configuration file. This file
is searched for in the following manner: if the command line
option -c<configfile> is given, that file will be used; if the
SQUISH environment variable is present, the file that it specifies
will be used; otherwise "SQUISH.CFG" in the current directory will
be used. If the -q<squalidcfg> command line option is used, the
file specified will be read AFTER the other configuration file.
Squalid gets much of its information from existing Squish
configuration items, and additional configuration items specific
to Squalid are inserted in Squish.CFG (or may be put into a
separate file, with some limitations).
All Squalid configuration items begin with "App Squalid". This is
the recommended method for utilities to use the Squish.Cfg file.
The prefix is required in all cases, even when Squalid uses a
separate configuration file.
Echomail rescans are achieved by means of a batch file and echo
toss log file created when necessary by Squalid. Rescans should be
performed immediately but may be delayed until a regular
maintenance time by your main batch file.
SQUALID V0.36b Reference Manual Page 9
============================
Squalid Configuration Items:
============================
User <address> <password> [<keys>] [@<aka> ...] [#<user_name>]
The User keyword specifies all legitimate users of Squalid. A node
that does not have a User defined cannot use Squalid. The password
is the first word that must be specified on the subject line of
messages requesting service from Squalid. The keys specify the
security locks that the given user can 'open'. See Info for more
information on specifying keys (which are specified identically to
locks). If keys are not specifed, and the Info keyword is not
used, an unsecure system can get by with just this keyword for
each user. Alternative addresses for the user can be given
anywhere after the password, preceded by the commercial at
character ('@'). The name of the user can also be specified,
preceded by a hash ('#'), and with spaces replaced with
underscores. If specified, it will be used to address messages
normally sent to 'SysOp'.
App Squalid User 3:631/100 GRONK A-F @9:100/4 #Fred_Bloggs
specifies that the password for 3:631/100 (and 9:100/4) is
'GRONK', that the user's name is 'Fred Bloggs', and that Fred has
security keys A through to F. It also specifes that requests
coming from 9:100/4 will be treated in the same manner as those
from 3:631/100 (see "EndGroup" for an explanation of how this
works).
Any number of Users may be specified, up to the limit of available
memory.
Group <group tag> [*]
Begins the block that defines a group of zones that can be treated
as separate entities. The optional asterix signifies a default
group to be used when the group cannot be determined by other
means.
App Squalid Group FidoNet
Zones <zone> [<zone> ... ] (GROUP SPECIFIC)
The Zones keyword specifies the zones that are regarded as
belonging to the group currently being defined.
App Squalid Zones 1 2 3 4 5 6
would be a suitable statement for FidoNet. Multiple Zones
statements may appear for each group definition.
SQUALID V0.36b Reference Manual Page 10
AutoFlags <flags> (GROUP SPECIFIC)
Specifies the Squish flags (as per pp. 68-70, Squish V1.0
Reference Manual) to use when creating new areas. Multiple flags
should be separated by underscores. See also command line modifier
-f, which overrides this keyword. For example, to create areas
which are stored in squish format, and add 631/199 to the seen-
by's, use
App Squalid AutoFlags -$_-+631/199
AutoLocks <locks> (GROUP SPECIFIC)
The AutoLocks keyword specifies the locks to apply to new areas
created by Squalid. If this keyword is not specified, any new
areas created will not be secured. Overridden by the command line
modifier -l, if present. To give locks A,B,C,D,S,X,1,2,3 and 6 to
new areas, for example
App Squalid AutoLocks A-DSX1-36
See also Info for a detailed explanation of area locks and user
keys.
Elist <filespec> (GROUP SPECIFIC)
The Elist keyword specifies the name of an echo list file to be
sent in response to the -L subjectline switch, and with NOTIFY
messages (if IncludeList is set to "On").
App Squalid Elist F:\echolist\another.txt
Uplink <address> <req_pswd> <filespec> (GROUP SPECIFIC)
The Uplink keyword specifies an uplink for a particular zone.
Multiple uplinks may be specified. <req_pswd> is the password to
be used in forwarded area requests. <filespec> is the file to
search for echo tags to request. If an echo tag is not found in
any of the files specified for all uplinks, the response "area not
found" is returned to the requester.
App Squalid Uplink 3:631/530 freddie f:\echolist\another.txt
tells Squalid to search "F:\EchoList\Another.Txt" for currently
unknown echoes, and if found, to send a request to 3:631/530, with
password "freddie".
SQUALID V0.36b Reference Manual Page 11
EndGroup
EndGroup is an optional termination of a group definition. Group
definition terminates when either an EndGroup or a Group is
encountered. However, this seems an appropriate place to put a
complete group definition example!
App Squalid Group fidonet
App Squalid Zones 1 2 3 4 5 6
App Squalid AutoFlags -0
App Squalid AutoLocks S
App Squalid Elist F:\EList\FidoNet.Na
App Squalid Uplink 3:631/100 bosspass F:\EList\FidoHost.Eco
App Squalid Group rainbownet
App Squalid Zones 199
App Squalid AutoFlags -$_-p199:4242/8
App Squalid AutoLocks S
App Squalid Elist F:\EchoList\RainEcho.Lst
App Squalid Uplink 199:4242/1 not_telling F:\EList\REcho.Lst
App Squalid EndGroup
defines two groups, known (to Squalid only) as "fidonet" and
"rainbownet". Squalid will attempt to match the zone of any
address or AKA of a user to one of the zones specified in a Group
block. If this matching fails, the user has no access to any
facilities. If the matching succeeds, however, only those echoes
appropriate to the group of the user will be made available.
Requests may be made under any AKA for areas from another group,
and the appropriate address will be added to the scan list. For
instance, if the user with AKAs in both zone 199 and zone 3
requests an echo that is 'in' group rainbownet using per zone 3
address, Squalid will add the zone 199 AKA to the scan list, not
the zone 3 address.
Alias <alias> (default "Squalid")
The Alias keyword specifies a name for Squalid to respond to, in
addition to "Squalid". For example,
App Squalid Alias Areafix
is suggested. Any number of aliases may be specified, up to the
limit of available memory.
SQUALID V0.36b Reference Manual Page 12
CreatePath <path>
The CreatePath keyword specifies the path to use when creating new
areas. A new subdirectory (*.MSG) or file (Squish) with the name
SQLDnnnn, where nnnn is a number from 0001 to 9999, is created in
the directory specified. The combination
App Squalid CreatePath C:\Echo\Created
App Squalid Group ...
App Squalid AutoFlags -$
App Squalid AutoLocks A-F2-5
and the command
SQUALID CREATE COMP.SOURCES.C.LANG 632/300
will cause the lines
EchoArea COMP.SOURCES.C.LANG C:\Echo\Created\SQLD0001 -$ 632/300
App Squalid Info COMP.SOURCES.C.LANG A-F2-5
to be added to Squish.Cfg, and a set of Squish message files with
the base name "SQLD0001" to be created in the C:\Echo\Created
directory.
A trailing backslash character is optional for <path>.
Header <filespec>
The Header keyword specifies the name of a file that contains text
to be included at the beginning of each response message created
by Squalid. The file should be SHORT and to the point.
Trailer <filespec>
The Trailer keyword specifies the name of a file that contains
text to be included at the end of each response message created by
Squalid. The file should be SHORT and to the point.
HelpFile <filespec>
The HelpFile keyword specifies the name of a file that contains
help information for end-users of Squalid. SDUSRMAN.DOC (or ARJ,
or ZIP) is suggested. If the keyword is present, the specified
file is sent in response to the -H subject line switch.
HelpText <filespec>
The HelpText keyword specifies the name of a file that contains
help information for end-users of Squalid. If the keyword is
present, the contents of the specified file are sent AS A MESSAGE
in response to the -H subject line switch or the %HELP command.
This keyword overrides the HelpFile keyword. NOTE that the
combined length of Header, Trailer, HelpText and actual message
content cannot exceed 16K. Do try to keep it simple.
SQUALID V0.36b Reference Manual Page 13
IncludeList [Off|On] (default Off)
The IncludeList keyword specifies whether to respond to the -L
subjectline switch or the NOTIFY command line action by attaching
the file specified by Elist. If neither Off nor On is specified,
but the keyword is present, IncludeList is set to On.
;App Squalid IncludeList OFF ;Lists will NOT be sent
App Squalid IncludeList Off ;Lists will NOT be sent
App Squalid IncludeList ;Lists WILL be sent
App Squalid IncludeList On ;Lists WILL be sent
BlockInfo {<locks> | @<group>}
The BlockInfo keyword specifies locks and/or a group for all
EchoArea definitions following up to the next BlockInfo, or to a
BlockEnd, or to the end of the configuration file. It can be
overridden by the Info line for any echo areas within a block if
necessary.
App Squalid BlockInfo 2-4A-F
EchoArea CHIAPPI ....
EchoArea BERLIOZ ....
EchoArea DELIBES ....
EchoArea LISZT ....
App Squalid BlockEnd
[...]
App Squalid Info DELIBES G-K1-6
will give locks 2,3,4 and A through to F to area CHIAPPI, BERLIOZ
and LISZT, and locks G-K and 1-6 to DELIBES. Note that such an
override (DELIBES) would not be a normal usage of the BlockInfo
keyword.
See the Info keyword for details on locks and keys.
BlockEnd
See above.
Info <echotag> [<locks>] [@<group>]
The Info keyword is used for each echo area for which security is
desired, or for which a group that cannot be determined
automatically by the zone of the first listed node.
This keyword overrides BlockInfo, for the specified echo only.
Valid locks are A through to Z, and 1 to 6. A range of locks may
be specified by using the (-) symbol between the starting and
ending locks to be used (use "A-E" to specify keys A,B,C,D and E,
for example). When an area has locks specified, only users with
keys for ALL such locks can add or rescan that area. For example,
the key S could be used to indicate sysop, so that points can be
prevented from obtaining those echoes.
SQUALID V0.36b Reference Manual Page 14
Groups only need to be specified to override Squalid's automatic
group detection, for instance when the first listed node for an
echo does not have a zone that is defined in the appropriate Zone
statement for the desired group.
Examples...
App Squalid Info ZONE3_SYSOP S
gives lock 'S' to the echo area ZONE3_SYSOP, and
App Squalid Info STRANGEWAYS @fidonet
informs Squalid that the STRANGEWAYS echo belongs in the fidonet
group, no matter what the zone of the first listed node is.
Any number of Info keywords may be specified, up to the limit of
available memory.
Refer also to the Query, RescanLock, Forward and User keywords.
LogFile <filespec>
The LogFile keyword specifies the name of the log file for Squalid
to record its history. If no log file is specifed, no log
information will be written.
LogLevel <level> (default 1)
This keyword specifies the amount of information which is written
to the logfile, according to the importance attached to the
message. This is similar to the BinkleyTerm technique, and
identical to that used in Squish V1.01. Hey Scott, why didn't you
keep it consistent with Binkley? Allowable LogLevels are
0 !
1 !+
2 !+*
3 !+*-
4 !+*-#
5 !+*-#:
6 !+*-#:(space)
Log messages will only appear in the log file if the character
which precedes them is shown next to the active loglevel in the
list above.
Note that Squalid will use the Squish loglevel setting if it is
present, or will override it with its own if a specific Squalid
loglevel keyword is present.
LogLevel 6
App Squalid LogLevel 0
SQUALID V0.36b Reference Manual Page 15
will cause Squalid to only log messages that are preceded by a
`!', whereas
LogLevel 6
will cause Squalid to log all messages.
MaxLineLength <length> (default 2047)
The MaxLineLength keyword specifies the maximum length of EchoArea
definition lines written by Squalid in Squish.Cfg. Squalid will
override the specified length if it is unable to write the FIRST
node on any line, and reset it to the default. No minimum value is
specified, but be reasonable...if you have long pathnames please
allow a little room for addresses too! The maximum value for this
keyword is the default of 2047.
MsgFlag <flags>
The MsgFlag keyword specifies message attributes for messages
created by Squalid. You can specify the attributes Kill/Sent,
Crash, Hold and Private only. Each attribute must appear as a
single word on the MsgFlag line, separated by spaces. Only the
initial letter of each word is used, however, so you could use
App Squalid MsgFlag K C
to specify Kill/Sent and Crash, or you could write
App Squalid MsgFlag Kill/Sent Crash
if you wanted to make it a bit more obvious.
FileFlag <flags>
This is the same as the MsgFlag keyword, except Squalid uses it
when creating file attach messages.
App Squalid FileFlag Pri Hld
would cause file attaches to have the Private and Hold attributes.
MsgSize <size_in_kB>[K] (default 4194304K)
The MsgSize keyword specifies the maximum length of a message
created by Squalid. Messages which will exceed this length will be
split, with a 'Continued...' at the end of each part except the
last, and a '...from previous message.' at the beginning of each
except the first. On rare occasions a message will erroneously
have a 'Continued...' without a following message. The maximum
value for this keyword is the default of 4194304 (you might cop a
blast if you send a message this size!). The 'K' following the
number is optional.
App Squalid MsgSize 16K
SQUALID V0.36b Reference Manual Page 16
Sets the maximum size of messages created by Squalid to 16384
bytes.
NodeFormat Short|Brief|Long (default Short)
The NodeFormat keyword specifies the format of addresses written
by Squalid. 'Short' specifies the absolute minimum that Squish can
understand. 'Brief' prints zone:node/net for the first address,
minimal information for the rest. 'Long' prints zone:node/net for
all addresses.
Sort [On|Off] (default On)
The Sort keyword (if present) specifies whether to sort nodes into
ascending order of zone, net, node, point (with the exception of
the first listed node, which is never repositioned unless
deleted). If the keyword is not present, the scan list is sorted.
IncludePoints (default DISABLED)
If the IncludePoints keyword is encountered, points of the 'home'
address are included in the order in which they are encountered
(or in normal sort order) when a scan list is written. The
alternative situation is that points of the home node have a
separate line in SQUISH.CFG. The operation of Sort and
IncludePoints is demonstrated in the following example:
If we begin with an area 'GLUCK', specified:
EchoArea GLUCK C:\Echoes\Gluck -$ 631/100 1:639/240
EchoArea GLUCK C:\Echoes\Gluck -$ .2 .5 .7 .3 631/120
and a command 'SQUALID ADD .1 GLUCK', (all assuming that line
length is limited by MaxLineLength)
SQUALID V0.36b Reference Manual Page 17
1) App Squalid Sort Off
App Squalid IncludePoints
results in:
EchoArea GLUCK C:\Echoes\Gluck -$ 631/100 1:639/240
EchoArea GLUCK C:\Echoes\Gluck -$ .2 .5 .7 .3 631/120
EchoArea GLUCK C:\Echoes\Gluck -$ .1
2) App Squalid Sort Off
;App Squalid IncludePoints
results in:
EchoArea GLUCK C:\Echoes\Gluck -$ 631/100 1:639/240
EchoArea GLUCK C:\Echoes\Gluck -$ 631/120
EchoArea GLUCK C:\Echoes\Gluck -$ .2 .5 .7 .3 .1
3) App Squalid Sort On
App Squalid IncludePoints
results in:
EchoArea GLUCK C:\Echoes\Gluck -$ 631/100 120 632/376.1
EchoArea GLUCK C:\Echoes\Gluck -$ .2 .3 .5 .7 1:639/240
4) App Squalid Sort On
;App Squalid IncludePoints <== commented out
results in:
EchoArea GLUCK C:\Echoes\Gluck -$ 631/100 120 1:639/240
EchoArea GLUCK C:\Echoes\Gluck -$ .1 .2 .3 .5 .7
Sysop <sysop name> (default "SysOp")
The Sysop keyword specifies the name to be used when 'signing'
various response messages.
App Squalid Sysop Johann Pachelbel
will cause certain messages to be "signed" by Johann Pachelbel.
(see the separate document "How to Use Squalid" contained in
SDUSRMAN.DOC for examples of the messages concerned.)
Query <locks>
The Query keyword specifies the security level required to use the
-Q subject line switch. For example
App Squalid Query Q
means that a user must have key Q for Squalid to provide a query
report.
SQUALID V0.36b Reference Manual Page 18
Forward <locks>
The Forward keyword specifies the security level required by a
user before Squalid will generate forward requests for that node.
For example
App Squalid Forward F
means that a user must have key F for Squalid to forward requests
that cannot be satisfied locally. If a user does not have the
requisite keys, no attempt is made to search for unknown areas.
NotifyInclude <locks>
This keyword specifies the keys required by a client for that
client to be included in a 'NOTIFY *' command. This would normally
be used to explicitly exclude a node from NOTIFY commands. Note
that without these keys, a client can NEVER be notified.
App Squalid NotifyInclude N
Means that clients without the N key will not be notified when the
SQUALID NOTIFY command is given.
RescanLock <locks>
The RescanLock keyword specifies the security level required to
rescan an echo area, either by the '^' prefix to an area, or by
the %RESCAN command. For instance
App Squalid RescanLock D-H4
means that a user must have keys D, E, F, G, H and 4 to rescan any
area.
RescanCmd <command line>
This specifies the command to place in SDRESCAN.BAT (or whatever
is specified in RescanFile) to generate a rescan for an area. If
RescanCmd is not specified, "SQUISH RESCAN" is the default. The
RescanCmd will be written to the RescanFile with the areaname and
address for each area to be rescanned. Examples:
App Squalid RescanCmd SQ386 RESCAN
or
App Squalid RescanCmd SQUISHP RESCAN
for OS/2.
SQUALID V0.36b Reference Manual Page 19
RescanFile
Specifies the name of the file to write RescanCmd to...
App Squalid RescanFile D:\BATCH\SDRESCAN.BAT
for DOS, or
App Squalid RescanFile SDRESCAN.CMD
for OS/2.
SaveRequests [Off|On] (default Off)
The SaveRequests keyword tells Squalid whether to save request
messages after processing. The default if SaveRequests is not
specified is to erase successfully processed requests. If
specified without "Off" or "On", defaults to On.
SaveSent [Off|On] (default Off)
Superceded by MsgFlag and FileFlag keywords.
KillPass [Off|On] (default On)
The KillPass keyword tells Squalid to remove a passthrough area
when the last downlink unlinks from it, and to send an unlink
message to the uplink.
SQUALID V0.36b Reference Manual Page 20