mutil_file_toss
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
mutil_file_toss [2016/04/19 03:43] – avon | mutil_file_toss [2016/04/19 03:51] – completed file hatching info. avon | ||
---|---|---|---|
Line 84: | Line 84: | ||
You then set a number of options as the **default values** MUTIL will apply when a file base is auto-created: | You then set a number of options as the **default values** MUTIL will apply when a file base is auto-created: | ||
+ | ; Display file to use | ||
+ | dispfile | ||
+ | ; Template to use | ||
+ | template | ||
; ACS to see the file base | ; ACS to see the file base | ||
acs_list | acs_list | ||
Line 94: | Line 97: | ||
acs_upload | acs_upload | ||
; ACS to hatch files from the file base to connected nodes | ; ACS to hatch files from the file base to connected nodes | ||
- | acs_hatch | + | acs_hatch |
; ACS to use the file base with sysop access | ; ACS to use the file base with sysop access | ||
acs_sysop | acs_sysop | ||
Line 109: | Line 112: | ||
| | ||
+ | == Define Specific Auto-Create Settings Based On Sender == | ||
+ | |||
+ | If you want to create settings specific to certain node addresses that send your system messages - you can! | ||
+ | |||
+ | For example, if you wanted to auto create bases that were linked to your fsxNet feed using the fsxNet HUB address of 21:1/100 , you have defined fsxNet as file group #1 in the File Group Editor, you want non-validated users (s10) to see files in the base, but only validated users (s20) to be able to download. You would set something like the following: | ||
+ | |||
+ | 21: | ||
+ | 21: | ||
+ | 21: | ||
+ | 21: | ||
+ | 21: | ||
+ | 21: | ||
+ | 21: | ||
+ | 21: | ||
+ | 21: | ||
+ | | ||
mutil_file_toss.txt · Last modified: 2023/01/03 00:49 by avon