home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ARM Club 3
/
TheARMClub_PDCD3.iso
/
hensa
/
internet
/
fidomail_1
/
!FidoMail
/
Dox
/
Variables
< prev
next >
Wrap
Text File
|
1994-02-19
|
6KB
|
129 lines
FidoMail variables
------------------
There's some things for you to alter here too, if you wish to customise
FidoMail at a low level. All major filenames and directories can be reset to
point anywhere reasonable.
By default, the variables are set in the '!SetVars' file, which usually resides
in the 'Config' directory:
SetEval FM%LogLevel 100
Set FM$Inbound$Dir <Inbound><FM$Postfix>
Set FM$Outbound$Dir <Outbound><FM$Postfix>
Set FM$CurDomain$Dir <FM$Domains$Dir>.<FM$Domain>
Set FM$MsgBase$File <FM$CurDomain$Dir>.Msgs.Heap
Set FM$FSMap$File <FM$CurDomain$Dir>.Msgs.FSMap
Set FM$AreaLinks$File <FM$CurDomain$Dir>.Msgs.AreaLinks
Set FM$BaseState$File <FM$CurDomain$Dir>.Msgs.BaseState
Set FM$FileLists$Dir <FM$CurDomain$Dir>.FileLists
Set FM$AreaMap$File <FM$CurDomain$Dir>.Misc.AreaMap
Set FM$OrigAreas$File <FM$CurDomain$Dir>.Misc.OrigAreas
Set FM$Book$File <FM$CurDomain$Dir>.Misc.!AddrBook
Set FM$Sig$File <FM$CurDomain$Dir>.Misc.sig
Set FM$Config$File <FidoMail$Dir>.Config.Main
Set FM$Limits$File <FidoMail$Dir>.Config.!Limits
Set FM$Log$File <FidoMail$Dir>.Log
And their meanings are:
FM%LogLevel (number) This variable controls how much information is put in
the logfile. See below for more details
FM$Inbound$Dir This var contains the name of the directory when the
inbound packets are to be found.
FM$Outbound$Dir This var says where to put the outbound packets.
FM$CurDomain$Dir This var is just used to set the next ones easier.
FM$MsgBase$File The filename of the messagebase file. See below for an
example of usage.
FM$FSMap$File The name of the msgbase freespace map.
FM$AreaLinks$File The name of the message-link file.
FM$BaseState$File The name a file describing the messagebase state.
FM$FileLists$Dir The name of a directory containing the filelists.
FM$AreaMap$File A map of your downlinks and which echos they get.
FM$OrigAreas$File A file for spotting when the areas changes.
FM$Book$File A file containing the address book.
FM$Sig$File Not used by FidoMail, but by the UUCP scanner, which I
haven't released yet.
FM$Config$File The name of the Config file.
FM$Limits$File The name of the limit file.
FM$Log$File The name of the logfile.
If you are running FidoMail from a floppy, it is a very good idea to place
the messagebase file on the ram-disc. Do this by changing this line in the
!Run file:
Set FM$MsgBase$File <FidoMail$Dir>.Msgs.Heap
to:
Set FM$MsgBase$File RAM:$.Heap
You could also make Copy commands in the !Run file to transfer the file
to/from ram automatically.
If you have space on the ram-disc for the Inbound directory, put it there too.
This will give a major speed increase when tossing. Remember to tell Binkley
about this too!
If you wish to experiment with moving the files about, you might want to know
something about what and when they are used.
The use of FM$Log$File depends on the loglevel, and if it is non-0, it will be
updated at many different times. 100 is normal, 1000 yields a lot of debugging
info. If it is 0 the file is still opened and closed, but no information is
output. If you want to get rid of the file altogether, set FM$Log$File to
"null:". The FM%LogLevel doesn't matter, then.
You can control whether the log file should be kept open, (which is faster,
especially on floppy) or closed when the program is running.
FM$Inbound$Dir is only used when tossing and unarcing.
FM$Outbound$Dir is used when file requesting, dispatching and scanning.
FM$MsgBase$File is used very often, and must be put at the fastest device you
can think of. It is usually also the largest one, so a harddisc is the most
obvious place to put it. If you want to make a backup of the messages, it is
vitally important that you copy _ALL_ the files in the Msgs directory or
wherever they might be (i.e. FM$MsgBase$File, FM$FSMap$File, FM$AreaLinks$File,
and FM$BaseState$File), treat them as a single item, and restore them together.
They point into each other, and if one of them gets 'out of sync' with the
others, _anything_ might happen!
If you lose one of them, the reaction depends on which one:
Losing the msgbase file obviously means that all the messages are lost. You
must delete the other files in that case.
Losing the Arealinks file will mean that you lose the information about where
to find the messages in the msgbase file. This is in effect the same as losing
the messages, but if some of them are really important, you will still be able
to cut them out of the msgbase file with an editor.
Losing the freespace map is not as fatal as it sounds. You will end up with a
msgbase file which is larger than actually needed, but you will still be able
to read the messages quite safely. If you know the FSMap file has been
corrupted, it is therefore safer to just delete it. When you've finished using
the larger-than-needed msgbase (and saved any important messages elsewhere),
delete the msgbase, arealinks and fsmap to start from scratch and regain the
lost disc space.
Losing the basestate currently isn't that important. When you start FidoMail
it will assume that the messages are sorted 'by area'. If you have specified
something else in the Config file, it will sort them at once after starting.
If you haven't, you might see some strange behaviour until you sort them
manually from the iconbar menu, so if you do this at once, everything will be
fine.
FM$FSMap$File is loaded at startup and saved when quitting. It is also saved
just before a toss to avoid running out of disc space afterwards. A tidy or
heapcheck operation will also save it.
FM$AreaLinks$File is loaded at startup and saved when quitting. This file is
also saved before tossing. If you have 'SafeHeap' turned on, both the FSMap and
the AreaLinks will be saved when major changes are made to them.
FM$BaseState$File is read at startup and written if you sort the message base
or change AKA.
FM$FileLists$Dir is checked for validity at startup and scanned when you
request a file or open the request submenu.
FM$AreaMap$File is read at startup and saved whenever it changes. This includes
when messages to AreaFix comes in, when you add or delete areas in the Config
file, and clicking 'Save' in the Area map window of course.
FM$OrigAreas$File is read and updated at startup.
FM$Config$File and FM$Limits$File are read at startup only.