Hello All!
When i look to the logic for the echoarea definition -nm switch i found:
##############################################################################
#EchoArea <name> <file> [-b <msgbase>] [Options] [linkAKAs] [linkOptions] #
# LinkOptions:
# -mn
# this link is mandatory subscribed,
# you may also set:
# "<aka> -r -mn"
# or
# "<aka> -w -r"
# and so on...
Because there may be links that have a read-only or write-only (-r -w) limitation this linkOption works per individual linkAKA?
If yes i'd like to suggest a documentation update from:
#EchoArea <name> <file> [-b <msgbase>] [Options] [linkAKAs] [linkOptions] to
#EchoArea <name> <file> [-b <msgbase>] [Options] [linkAKAs [linkOptions]]
When i look to the logic for the echoarea definition -nm switch i
found:
###################################################################### ######## #EchoArea <name> <file> [-b <msgbase>] [Options] [linkAKAs] [linkOptions] # # LinkOptions: # -mn # this link is mandatory subscribed, # you may also set: # "<aka> -r -mn" # or #
"<aka> -w -r" # and so on...
Because there may be links that have a read-only or write-only (-r -w) limitation this linkOption works per individual linkAKA?
If yes i'd like to suggest a documentation update from:
#EchoArea <name> <file> [-b <msgbase>] [Options] [linkAKAs]
[linkOptions] to #EchoArea <name> <file> [-b <msgbase>] [Options] [linkAKAs [linkOptions]]
^
^
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 139:10:25 |
Calls: | 166 |
Files: | 5,389 |
Messages: | 223,229 |