1. Forum
  2. FSXnet
  3. FSX MAG

  • Talisman msg base pack

    From vorlon@21:1/195.1 to apam on Tue Oct 25 12:26:14 2022
    Hi apam,

    vorlon@a3000:~/talisman$ ./toolbelt pack
    /home/vorlon/talisman/msgs/fsx/gen 200

    An error occured, msg base not packed!



    \/orlon
    aka
    Stephen


    --- Talisman v0.45-dev (Linux/m68k)
    * Origin: Vorlon Empire: Amiga 3000 powered in Sector 550 (21:1/195.1)
  • From apam@21:1/182 to vorlon on Tue Oct 25 13:17:18 2022
    vorlon@a3000:~/talisman$ ./toolbelt pack
    /home/vorlon/talisman/msgs/fsx/gen 200

    try :

    ./toolbelt pack fsx/gen 200

    Andrew


    --- Talisman v0.44-dev (Windows/x64)
    * Origin: Smuggler's Cove - Private BBS (21:1/182)
  • From Avon@21:1/101 to apam on Tue Oct 25 19:27:41 2022
    On 25 Oct 2022 at 01:17p, apam pondered and said...

    try :

    ./toolbelt pack fsx/gen 200

    I need

    ./toolbelt clean/vaccum room -now

    Please :)

    Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

    --- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From vorlon@21:1/195.1 to apam on Wed Oct 26 12:06:18 2022
    Hi apam,

    vorlon@a3000:~/talisman$ ./toolbelt pack
    /home/vorlon/talisman/msgs/fsx/gen 200

    try :./toolbelt pack fsx/gen 200

    Ok, did that and it looks like it packed the message bases.
    Loged into Talisman, and it then showed no messages in the bases.

    Did a postie toss, today and got these error's in the log file and no
    messages got imported. I was unable to read any messages in the message
    bases. Made a copy of them if you need to examine them, and then deleted
    the message base files:


    2022-10-26 10:48:54 [3760]
    ERROR: Unable to open message base! : msgs/fsx/dat
    2022-10-26 10:48:54 [3760] ERROR: Unable to open message base! :
    msgs/fsx/dat
    2022-10-26 10:48:54 [3760] ERROR: Unable to open message base! :
    msgs/fsx/bbs
    2022-10-26 10:48:54 [3760] ERROR: Unable to open message
    base! : msgs/fsx/dat
    2022-10-26 10:48:54 [3760] ERROR: Unable to open message base! :
    msgs/fsx/gen
    2022-10-26 10:48:54 [3760] ERROR: Unable to open message base! :
    msgs/fsx/dat
    2022-10-26 10:48:54 [3760] ERROR: Unable to open message base! :
    msgs/fsx/tst
    [...]
    2022-10-26 10:48:54 [3760] ERROR: Unable to open message base! :
    msgs/fsx/mys
    2022-10-26 10:48:54 [3760] ERROR: Unable to open message base! :
    msgs/fsx/dat


    \/orlon
    aka
    Stephen


    --- Talisman v0.45-dev (Linux/m68k)
    * Origin: Vorlon Empire: Amiga 3000 powered in Sector 550 (21:1/195.1)
  • From apam@21:1/182 to vorlon on Wed Oct 26 11:32:01 2022
    Ok, did that and it looks like it packed the message bases.
    Loged into Talisman, and it then showed no messages in the bases.

    looks like i forgot to add the byte swapping to the message packing stuff.

    I'll do it when I get some spare time next.

    Andrew


    --- Talisman v0.44-dev (Windows/x64)
    * Origin: Smuggler's Cove - Private BBS (21:1/182)
  • From apam@21:1/182 to vorlon on Wed Oct 26 20:58:12 2022
    Ok, did that and it looks like it packed the message bases.
    Loged into Talisman, and it then showed no messages in the bases.

    I think I found the problem, I made a mistake when I was adding the byte swapping code to the squish stuff. When packing it would write the base
    header out twice, once converted then once unconverted (So it was
    corrupting the message base).

    I think it should work now in git, but haven't tested it yet, but it
    would affect everyone, not just m68k

    Andrew


    --- Talisman v0.44-dev (Windows/x64)
    * Origin: Smuggler's Cove - Private BBS (21:1/182)
  • From apam@21:1/182 to vorlon on Wed Oct 26 21:23:13 2022
    Ok, did that and it looks like it packed the message bases.
    Loged into Talisman, and it then showed no messages in the bases.

    can confirm it now works in git... however the toolbelt command "pack"
    just gets rid of deleted messages.

    "prune" takes a second argument to prune the message base down to x
    messages.

    Andrew


    --- Talisman v0.44-dev (Windows/x64)
    * Origin: Smuggler's Cove - Private BBS (21:1/182)
  • From vorlon@21:1/195.1 to apam on Thu Oct 27 21:26:14 2022
    Hi apam,

    Ok, did that and it looks like it packed the message bases.
    Loged into Talisman, and it then showed no messages in the bases.

    can confirm it now works in git... however the toolbelt command "pack"
    just gets rid of deleted messages.

    "prune" takes a second argument to prune the message base down to x messages.

    Have just done a git clone, and a re-compile. Will do a re-scan of some
    message are's and report back.




    \/orlon
    aka
    Stephen


    --- Talisman v0.45-dev (Linux/m68k)
    * Origin: Vorlon Empire: Amiga 3000 powered in Sector 550 (21:1/195.1)
  • From vorlon@21:1/195.1 to apam on Fri Oct 28 09:54:07 2022
    Hi apam,

    Ok, did that and it looks like it packed the message bases.
    Loged into Talisman, and it then showed no messages in the bases.

    can confirm it now works in git... however the toolbelt command "pack"
    just gets rid of deleted messages.

    "prune" takes a second argument to prune the message base down to x messages.

    I really should have told areafix to only re-scan 200-300 messages! The
    system chucked along and imprted 18000 odd messages. (I went to bed).

    The pack/prune worked this time, but I also have noticed it's re-numberd
    the messages. With you now working on NNTP support that will be a bad
    thing. It might also affect offline readers as well.





    \/orlon
    aka
    Stephen


    --- Talisman v0.45-dev (Linux/m68k)
    * Origin: Vorlon Empire: Amiga 3000 powered in Sector 550 (21:1/195.1)
  • From apam@21:1/182 to vorlon on Fri Oct 28 10:16:27 2022
    The pack/prune worked this time, but I also have noticed it's
    re-numberd
    the messages. With you now working on NNTP support that will be a bad

    when you say renumbered what do you mean? it's supposed to maintain the
    umsgids from the old base (internal msg number), but the offset (visible
    msg no) will change?

    Andrew


    --- Talisman v0.45-dev (Windows/x64)
    * Origin: Smuggler's Cove - Private BBS (21:1/182)
  • From vorlon@21:1/195.1 to apam on Sat Oct 29 12:00:08 2022
    Hi apam,

    The pack/prune worked this time, but I also have noticed it's
    re-numberd the messages. With you now working on NNTP support that
    will be a bad

    when you say renumbered what do you mean? it's supposed to maintain
    the umsgids from the old base (internal msg number), but the offset
    (visible msg no) will change?

    After packing and pruning the message base, talisman displayed the
    messages as being from 1 to 200. I pruned from 18000 odd to 200.

    Doing the same thing on a intel hpt install, the message numbers are not changed, but there is still x amount of messages in the message base.

    I'm unable to see what they look like in golded/msged as cursor movement
    is totally broken on m68k.


    \/orlon
    aka
    Stephen


    --- Talisman v0.45-dev (Linux/m68k)
    * Origin: Vorlon Empire: Amiga 3000 powered in Sector 550 (21:1/195.1)
  • From apam@21:1/182 to vorlon on Sat Oct 29 21:13:22 2022
    After packing and pruning the message base, talisman displayed the
    messages as being from 1 to 200. I pruned from 18000 odd to 200.

    That's right. Talisman will always show them as 1..X where X is the
    number of messages in the base. It doesn't display the message number
    (UMSGID in squish)

    It does use the UMSGID for last read (or at least it's supposed to)

    Doing the same thing on a intel hpt install, the message numbers are
    not
    changed, but there is still x amount of messages in the message base.

    Are you using HPT with talisman on intel? or some other message viewer?

    I do confuse myself sometimes with message numbers, but there is two
    numbers in play, the unique message number each message gets when it's
    put in the message base for the first time, and the number of the message
    as an offset in the index.

    So, message number 1 will be the first message displayed always, however
    it might not be message id number 1, it might be message id number 300 if you've pruned off 300 messages.

    If you never delete or prune messages, the numbers should generally be
    the same (which catches me out sometimes)

    Other message viewers might not do it that way, they might just use the
    message id number instead of the offset. I didn't want to do that as the
    number could get quiet high, even if there are not many messages in the
    base.

    Andrew


    --- Talisman v0.45-dev (Windows/x64)
    * Origin: Smuggler's Cove - Private BBS (21:1/182)
  • From vorlon@21:1/195.1 to apam on Sun Oct 30 11:16:25 2022
    Hi apam,

    After packing and pruning the message base, talisman displayed the
    messages as being from 1 to 200. I pruned from 18000 odd to 200.

    That's right. Talisman will always show them as 1..X where X is the
    number of messages in the base. It doesn't display the message number (UMSGID in squish)

    It does use the UMSGID for last read (or at least it's supposed to)

    Ok. So just a display thing then.

    Doing the same thing on a intel hpt install, the message numbers
    are not changed, but there is still x amount of messages in the
    message base.

    Are you using HPT with talisman on intel? or some other message
    viewer?

    No, just comparing what the hub/boss node system does. There's no BBS
    software involved, and just HPT/Golded on intel x64.



    \/orlon
    aka
    Stephen


    --- Talisman v0.45-dev (Linux/m68k)
    * Origin: Vorlon Empire: Amiga 3000 powered in Sector 550 (21:1/195.1)
  • From Oli@21:3/102 to vorlon on Mon Oct 31 13:01:48 2022
    vorlon wrote (2022-10-28):

    I really should have told areafix to only re-scan 200-300 messages! The system chucked along and imprted 18000 odd messages. (I went to bed).

    The pack/prune worked this time, but I also have noticed it's re-numberd the messages. With you now working on NNTP support that will be a bad thing. It might also affect offline readers as well.

    Changing Message-IDs after a rescan/import looks like a problem. UMSGIDs might change and Gatebau-compatible Message-IDs / References will be affected by the hpt/smapi JAM 2-second bug.

    For some reason you messages also don't have a REPLY kludge, but apam's message do. Both written with Talisman v0.45-dev?


    ⁂

    ---
    * Origin: War is Peace. Freedom is Slavery. Ignorance is Strength. (21:3/102)
  • From vorlon@21:1/195.1 to Oli on Tue Nov 1 11:11:16 2022
    Hi Oli,

    For some reason you messages also don't have a REPLY kludge, but
    apam's message do. Both written with Talisman v0.45-dev?

    There was no reply kludge, as I'd nuked the local message base and
    grabbed the text from the hub/boss nodes message base!

    Jam's not being used on Talisman, so it wont see that bug!.



    \/orlon
    aka
    Stephen


    --- Talisman v0.45-dev (Linux/m68k)
    * Origin: Vorlon Empire: Amiga 3000 powered in Sector 550 (21:1/195.1)
  • From Oli@21:3/102 to vorlon on Tue Nov 1 20:32:39 2022
    vorlon wrote (2022-11-01):

    For some reason you messages also don't have a REPLY kludge, but
    apam's message do. Both written with Talisman v0.45-dev?

    There was no reply kludge, as I'd nuked the local message base and
    grabbed the text from the hub/boss nodes message base!

    But my message had a MSGID and your reply does not have a REPLY kludge.

    Or do you mean: grabbed = copy&paste?

    Jam's not being used on Talisman, so it wont see that bug!.

    until the hub's message base is JAM and a rescan is done by hpt.


    ⁂

    ---
    * Origin: War is Peace. Freedom is Slavery. Ignorance is Strength. (21:3/102)
  • From vorlon@21:1/195.1 to Oli on Wed Nov 2 10:08:13 2022
    There was no reply kludge, as I'd nuked the local message base and grabbed the text from the hub/boss nodes message base!

    But my message had a MSGID and your reply does not have a REPLY
    kludge.

    That might be another bug then, as this install is stock standard with no
    mods.

    Apam, are you seeing this?


    Or do you mean: grabbed = copy&paste?

    Yes.



    \/orlon
    aka
    Stephen


    --- Talisman v0.45-dev (Linux/m68k)
    * Origin: Vorlon Empire: Amiga 3000 powered in Sector 550 (21:1/195.1)
  • From apam@21:1/182 to vorlon on Wed Nov 2 09:26:16 2022
    Apam, are you seeing this?

    Yes

    Andrew


    --- Talisman v0.45-dev (Windows/x64)
    * Origin: Smuggler's Cove - Private BBS (21:1/182)
  • From apam@21:1/182 to Oli on Wed Nov 2 09:26:15 2022
    @MSGID: 21:3/102 6361744e
    @REPLY: 21:1/195.1 63606424

    Testing to see if this message has a reply kludge

    Andrew


    --- Talisman v0.45-dev (Windows/x64)
    * Origin: Smuggler's Cove - Private BBS (21:1/182)
  • From apam@21:1/182 to vorlon on Wed Nov 2 09:29:20 2022
    Can you double check Oli's message has a msgid kludge when it gets to
    your talisman bbs?

    you can turn on kludges in the setting menu

    Andrew


    --- Talisman v0.45-dev (Windows/x64)
    * Origin: Smuggler's Cove - Private BBS (21:1/182)
  • From vorlon@21:1/195.1 to apam on Wed Nov 2 11:02:18 2022
    Hi apam,

    @TZUTC: 1000
    @CHRS: CP437 2
    @MSGID: 21:1/182 6361ABD0
    @REPLY: 21:1/195.1 6361A6DD
    @TID: Postie 0.13
    Can you double check Oli's message has a msgid kludge when it gets to
    your talisman bbs?

    you can turn on kludges in the setting menu


    Your's above.

    Oli's kludges.

    @MSGID: 21:3/102 6361744e
    @REPLY: 21:1/195.1 63606424
    @PID: JamNNTPd/Linux 1
    @CHRS: UTF-8 2
    @TZUTC: 0100
    @TID: CrashMail II/Linux 1.7




    \/orlon
    aka
    Stephen


    --- Talisman v0.45-dev (Linux/m68k)
    * Origin: Vorlon Empire: Amiga 3000 powered in Sector 550 (21:1/195.1)
  • From vorlon@21:1/195.1 to apam on Wed Nov 2 11:04:17 2022
    Hi apam,

    Can you double check Oli's message has a msgid kludge when it gets to
    your talisman bbs?

    Just looked at the reply to you after turning that option on, and there
    is no reply kludge on my messages.



    \/orlon
    aka
    Stephen


    --- Talisman v0.45-dev (Linux/m68k)
    * Origin: Vorlon Empire: Amiga 3000 powered in Sector 550 (21:1/195.1)
  • From apam@21:1/182 to vorlon on Wed Nov 2 12:18:19 2022
    Just looked at the reply to you after turning that option on, and
    there
    is no reply kludge on my messages.

    Yep, sorry about that.

    It should be fixed in git. Was a case of me confusing offsets with
    umsgids, so it only happens on packed message bases.

    Andrew


    --- Talisman v0.45-dev (Windows/x64)
    * Origin: Smuggler's Cove - Private BBS (21:1/182)
  • From vorlon@21:1/195.1 to apam on Thu Nov 3 10:45:30 2022
    Hi apam,

    Just looked at the reply to you after turning that option on, and
    there is no reply kludge on my messages.

    Yep, sorry about that.

    It should be fixed in git. Was a case of me confusing offsets with
    umsgids, so it only happens on packed message bases.

    One reply kludge now present!.



    \/orlon
    aka
    Stephen


    --- Talisman v0.45-dev (Linux/m68k)
    * Origin: Vorlon Empire: Amiga 3000 powered in Sector 550 (21:1/195.1)
  • From Oli@21:3/102 to apam on Wed Nov 30 18:33:51 2022
    apam wrote (2022-11-02):

    Just looked at the reply to you after turning that option on, and
    there
    is no reply kludge on my messages.

    Yep, sorry about that.

    It should be fixed in git. Was a case of me confusing offsets with
    umsgids, so it only happens on packed message bases.

    Thanks for the fix, Andrew.

    (I haven't had much time / motivation to read fsxnet lately. Trying to catch up).

    ⁂

    ---
    * Origin: War is Peace. Freedom is Slavery. Ignorance is Strength. (21:3/102)