• echoarc/in directory

    From Erazmus@21:1/133 to All on Friday, May 04, 2018 15:05:12
    Hello all,

    I just noticed that I have a directory called echoarc/in that appears to have
    a very large number of TICs andmessage packets. New ones are getting added every day, but I can't find any reference to this directory in any config
    file, or any reason as to why these files are in here. Can someone enlighten
    me as to what this is?

    Ian

    --- Mystic BBS v1.12 A38 2018/01/01 (Linux/32)
    * Origin: The Parity Error BBS - Kelowna, BC, Canada (21:1/133)
  • From Avon@21:1/101 to Erazmus on Saturday, May 05, 2018 10:20:50

    On 05/04/18, Erazmus pondered and said...

    Hello all,

    I just noticed that I have a directory called echoarc/in that appears to

    echomail/in ?

    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Erazmus@21:1/133 to Avon on Friday, May 04, 2018 15:37:20
    On 05/05/18, Avon said the following...


    echomail/in ?

    No. I have that directory also. It just hold current stuff that hasn't been processed yet. I have a echoarc/in as well, which almost seems like it's a
    copy of everything that's ever gone through echomail/in. Some sort of
    archive? Never noticed it before.

    Ian

    --- Mystic BBS v1.12 A38 2018/01/01 (Linux/32)
    * Origin: The Parity Error BBS - Kelowna, BC, Canada (21:1/133)
  • From Erazmus@21:1/133 to Erazmus on Friday, May 04, 2018 16:50:33
    Answering myself :)

    I found it. Apparently, sometime in the past, I set up a script on incoming mail to make a backup of each file before processing. I can't remember what issue I was having at the time and how this exactly would solve it.

    Anyway, this is purely a self-inflicted wound :)

    Ian

    --- Mystic BBS v1.12 A38 2018/01/01 (Linux/32)
    * Origin: The Parity Error BBS - Kelowna, BC, Canada (21:1/133)
  • From Jeff Smith@21:1/128 to Erazmus on Friday, May 04, 2018 18:47:44

    Hello Erazmus!

    echomail/in ?

    No. I have that directory also. It just hold current stuff that hasn't been processed yet. I have a echoarc/in as well, which almost seems
    like it's a copy of everything that's ever gone through echomail/in.
    Some sort of archive? Never noticed it before.

    I have a echomail/in and a echomail/out. I don't however have any echoarc directory.


    Jeff


    --- GoldED+/LNX 1.1.5-b20170303 / Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
    * Origin: The Ouijaboard II - Anoka, MN (21:1/128)
  • From Avon@21:1/101 to Erazmus on Saturday, May 05, 2018 16:45:33
    On 05/04/18, Erazmus pondered and said...

    Anyway, this is purely a self-inflicted wound :)

    Ouch but cool, glad you sorted / debugged :)

    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From bcw142@21:1/145 to Erazmus on Sunday, May 13, 2018 08:43:13
    On 05/04/18, Erazmus said the following...

    Answering myself :)

    I found it. Apparently, sometime in the past, I set up a script on incoming mail to make a backup of each file before processing. I can't remember what issue I was having at the time and how this exactly would solve it.

    Yup, welcome to the club. I thought there was a problem with Mystic A39, but
    it was a file already created that was blocking a new directory from being created as it had the same name and existed before the directory Mystic was trying to create - so also self-inflicted. I'm pretty sure we're in good company with that, I think even g00r00 does it sometimes. Luckily we're all generally good enough to be able to find the real problem and fix it ;)

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)