rtsi.com/2014.01.www.rtsi.com.tar/www.rtsi.com/OS9/TOP/USR/MAN/mmon.prf

Text File | 2009-11-06 | 13KB | 501 lines

.he //MMon//
.fo //- # -//
.po 5
.rm 70
.ps 72
.m1 1
.m2 2
.m3 2
.m4 7
.ec \

.skip 10
.ce 4
MMon
a special timesharing montior for
different types of connections over
several lines
.page
.cl 0 1. Introduction
.ul
1. Introduction

.in +2
    In a multiuser enviroment it is neccesary that every user can
identify as a unique user of the system. This task is done by
.bold
logon
or others. But there are several conditions to start logon. On a direct
connected line logon should be started at once without hitting the
RETURN key. On a modemline it should be started after a connection has
been established. To ensure that logon is started at the right time you
need a timesharing monitor. MMon can be frreely configured to the most
thinkable problems so you can use one program for different types of
connections.
.in -2

.cl 0 2. Installing MMon
.ul
2. Installing MMon

.in +2
    Several steps are neccesary to install MMon correct. You have to
install the
.bold
Sysinfo-Database
(available by TOP-Munich) where you have to add some lines. The
configuration file is normally placed in /dd/SYS and called mmon.config.
If you like to change this insert a line like
.nj
.nf
.ti +5
mmon.config,s=<fullpath>
.justify
.fill
    where <fullpath> is a valid absolute filename for the
configuration file. For every device you want to use you have to insert
two lock-entries in sysinfo, like this:
.nj
.nf
.in +5
<device>,l
mmon.<device>,l
.in -5
.justify
.fill
    The <deivce> entry is used by lines which are used for dialin
and dialout. With the locking features of sysinfo you can realize this
very easy and effective. But what is to do if you want to stop the mmon
completely but you only the device on which it is running? For this the
second entry is used. When locking mmon.<device> mmon makes its cleanups
an dies.

    What else to do? You have to copy mmon to an execution directory
and create the configuration file. This will be discussed now.
.in -2

.cl 0 3. Configuration and Commandline Options
.ul
3. Configuration and Commandline Options

.in +2

    You have a lot of features to configure in the configfile.  A
lot of them can be overwritten by commandline options.  So when you can
do this the option is discussed when the feature is discussed.  The file
is organized in blocks, each block is introducted by the device for the
block and ended with the next device (or the end of the file).  The
device name follows the whole configuration.  Every configuration part
needs one line and must be indent by one or more spaces or tabs.  Now
all entries in detail.  The poosible commandline options are set in
brackets and written in the term (CLO: <opts>) where <opts> for the the
option in the commandline stands.

.in +2
.cl 1 3.1. is_modem
3.1. is_modem (CLO -m)

.in +2
    This tells MMon that there is a modem (or something like this)
is connected to this line. So MMon knows not to start logon at once but
to wait for a successful connection. Possible values are true and false
(further referd as a boolean expression.)
.in -2

.cl 1 3.2. init_modem
3.2. init_modem (CLO -m=<string>)

.in +2
    There is a default init string for a HAYES 1200 compatoble modem
in the program. If you need another init string, then you can set it
here. There are some escape-codes supported, all starting with a
backslash and followed by a letter. 'r' and 'n' sends a CR, 'l' a LF,
't' a TAB and 'd' stands for 1 sec. delay. This string is only send when
starting MMon (or if the device had been used by some other programs.)
.in -2

.cl 1 3.3. init_modem_no_attach
3.3. init_modem_no_attach (CLO -m=<string>)

.in +2
    This like init_modem, but used when no atach/detach should take
place.
.in -2

.cl 1 3.4. escape_to_command
3.4. escape_to_command

.in +2
    Normally MMon detachs a device to force DTR to go low and the
modem hangs up and return to command mode. If your driver doesn't
support this or you work with no atach/detach then MMon needs this to
return to command mode.
.in -2

.cl 1 3.5. reset_modem
3.5. reset_modem (CLO -r=<string>

.in +2
    When MMon cleans up to exit (or to free the device for another
program) it sends a reset string to the modem to ensure that it returns
to a defined state.
.in -2

.cl 1 3.6. reinit_modem
3.6. reinit_modem

.in +2
    After a hang up of the line this string will be send to make
sure that the modem is in a fine state to reenter a new loop. This
should not reset the values set in the init string, just make sure it
works probarly.
.in -2

.cl 1 3.7. logon_path
3.7. logon_path (CLO -p=<string>)

.in +2
    Normally you start logon from mmon. If you prefer to start some
other programs (e.g. login, or a own bbs program) you can insert it
here.
.in -2

.cl 1 3.8. start_before_logon
3.8. start_before_logon

.in +2
    With a special option you can force mmon to start a shellscript
before and after a start of logon. This gives the string to the shell
script which should be started before logon is started.
.in -2

.cl 1 3.9. start_after_logon
3.9. start_after_logon

.in +2
    Like above, but this is the path of the script to be executed
when logon returns.
.in -2

.cl 1 3.10. entry_for_logon
3.10. entry_for_logon (CLO -e=<string>

.in +2
    Logon reads its configurations from a special file (see logon)
and there are different entries, all with an own label. This string
gives the label for logon to be used for this line.
.in -2

.cl 1 3.11. options_for_logon
3.11. options_for_logon (CLO -o=<string>)

.in +2
    If you want to pass over some special Options to logon you can
insert them here.
.in -2

.cl 1 3.12. motd_file
3.12. motd_file (CLO -l, -l=<string>)

.in +2
    If you want to send no or another MOTD for this line use this
option. If you choose 'false' as text (or CLO -l) then no MOTD will be
displayed, otherwise you give the path of a file (CLO -l=<string>.)
.in -2

.cl 1 3.13. modem_response
3.13. modem_response

.in +2
    MMon determinates a successful connection by the responses of
the modem. This entry may come several times for a line for different
answers. The syntax for a string is <response>,<speed>, e.g. the entry
CONNECT 1200,1200 will determinate 'CONNECT 1200' as a valid response
for a successful connection and switch the line to 1200 baud.
.in -2

.cl 1 3.14. default_speed
3.14. default_speed (CLO -b=<string>)

.in +2
    This is the default speed (in baud/bps) for MMon to work in the
command mode of the modem, in general this will be hte highest supported
speed by the modem.
.in -2

.cl 1 3.15. examine_linkcount
3.15. examine_linkcount (CLO -k)

.in +2
    This boolean expressions tells MMon to examine the linkcount to
ensure that it is low enough (mostly zero) that the line drops it DTR
and the modems hangs up. Should only be used when atach/detach is on.
.in -2

.cl 1 3.16. use_attach
3.16. use_attach (CLO -d)

.in +2
    This boolean expression is used to switch the atach and detach
operations on and off (CLO -d switch the use OFF).
.in -2

.cl 1 3.17. use_checkfile
3.17. use_checkfile (CLO -c)

.in +2
    Above are the entries for scripts to be started before and after
the execution of logon. With this boolean expression you switch if
theses scripts are realy used on or off.
.in -2

.cl 1 3.18. use_fix_speed
3.18. use_fix_speed (CLO -f)

.in +2
    If you just want to allow a connection on one speed use this
boolean option. May be usefull for modems which just support one speed.
.in -2

.cl 1 3.19. fix_speed
3.19. fix_speed (CLO -f=<string>)

.in +2
    This sets the fixed speed to the given baud rate rather than the
default value.
.in -2

.cl 1 3.20. use_limit
3.20. use_limit (CLO -s=<string>)

.in +2
    In some special cases it may be useful to allow just a limitied
numbers of logins. After these MMon should die (mostly one login.) Use
this boolean option for switch it on or off.
.in -2

.cl 1 3.21. limit_logons_to
3.21. limit_logons_to (CLO -s=<string>)

.in +2
    use_limit switches the featzre on and off, this option sets the
number to the desired value.
.in -2

.cl 1 3.22. die_after_time
3.22. die_after_time (CLO -s=,<string> or in combination -s=<str>,<str>)

.in +2
    This gives a time in minutes to run and die, if no login had
took place to this time. Very useful in combination with limited logins.
So you can say with CLO -s=1,1 that only one login should be possible,
and this login must be in one minute. This is used in 'watch'.
.in -2

.cl 1 3.23. do_protocoll_to
3.23. do_protocoll_to (CLO -z=<string>)

.in +2
    This string is a pathname to a logfile for MMon. Normally
useless, but useful for debugging the program (and perhaps the responses
of the modem.)
.in -2

.cl 1 3.24. force_lock
3.24. force_lock (CLO -x)

.in +2
    When MMon is started on a device which is currently locked it
dies after some tries. If this option is given, it stays as long as it
will be free (boolean expression.)
.in -2

.cl 1 3.25. stay_on_free_device
3.25. stay_on_free_device (-g=<string>)

.in +2
    While MMon is running, some other process will use this device
for a short time (dial-outs, uucico etc.). These processes will try to
lock the device and MMon is forced to free it. Normally MMon then dies.
If you want that MMon restarts after the device is free again, use this
option. There is a numeric value neccasery that tells MMon to look all
n-times at the device. This value is in general one (every minute.)
.in -2

.cl 1 3.26. process_terminating_by_driver
3.26. process_terminating_by_driver (CLO -t)

.in +2
    When a user hangs up the line without logging off properly then
MMon will kill all running processes started by the user (if can be
reached through the process table tree.) If your device driver will kill
all processes which have a path open on this line on receiving a hangup
use this boolean option (never seen yet such driver..)
.in -2

.cl 1 3.37. line
3.37. line

.in +2
    The line on which MMon runs is normally given in the
commandline. If you want to use another line, use this option.
.in -2

.cl 1 3.38. do_lock
3.38. do_lock

.in +2
    This boolean expression is normally set to true that MMon will
lock the device. In some special cases this may not be useful, so you
can switch it off here.
.in -2

.cl 1 3.39. be_tolerant
3.39. be_tolerant

.in +2
    As written above, MMon tries to kill all process started by a
specific user when hang up. On some special programs this is not useful
at once, because they want to do some cleanup. These programs are usally
is one group. So you can give with this option a groupname where the
kill will be send later, so a cleanup can be safely done, useful for
UUCP, SMTP, etc. There can be more than one entry of this form for
different groups.
.in -2
.in -2
.in -2

.cl 0 4. Default Values
.ul
4. Default Values

.in +2

    Now this is a complete list of the defaults, so you know which
option you have to set or you may not set (lines must not be splitted as
in the example, this is just done for a better layout.)
.in +2
.nf
.nj
is_modem = false
init_modem = ATZ\\nAT X4 Q0 V1 S0=1 S2=255 S4=17 \\
             S10=20 S12=120 E0\\n
init_modem_no_attach = ATZ\\nAT X4 Q0 V1 S0=1 S2=2 \\
                       S4=17 S10=20 S12=120 E0\\n
#
#    Only i defaults as Ctrl-B (02), you can't
#    set it (yet) in the config file to
#    control codes
escape_to_command = ^B^B^B
reset_modem = ATZ\\n
reinit_modem = \\dAT\\n
logon_path = logon
start_before_logon = /dd/SYS/.mmonstart
start_after_logon = /dd/SYS/.mmonend
#
#    %d will be set to current line speed
entry_for_logon = M%d
#
#    No options on default
# options_for_logon =
#
#    The defualt MOTD should be used
# motd_file =
#
#    No responses are stored on default
# modem_response
default_speed = 1200
examine_linkcount = true
use_attach = true
use_checkfile = false
use_fix_speed = false
#
#    Not set as use_fix_speed is false
# fix_speed =
#
#    Only used in special applications
# use_limit =
# limit_logons_to =
# die_after_time =
#
# do_protocoll_to =
force_lock = false
#
#    Die after lock by another process
# stay_on_free_device =
process_terminating_by_driver = false
#
#    Line is set in command line
# line =
do_lock = true
#
#    Nothing set on default
# be_tolerant
.fill
.justify
.in -4

.cl 0 5. Example File
.ul
5. Example File

.in +2
    Here a working example file:
.nf
.nj
#
#    For a modem line
#
/t1
    is_modem = true
    entry_for_logon = M1200_8N1
    options_for_logon = -lc
    modem_response = CONNECT,300
    modem_response = CONNECT 1200,1200
    modem_response = CONNECT 2400,2400
    be_tolerant = Uucp
    be_tolerant = Smtp
    do_protocoll_to = /dd/mmon.log
    stay_on_free_device = true

#
#    For a hard wired line
#
/t3
    entry_for_logon = 9600
    options_for_logon = -tsm
    use_fix_speed = true
    fix_speed = 9600

#
#    For a hard wired line with UUCP/SMTP
#    Connections
#
/t5
    entry_for_logon = 9600
    use_attach = false
    use_fix_speed = true
    be_tolerant = Uucp
    be_tolerant = Smtp
    fix_speed = 9600

#
#    For a hard wired line for my Cambridge
#    Z88 handheld
#
/t6
    entry_for_logon = Z88
    motd_file = false
    options_for_logon = -ts
    use_attach = false
    use_fix_speed = true
    fix_speed = 2400
    stay_on_free_device = true
.fill
.justify
.in -4
.page
.ce
Contens
.pc