• Auto Create File Areas?

    From Jeff Smith@1:282/1031 to All on Mon Jun 8 13:32:08 2020

    Hello everybody!

    A question. I have setup some file areas in Mystic manually.
    But decided to setup future files from specific nodes as auto
    created.

    I have edited the appropriate mutil.ini stanza to specify a
    a directory prefix of /home/mystic/files/fido_ for a specific
    node. But when a file and the associated TIC is received from
    that specified node and processed I get the following in the
    Mutil log file:

    ----------------- MUTIL v1.12 A46 2020/04/26 Mon, Jun 08 2020 (loglevel 3)
    + Jun 08 13:23:49 Startup using filetoss.ini
    - Jun 08 13:23:49 EXEC FileToss
    + Jun 08 13:23:49 Process: Toss FDN/TIC Files
    + Jun 08 13:23:49 Results: Auto-create prefix path does not exist in 0.01s
    ! Jun 08 13:23:49 Status: FATAL
    + Jun 08 13:23:49 Shutdown Normal (0) ---------------------------------------------------------------

    Now it is my understanding that if say a file in the nodelist
    file echo is received then upon processing Mutil would use the
    specified prefix to auto-create the path /home/mystic/files/fido_nodelist
    for the nodelist file. Based on the log I would say that the file
    directory path doesn't exist because Mutil hasn't/didn't create
    it.

    As always there exists the possibility that I am missing something
    here. :)



    Jeff


    --- Mystic v1.12 A46 (2020/04/26) GoldED+/LNX 1.1.5-b20170303
    * Origin: The OuijaBoard BBS - bbs.ouijabrd.net (1:282/1031)
  • From g00r00@1:129/215 to Jeff Smith on Tue Jun 9 00:29:53 2020
    I have edited the appropriate mutil.ini stanza to specify a
    a directory prefix of /home/mystic/files/fido_ for a specific
    node. But when a file and the associated TIC is received from
    that specified node and processed I get the following in the
    Mutil log file:

    + Jun 08 13:23:49 Process: Toss FDN/TIC Files
    + Jun 08 13:23:49 Results: Auto-create prefix path does not exist in

    Does /home/mystic/files/ exist?

    --- Mystic BBS v1.12 A46 2020/05/28 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From Jeff Smith@1:282/1031 to g00r00 on Tue Jun 9 11:23:46 2020

    Hello g00r00!

    09 Jun 20 00:29, you wrote to me:

    I have edited the appropriate mutil.ini stanza to specify a
    a directory prefix of /home/mystic/files/fido_ for a specific
    node. But when a file and the associated TIC is received from
    that specified node and processed I get the following in the
    Mutil log file:

    + Jun 08 13:23:49 Process: Toss FDN/TIC Files
    + Jun 08 13:23:49 Results: Auto-create prefix path does not
    exist in

    Does /home/mystic/files/ exist?

    Yes it does. Before I attempted the Auto Create option Mystic
    has processed incoming files/tics ok when the file echos were
    manually created. Right now there 506 subdirectories under
    /home/mystic/files containing some 4500 files.

    Jeff


    --- Mystic v1.12 A46 (2020/04/26) GoldED+/LNX 1.1.5-b20170303
    * Origin: The OuijaBoard BBS - bbs.ouijabrd.net (1:282/1031)
  • From g00r00@1:129/215 to Jeff Smith on Wed Jun 10 19:43:17 2020
    Yes it does. Before I attempted the Auto Create option Mystic
    has processed incoming files/tics ok when the file echos were
    manually created. Right now there 506 subdirectories under /home/mystic/files containing some 4500 files.

    Thanks. That message should only be displayed if Mystic can't access that directory.

    When you have some time would you mind upgrading to the latest prealpha
    version just to make sure I didn't fix something between your version and the current? I do think I made a change or two with the file tossing but I can't remember what it was exactly.

    --- Mystic BBS v1.12 A46 2020/05/28 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From Jeff Smith@1:282/1031 to g00r00 on Wed Jun 10 20:31:39 2020

    Hello g00r00!

    10 Jun 20 19:43, you wrote to me:

    Yes it does. Before I attempted the Auto Create option Mystic
    has processed incoming files/tics ok when the file echos were
    manually created. Right now there 506 subdirectories under
    /home/mystic/files containing some 4500 files.

    Thanks. That message should only be displayed if Mystic can't access
    that directory.

    When you have some time would you mind upgrading to the latest
    prealpha version just to make sure I didn't fix something between your version and the current? I do think I made a change or two with the
    file tossing but I can't remember what it was exactly.

    I upgraded to the 06/10/2020 pre-alpha version of Mystic and executed
    Mutil to process files for a fileecho that I have not as yet manually
    added and I get:

    ----------------- MUTIL v1.12 A46 2020/06/10 Wed, Jun 10 2020 (loglevel 3)
    + Jun 10 20:13:39 Startup using filetoss.ini
    - Jun 10 20:13:39 EXEC FileToss
    + Jun 10 20:13:39 Process: Toss FDN/TIC Files
    + Jun 10 20:13:39 Results: Auto-create prefix path does not exist: in 0.01s
    ! Jun 10 20:13:39 Status: FATAL
    + Jun 10 20:13:39 Shutdown Normal (0)

    Jeff


    --- Mystic v1.12 A46 (2020/06/10) GoldED+/LNX 1.1.5-b20170303
    * Origin: The OuijaBoard BBS - bbs.ouijabrd.net (1:282/1031)
  • From g00r00@1:129/215 to Jeff Smith on Thu Jun 11 12:28:55 2020
    I upgraded to the 06/10/2020 pre-alpha version of Mystic and executed Mutil to process files for a fileecho that I have not as yet manually added and I get:

    + Jun 10 20:13:39 Results: Auto-create prefix path does not exist: in

    So it looks like its saying dir_prefix is set to a invalid/blank value.

    --- Mystic BBS v1.12 A46 2020/05/28 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From Nicholas Boel@1:154/10 to g00r00 on Thu Jun 11 14:45:54 2020
    Hello g00r00,

    On Thu Jun 11 2020 12:28:54, g00r00 wrote to Jeff Smith:

    I upgraded to the 06/10/2020 pre-alpha version of Mystic and
    executed Mutil to process files for a fileecho that I have not as
    yet manually added and I get:

    + Jun 10 20:13:39 Results: Auto-create prefix path does not
    exist: in

    So it looks like its saying dir_prefix is set to a invalid/blank
    value.

    It seems as though he's trying to actually prefix his directory name, ie: fido_<dirname>, So Mystic seems to be telling him that ../mystic/files/fido_ doesn't exist. I've always understood the "Prefix Directory" as just that (the path to the actual directory), and not an actual prefixed directory name. Unless you've already added this functionality in, it may be something entirely new.

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- GoldED+/LNX 1.1.5-b20181215
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From g00r00@1:129/215 to Nicholas Boel on Thu Jun 11 17:30:16 2020
    It seems as though he's trying to actually prefix his directory name, ie: fido_<dirname>, So Mystic seems to be telling him that ../mystic/files/fido_ doesn't exist. I've always understood the "Prefix

    It removes the prefix part and checks to make sure the base directory is accessible. If it cannot access the base directory then it shows that error.

    --- Mystic BBS v1.12 A46 2020/05/28 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From Nicholas Boel@1:154/10 to g00r00 on Fri Jun 12 06:00:40 2020
    Hello g00r00,

    On Thu Jun 11 2020 17:30:16, g00r00 wrote to Nicholas Boel:

    It seems as though he's trying to actually prefix his directory
    name, ie: fido_<dirname>, So Mystic seems to be telling him that
    ../mystic/files/fido_ doesn't exist. I've always understood the
    "Prefix

    It removes the prefix part and checks to make sure the base directory
    is accessible. If it cannot access the base directory then it shows
    that error.

    Ah ok. Then disregard. ;)

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- GoldED+/LNX 1.1.5-b20181215
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Jeff Smith@1:282/1031 to Nicholas Boel on Fri Jun 12 10:40:21 2020

    Hello Nicholas!

    11 Jun 20 14:45, you wrote to g00r00:

    + Jun 10 20:13:39 Results: Auto-create prefix path does not
    exist: in

    So it looks like its saying dir_prefix is set to a invalid/blank
    value.

    It seems as though he's trying to actually prefix his directory name,
    ie: fido_<dirname>, So Mystic seems to be telling him that ../mystic/files/fido_ doesn't exist. I've always understood the
    "Prefix Directory" as just that (the path to the actual directory),
    and not an actual prefixed directory name. Unless you've already added this functionality in, it may be something entirely new.

    I had thought of that too. As a test I created the prefix path fido_ under /home/mystic/files. I got the same response when running Mutil. It didn't
    seem to matter if /home/mystic/files or /home/mystic/files/fido_ existed.
    The docs led me to think that Mystic would create the prefix path specified when a file/tic was precessed for an unknown fileecho. As in /fido_nodelist when a file for say the nodelist file echo was received. Please correct any misunderstanding that I might have.

    Jeff


    --- Mystic v1.12 A46 (2020/06/10) GoldED+/LNX 1.1.5-b20170303
    * Origin: The OuijaBoard BBS - bbs.ouijabrd.net (1:282/1031)
  • From Jeff Smith@1:282/1031 to g00r00 on Fri Jun 12 10:55:13 2020

    Hello g00r00!

    11 Jun 20 17:30, you wrote to Nicholas Boel:

    It seems as though he's trying to actually prefix his directory
    name, ie: fido_<dirname>, So Mystic seems to be telling him that
    ../mystic/files/fido_ doesn't exist. I've always understood the
    "Prefix

    It removes the prefix part and checks to make sure the base directory
    is accessible. If it cannot access the base directory then it shows
    that error.

    And if that was the case I would totally understand the error and eliminate
    the cause of the error. But in this case /home/mystic/files does indeed
    exist and is occupied by hundreds of sub-directories and thousands of files. All put there by Mystic for manually created file echos.

    Jeff


    --- Mystic v1.12 A46 (2020/06/10) GoldED+/LNX 1.1.5-b20170303
    * Origin: The OuijaBoard BBS - bbs.ouijabrd.net (1:282/1031)
  • From Jeff Smith@1:282/1031 to g00r00 on Fri Jun 12 13:16:26 2020

    Hello g00r00!

    It removes the prefix part and checks to make sure the base directory
    is accessible. If it cannot access the base directory then it shows
    that error.

    I also noticed that as long as auto_create is set to true Mutil will fail immediately and not process any files/tics. Only when auto_create is set
    to false will Mutil process files/tics for the manually created file echos.

    Jeff


    --- Mystic v1.12 A46 (2020/06/10) GoldED+/LNX 1.1.5-b20170303
    * Origin: The OuijaBoard BBS - bbs.ouijabrd.net (1:282/1031)
  • From Michael Pierce@1:340/201 to Jeff Smith on Fri Jun 12 12:40:31 2020
    Hello g00r00!

    11 Jun 20 17:30, you wrote to Nicholas Boel:

    It seems as though he's trying to actually prefix his directory
    name, ie: fido_<dirname>, So Mystic seems to be telling him that
    ../mystic/files/fido_ doesn't exist. I've always understood the
    "Prefix

    It removes the prefix part and checks to make sure the base
    directory is accessible. If it cannot access the base directory
    then it shows that error.

    And if that was the case I would totally understand the error and eliminate the cause of the error. But in this case /home/mystic/files
    does indeed exist and is occupied by hundreds of sub-directories and thousands of files. All put there by Mystic for manually created file echos.

    Jeff
    quick question, if your files are litterly in /home/mystic/files, who owns the files/folders?? does the mystic folder and the files folder have the exact same permissions?? mutil might not be able to create the new folder if permissions are not right.

    Michael

    ... Official Blue Wave Betazoid (oh, Deanna...?)
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Mike's Mansion - Portland, OR - mansion.dynv6.net:2323 (1:340/201)
  • From g00r00@1:129/215 to Jeff Smith on Fri Jun 12 17:24:30 2020
    And if that was the case I would totally understand the error and eliminate the cause of the error. But in this case /home/mystic/files
    does indeed exist and is occupied by hundreds of sub-directories and thousands of files. All put there by Mystic for manually created file echos.

    The logs said you have no value set at all for your auto-create prefix. I can't see your configuration but make sure you're executing the correct .ini file and that you have the value set properly, that MUTIL has access to read the values, etc.

    I use auto-create here and its working for me so thats as much as I know at
    the moment. I haven't had a chance to set up a test on the Linux side.

    --- Mystic BBS v1.12 A46 2020/06/11 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From Jeff Smith@1:282/1031 to Michael Pierce on Sun Jun 14 12:19:53 2020

    Hello Michael!

    12 Jun 20 12:40, you wrote to me:



    And if that was the case I would totally understand the error and
    eliminate the cause of the error. But in this case
    /home/mystic/files does indeed exist and is occupied by hundreds
    of sub-directories and thousands of files. All put there by
    Mystic for manually created file echos.

    quick question, if your files are litterly in /home/mystic/files, who
    owns the files/folders?? does the mystic folder and the files folder
    have the exact same permissions?? mutil might not be able to create
    the new folder if permissions are not right.

    That was one of the first things that I checked. That entire directory structure /home/mystic/.... is owned by mystic and has read and write
    access with create and delete rights. Mystic can toss files to the same
    prefix directory /home/mystic/files/ when it tosses files for manually
    created file echos. But for some reason doesn't seem to see
    /home/mystic/files when using the auto-create option.

    Jeff


    --- Mystic v1.12 A46 (2020/06/10) GoldED+/LNX 1.1.5-b20170303
    * Origin: The OuijaBoard BBS - bbs.ouijabrd.net (1:282/1031)
  • From Jay Harris@1:229/664 to g00r00 on Mon Jun 15 14:46:20 2020
    I use auto-create here and its working for me so thats as much as I know at the moment. I haven't had a chance to set up a test on the Linux
    side.

    I'm running Mystic v1.12 A45 (2020/02/18) on Windows 10 32bit. I can auto-create file areas but the auto-prefix option doesn't seem to work
    for me.

    It seems to ignore the (address)_dir_prefix= option and only use the dir_prefix= option.

    Here's what I have in my mailin.ini:

    bad_dir=c:\mystic\files\badfile
    unsecure_dir = false
    no_desc=No Description
    uploader=NRBBS
    check_crc = true
    check_size = true
    allow_unsecure = false
    allow_replace = true
    auto_create = true
    1:229/426_bad_dir = c:\mystic\files\bad-fdn\
    1:229/426_dir_prefix = c:\mystic\files\fdn_
    1:229/426_allow_replace = true
    1:229/426_acs_list = s10z2
    1:229/426_acs_ftp = s255z2
    1:229/426_acs_download = s20z2
    1:229/426_acs_upload = s255z2
    1:229/426_acs_hatch = s255z2
    1:229/426_acs_sysop = s255z2
    dir_prefix = c:\mystic\files\
    dispfile =
    template = ansiflst
    acs_ftp = s255
    acs_hatch = s255
    free_files = 0
    show_uploader = 1
    new_scan = 1


    I have several other lines in the .ini file such as:

    21:3/100_dir_prefix = c:\mystic\files\fsx_
    46:1/156_dir_prefix = c:\mystic\files\agora_
    1337:3/100_dir_prefix = c:\mystic\files\tqw_
    618:500/1_dir_prefix = c:\mystic\files\mcn_

    It will create the new file base just fine, but it ignores the prefixed dir_prefix line and just uses "naked" dir_prefix option. All of the other settings seem to carry over. I tried removing the dir_prefix= option but
    then the FileToss stanza just errors out.

    Jay

    --- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
    * Origin: Northern Realms BBS | bbs.nrbbs.net | Binbrook, ON (1:229/664)
  • From g00r00@1:129/215 to Jay Harris on Mon Jun 15 15:08:12 2020
    I have several other lines in the .ini file such as:

    21:3/100_dir_prefix = c:\mystic\files\fsx_
    46:1/156_dir_prefix = c:\mystic\files\agora_ 1337:3/100_dir_prefix = c:\mystic\files\tqw_
    618:500/1_dir_prefix = c:\mystic\files\mcn_

    This was not an option in A45. It was added in A46. If it doesn't work
    after upgrading please let me know. There was someone else having a problem with this even in the A46 version so there is probably a bug somewhere that needs to be uncovered.

    --- Mystic BBS v1.12 A46 2020/06/11 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)
  • From Jay Harris@1:229/664 to g00r00 on Mon Jun 15 15:32:16 2020
    On 15 Jun 2020, g00r00 said the following...

    This was not an option in A45. It was added in A46. If it doesn't work after upgrading please let me know. There was someone else having a problem with this even in the A46 version so there is probably a bug somewhere that needs to be uncovered.

    Thank you sir, I'll give A46 a try today.

    Jay

    --- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
    * Origin: Northern Realms BBS | bbs.nrbbs.net | Binbrook, ON (1:229/664)
  • From Michael Pierce@1:340/201 to Jeff Smith on Mon Jun 15 16:17:31 2020
    quick question, if your files are litterly in /home/mystic/files,
    who owns the files/folders?? does the mystic folder and the files
    folder have the exact same permissions?? mutil might not be able
    to create the new folder if permissions are not right.

    That was one of the first things that I checked. That entire directory structure /home/mystic/.... is owned by mystic and has read and write access with create and delete rights. Mystic can toss files to the
    same prefix directory /home/mystic/files/ when it tosses files for manually created file echos. But for some reason doesn't seem to
    see /home/mystic/files when using the auto-create option.

    it still sounds like a permissions issue?? maybe "auto-create" is using a different userid?? what if for a test, you chmod 777 files -R
    see if being completely open for permission allows a file to be tossed.

    the only other thing that comes to mind .. maybe auto-create is trying to create the file in a non-existent tmp location ?? like say instead of temp1 its /tmptic.xyz ??

    Michael


    ... Bad Command:(A)bort (R)etry (T)ake RAM hostage
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Mike's Mansion - Portland, OR - mansion.dynv6.net:2323 (1:340/201)