• TIC File processing question.

    From Argos@21:1/203 to All on Sat Oct 19 08:53:36 2019
    Question,

    A few days ago a File hatch was sent out going to FSX_ARTS and the file was impure74.zip.

    I received the file and the TIC just fine, Mutil processed the TIC and
    'copied' the file to the proper Files area without issue. good so far.

    However, it copied the file to the FSX_ARTS file ares it did not move the
    file, thus leaving a copy of that very file in my echomail IN directory.

    Although this is now big deal, I just delete it, but this is the third time I noticed this and wondering if I may have missed something on my mutil stanza in the .INI .....

    Any Thought ??

    ---

    Rocket Town BBS - Telnet: rtbbs.ddns.net
    fsxNET: 21:1/203 FidoNET:1:135/383 - Titusville, FL. NASA SPACE Coast

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Rocket Town BBS (21:1/203)
  • From Zip@21:1/202 to Argos on Sat Oct 19 16:11:36 2019
    Hello Argos!

    On 19 Oct 2019, Argos said the following...
    However, it copied the file to the FSX_ARTS file ares it did not move the file, thus leaving a copy of that very file in my echomail IN directory.

    Any Thought ??

    Is the target directory (for FSX_ARTS) writable for the Mystic BBS user? (Perhaps it couldn't save it there?)

    Best regards
    Zip

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)
  • From Argos@21:1/203 to Zip on Sat Oct 19 11:19:44 2019

    On 19 Oct 2019, Argos said the following...
    However, it copied the file to the FSX_ARTS file ares it did not move file, thus leaving a copy of that very file in my echomail IN directo

    Any Thought ??

    Is the target directory (for FSX_ARTS) writable for the Mystic BBS user? (Perhaps it couldn't save it there?)


    Yes it is .. The Zip file was processed and copied into the correct directory for the File base FSX_ARTS .... the weirdness is the zip file was left in my echomail IN directory and another copy of the very file was exactly where it
    is suppose to be. So, actually I had tow copies of that file. One in the FSX_ARTS file directory and the other in my echomail IN box.

    I am curious on why after the file was processed it left it in the IN box.

    ---

    Rocket Town BBS - Telnet: rtbbs.ddns.net
    fsxNET: 21:1/203 FidoNET:1:135/383 - Titusville, FL. NASA SPACE Coast

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Rocket Town BBS (21:1/203)
  • From Avon@21:1/101 to Argos on Sun Oct 20 15:42:48 2019
    On 19 Oct 2019 at 08:53a, Argos pondered and said...

    I received the file and the TIC just fine, Mutil processed the TIC and 'copied' the file to the proper Files area without issue. good so far.

    However, it copied the file to the FSX_ARTS file ares it did not move the file, thus leaving a copy of that very file in my echomail IN directory.

    Although this is now big deal, I just delete it, but this is the third time I noticed this and wondering if I may have missed something on my mutil stanza in the .INI .....

    Any Thought ??

    It should be moving it from your echomail in.

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Rocket Town BBS (21:1/203)

    We're both on windows... my logs looked like this for this import

    [snip]

    + Oct 19 07:46:34 Process: Toss FDN/TIC Files
    + Oct 19 07:46:34 Waiting for BUSY nodes
    + Oct 19 07:46:34 Tossing impure74.tic
    - Oct 19 07:46:34 Unused Key (CREATED) Value (Created by HTick, written by Gabriel Plutzar)
    - Oct 19 07:46:34 Unused Key (LDESC) Value (LDesc)
    - Oct 19 07:46:34 Unused Key (LDESC) Value (LDesc --/-- iMPURE!aSCII
    art expo #74. --/--)
    - Oct 19 07:46:34 Unused Key (LDESC) Value (LDesc)

    [snip]

    - Oct 19 07:46:34 Unused Key (ORIGIN) Value (Origin 21:1/1)
    - Oct 19 07:46:34 Unused Key (PATH) Value (Path 21:1/1 1571424357 Fri
    Oct 18 18:45:57 2019 UTC htick/w32-mvcdll 1.9.0-cur 17-08-15)
    - Oct 19 07:46:34 Unused Key (SEENBY) Value (Seenby 21:1/1)
    - Oct 19 07:46:34 Unused Key (SEENBY) Value (Seenby 21:1/2)
    - Oct 19 07:46:34 Unused Key (PATH) Value (Path 21:1/100 Sat Oct 19 07:46:13 2019 UTC Mystic/1.12 A43)
    - Oct 19 07:46:34 Unused Key (SEENBY) Value (Seenby 21:1/100)
    - Oct 19 07:46:34 Unused Key (SEENBY) Value (Seenby 21:1/101)
    - Oct 19 07:46:34 Unused Key (SEENBY) Value (Seenby 21:1/143)
    - Oct 19 07:46:34 Unused Key (SEENBY) Value (Seenby 21:1/102)

    [snip]

    - Oct 19 07:46:34 Unused Key (SEENBY) Value (Seenby 21:1/202)
    - Oct 19 07:46:34 Unused Key (SEENBY) Value (Seenby 21:1/203)
    - Oct 19 07:46:34 Unused Key (SEENBY) Value (Seenby 21:1/150)
    - Oct 19 07:46:34 Unused Key (SEENBY) Value (Seenby 21:1/142)
    - Oct 19 07:46:34 Unused Key (SEENBY) Value (Seenby 21:1/149)
    - Oct 19 07:46:34 Unused Key (SEENBY) Value (Seenby 21:1/126)
    + Oct 19 07:46:34 File impure74.zip Area FSX_ARTS From 21:1/100
    - Oct 19 07:46:34 Replace "impure74.zip"
    + Oct 19 07:46:34 Added to ANSI Art - Groups, Individuals etc.
    + Oct 19 07:46:34 Scanning Hatches
    + Oct 19 07:46:34 Results: 1 import, 0 toss, 0 hatch, 0 bad in 0.11s

    [snip]

    what does your log look like?

    was your area created during this process or did it exist already?

    Best, Paul

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to Argos on Sun Oct 20 15:45:22 2019
    On 19 Oct 2019 at 11:19a, Argos pondered and said...

    directory for the File base FSX_ARTS .... the weirdness is the zip file was left in my echomail IN directory and another copy of the very file
    was exactly where it is suppose to be. So, actually I had tow copies
    of that file. One in the FSX_ARTS file directory and the other in my echomail IN box.

    I am curious on why after the file was processed it left it in the IN
    box.

    I'm wondering could you send me or post your mutil stanza that covers this process?

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Argos@21:1/203 to Avon on Sun Oct 20 10:54:44 2019

    I'm wondering could you send me or post your mutil stanza that covers
    this process?


    [FileToss]

    ; Processes .TIC files from incoming directories and move/upload files to the
    ; appropriate file bases (optionally creating them). Files are then
    tossed
    ; to the fileboxes of all downlinks connected to the file base.

    ; Directory where failed files are moved, or comment out to disable
    archive of
    ; failed files. This includes incorrect file sizes, bad CRC, missing area
    ; when auto-create is disabled, duplicate files, unsecured, etc.

    bad_dir=C:\mystic\files\fsx\badfile

    ; Toss TIC from unsecure directory in addition to inbound?

    unsecure_dir = false

    ; File description to use when no DIZ, long description or description
    can be
    ; found from the file or .TIC file.

    no_desc=No Description

    ; Name of the uploader to use when adding TIC files into the local file bases

    uploader=fsxNet TIC

    ; Check size and CRC values supplied in TIC file (if found) against the actual
    ; file. If the value does not match, then skip tossing the file (moving
    it
    ; to the bad directory if enabled)

    check_crc = true
    check_size = true

    ; If this is true, then files that are FROM an unknown node will still be
    ; processed. If false, they will be moved to the bad directory or deleted
    ; depending on configuration. An "unsecure" node is one that is not directly
    ; configured within your echomail nodes configuration.

    allow_unsecure = false

    ; If this is true, then Mystic will allow the REPLACE TIC option, which will
    ; remove and replace files by the specified file mask.

    allow_replace = true

    ; If true, then Mystic will attempt to autocreate file bases when a file
    is
    ; found for an Area that does not already exist. If an unknown file is found
    ; and this option is disabled, the file will be considered a failure, and will
    ; be ignored/moved to bad directory (if enabled)

    auto_create = true

    ; The directory prefix for auto-created bases. This will be used with the
    ; areatag appended onto it, so for example if prefix was set to:
    ;
    ; dir_prefix=c:\mystic\files\fdn_
    ;
    ; And the areatag was "nodelist", Mystic would create and the use path:
    ; c:\mystic\files\fdn_nodelist\
    ;
    ; And the datafile would be fdn_nodelist

    dir_prefix = C:\mystic\files\

    ; Auto create base options

    dispfile =
    template = ansiflst
    acs_list = s10z2
    acs_ftp = s255z2
    acs_download = s10z2
    acs_upload = s255z2
    acs_hatch = s255z2
    acs_sysop = s255z2

    ; true/false type values 0=false 1=true (newscan 2=forced)

    free_files = 0
    show_uploader = 1
    new_scan = 1

    ; Node-specific options allow some options to be overridden when a file is
    ; coming from a specific node. These options should be prefixed with the
    ; address, examples for each supported option are listed below in comments

    21:100/1_bad_dir = C:\mystic\files\fsx\badfile\
    21:100/1_dir_prefix = C:\mystic\files\fsx\
    21:100/1_allow_replace = true
    21:100/1_acs_list = s10z2
    21:100/1_acs_ftp = s255z2
    21:100/1_acs_download = s10z2
    21:100/1_acs_upload = s255z2
    21:100/1_acs_hatch = s255z2
    21:100/1_acs_sysop = s255z2

    1:135/300_bad_dir = C:\mystic\files\fido\badfile\
    1:135/300_dir_prefix = C:\mystic\files\fido\
    1:135/300_allow_replace = true
    1:135/300_acs_list = s10z3
    1:135/300_acs_ftp = s255z3
    1:135/300_acs_download = s10z3
    1:135/300_acs_upload = s255z3
    1:135/300_acs_hatch = s255z3
    1:135/300_acs_sysop = s255z3

    11:1/222_bad_dir = C:\mystic\files\wwiv\badfile\
    11:1/222_dir_prefix = C:\mystic\files\wwiv\
    11:1/222_allow_replace = true
    11:1/222_acs_list = s10z4
    11:1/222_acs_ftp = s255z4
    11:1/222_acs_download = s10z4
    11:1/222_acs_upload = s255z4
    11:1/222_acs_hatch = s255z4
    11:1/222_acs_sysop = s255z4

    432:1/141_bad_dir = C:\mystic\files\vkradio\badfile\
    432:1/141_dir_prefix = C:\mystic\files\vkradio\
    432:1/141_allow_replace = true
    432:1/141_acs_list = s10z5
    432:1/141_acs_ftp = s255z5
    432:1/141_acs_download = s10z5
    432:1/141_acs_upload = s255z5
    432:1/141_acs_hatch = s255z5
    432:1/141_acs_sysop = s255z5

    ---

    Rocket Town BBS - Telnet: rtbbs.ddns.net
    fsxNET: 21:1/203 FidoNET:1:135/383 - Titusville, FL. NASA SPACE Coast

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Rocket Town BBS (21:1/203)