1. Forum
  2. FidoNet
  3. MBSE

  • Mbse error after install

    From Benny Pedersen@2:230/0 to Rj Clay on Wed May 8 03:21:34 2013
    Hello Rj!

    29 Sep 2012 10:35, Rj Clay wrote to Benny Pedersen:

    would be great if one that have installed build an mbse.ebuild that
    installs it as it was make install,

    Thought you'd already created an ebuild for MBSE? Or am
    misunderstanding what you're referring to?

    this was my plan, but since i need a clean gentoo computer to develop it on i never got that done :/

    but i will do when i have it all sorted out, its also just that i do not really
    know where to begin with it also, and how mbse is working that holds me back

    xinetd supports initd script lines if done correct, so no need to
    convert

    Not sure what you're referring to, there; I understood that the
    issue that Gert is/was seeing was regarding /etc/init.d/mbsebbs, not /etc/inetd.conf or /etc/xinetd.d/mbsebbs...

    imho Gert used a real telnetd to call mbse, but he should configure mbse as a telnetd instaed, i dont remember all mbse problems right here, it would have being the same if postfix needed an telnetd setup :)))))


    Regards Benny

    ... there can only be one way of life, and it works :)

    --- Msged/LNX 6.2.0 (Linux/3.7.10-gentoo (i686))
    * Origin: duggi.junc.org where qico is waiting (2:230/0)
  • From Gert Andersen@1:218/700 to Benny Pedersen on Wed May 8 23:42:36 2013
    Hello Benny!

    Wed May 08 2013, Benny Pedersen wrote to Rj Clay:

    Hello Rj!

    29 Sep 2012 10:35, Rj Clay wrote to Benny Pedersen:

    would be great if one that have installed build an mbse.ebuild that
    installs it as it was make install,

    Thought you'd already created an ebuild for MBSE? Or am
    misunderstanding what you're referring to?

    this was my plan, but since i need a clean gentoo computer to develop
    it on i never got that done :/

    but i will do when i have it all sorted out, its also just that i do
    not really know where to begin with it also, and how mbse is working
    that holds me back

    xinetd supports initd script lines if done correct, so no need to
    convert

    Not sure what you're referring to, there; I understood that the
    issue that Gert is/was seeing was regarding /etc/init.d/mbsebbs, not
    /etc/inetd.conf or /etc/xinetd.d/mbsebbs...

    imho Gert used a real telnetd to call mbse, but he should configure
    mbse as a telnetd instaed, i dont remember all mbse problems right
    here, it would have being the same if postfix needed an telnetd setup
    :)))))

    The most gentoo mbse install is that the mbse.gentoo script file have still a path error, and this script is been put to /etc/init.d/mbsebbs

    Then is mbse install and compile self made a port file its put to xinetd.d as mbsebbs and this file can be modified for the ports mbse is using.

    Take care,
    Gert

    - Get the best with linux -

    --- Msged/LNX 6.2.0 (Linux/2.6.39-gentoo-r1 (x86_64))
    * Origin: http://www.kofobbs.dk (2:230/150)
    --- SBBSecho 2.27-Win32
    * Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)
  • From Vincent Coen@2:250/1 to All on Wed Mar 2 19:20:17 2022
    Hello All!

    I have found a bug that was in 1.0.7 namely:

    Set up a reporting group for 1 file area (ECHOLIST)
    This area is also defined via 10.3 Hatch where the following is set :

    --
    1. Mask /home/mbse/elist/elst-gen/EL??????.ZIP
    2. Area ECHOLIST
    3. Replace
    4. Magic ECHOLIST
    5. Desc Zip'd Echo list archive Weekly and Monthly
    6. Dupe Yes
    7. Active Yes
    8. Deleted No
    9. Days Sun, Mon, Tue, Wed, Thu, Fri, Sat
    10. Month None
    --

    This is much the same as some others defined only they do have a value in Replace, otherwise it looks exactly the same other than the path in Mask.
    i.e., here is a full list of all in Hatch :

    --
    1. /home/mbse/elist/elst-gen/EL???
    2. /home/mbse/hatch-area/FDNINFO.Z
    3. /home/mbse/hatch-area/FGATEHDR.
    4. /home/mbse/hatch-area/FGATEZXX.
    5. /home/mbse/tmp/allfiles.zip
    6. /home/mbse/tmp/newfiles.zip
    --

    So so far so good - in 12. Reports I have :

    --
    12. NEWFILES REPORTS

    1. All Files to uk-file-dist
    2. All files -> Allfix-file
    3. All files -> FIDO-REQ
    4. ECHOLIST archive
    5. New file annoucenemts to FDN_An
    6. PDN announcements
    7. Shareware support
    --

    The first 3 all work as I can see the output via golded, 6 & 7 I do not read but
    the problem is with 4. ECHOLIST

    It does not work - no report is produced. Now this area is included with the other first three reports and all works but for some reason this one does not and the only thing I can think of that is different is that it is only for ONE file area and that area is generated by File Hatch (4) process.

    Any one any ideas about this ?

    Just for a test I have now added another area to this report for my ALLFILES area but will not know if it (report 4) now works until tomorrow and that is only for the added area as the primary one only is issued monthly.


    Vincent

    --- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Vincent Coen@2:250/1 to All on Fri Mar 4 22:49:21 2022
    Hello All!

    Wednesday March 02 2022 19:20, I wrote to you:

    As a follow on to this the last posting to ECHOLIST has DBridge announced when it is NOT selected for reporting.


    I think the database file for this is royally screwed up.


    Vincent

    --- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)