1. Forum
  2. Fsxnet Message
  3. FSX MYS

  • Couple questions.

    From Jeff Smith@21:1/128.1 to All/Avon on Monday, June 25, 2018 18:42:26
    Hello there,

    Is it possible to have Fidopoll add a blank line to the log entry when it runs? It would make visually separating the log entries easier. Mutil already adds a line to separate the entries.

    When looking at the MIS screen on another machine I see "Res: 127" as I would
    assume a result indication. On this Mystic machine I see "Res: 0" as an assumed result indication. I recall the topic being mentioned previously but don't recall the specifics of what was typed. Both Mystic's seem to function ok. The "127" result looks to be expressed on each action by MIS. An excerpt from the MIS log on the other Mystic PC is:

    + 2018.06.25 18:50:06 EVENT Running event: Poll 1:229/426
    + 2018.06.25 18:50:06 EVENT Cmd: fidopoll 1:229/426
    + 2018.06.25 18:50:06 EVENT Res: 127
    + 2018.06.25 18:50:06 EVENT Cmd: mutil import.ini
    + 2018.06.25 18:50:06 EVENT Res: 127
    + 2018.06.25 19:09:17 EVENT Removing: /home/bbs/mystic/semaphore/echomail.out + 2018.06.25 19:09:17 EVENT Running event: Send outbound echomail
    + 2018.06.25 19:09:17 EVENT Cmd: mutil export.ini
    + 2018.06.25 19:09:17 EVENT Res: 127
    + 2018.06.25 19:09:17 EVENT Cmd: fidopoll send
    + 2018.06.25 19:09:17 EVENT Res: 127
    + 2018.06.25 19:09:17 EVENT Cmd: mutil import.ini
    + 2018.06.25 19:09:17 EVENT Res: 127

    While an excerpt from this MIS log is:

    + 2018.06.25 19:27:00 EVENT Running event: Poll (1:282/1031)
    + 2018.06.25 19:27:00 EVENT Cmd: /home/mystic/fidopoll 1:282/1031
    + 2018.06.25 19:27:01 EVENT Res: 0
    + 2018.06.25 19:27:01 EVENT Cmd: /home/mystic/mutil mailin.ini
    + 2018.06.25 19:27:01 EVENT Res: 0
    + 2018.06.25 19:30:46 HTTP 1-Request: index.html (161.0.252.166)
    + 2018.06.25 19:32:01 EVENT Running event: Poll 21:1/128.1
    + 2018.06.25 19:32:01 EVENT Cmd: /home/mystic/fidopoll 21:1/128.1
    + 2018.06.25 19:32:03 EVENT Res: 0
    + 2018.06.25 19:32:03 EVENT Cmd: /home/mystic/mutil mailin.ini
    + 2018.06.25 19:32:03 EVENT Res: 0

    It looks to only be a result of Events running based on the logs. Is there something that I can add to the list of things that I have missed? :)


    Jeff

    --- BBBS/Li6 v4.10 Toy-3
    * Origin: FsxNet: The Ouija Board - bbs.ouijabrd.net (21:1/128.1)
  • From Black Panther@21:1/186 to Jeff Smith on Monday, June 25, 2018 18:54:48
    On 06/25/18, Jeff Smith said the following...

    + 2018.06.25 18:50:06 EVENT Running event: Poll 1:229/426
    + 2018.06.25 18:50:06 EVENT Cmd: fidopoll 1:229/426
    + 2018.06.25 18:50:06 EVENT Res: 127
    + 2018.06.25 18:50:06 EVENT Cmd: mutil import.ini
    + 2018.06.25 18:50:06 EVENT Res: 127

    In the Events tab, list the command as: ./mutil import.ini and ./fidopoll. I had the same issue.

    + 2018.06.25 19:27:00 EVENT Cmd: /home/mystic/fidopoll 1:282/1031
    + 2018.06.25 19:27:01 EVENT Res: 0
    + 2018.06.25 19:27:01 EVENT Cmd: /home/mystic/mutil mailin.ini
    + 2018.06.25 19:27:01 EVENT Res: 0

    It's not doing it in this instance, as you are giving Mystic the path in the command.

    Hope this helps. :)


    ---

    Black Panther
    a.k.a. Dan Richter
    Sysop - Castle Rock BBS (RCS)
    telnet://bbs.castlerockbbs.com
    http://www.castlerockbbs.com
    The sparrows are flying again....

    --- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
    * Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)
  • From Avon@21:1/101 to Jeff Smith on Tuesday, June 26, 2018 13:11:34
    On 06/25/18, Jeff Smith pondered and said...

    Is it possible to have Fidopoll add a blank line to the log entry when
    it runs? It would make visually separating the log entries easier. Mutil already adds a line to separate the entries.

    I can log this as a request to pass to g00r00 when he next surfaces, it's
    hard coded as far as I know so only he can sort this.

    When looking at the MIS screen on another machine I see "Res: 127" as
    I would assume a result indication. On this Mystic machine I see "Res:

    Yes it means the shell command did not run. The reason the other (linux?) version of Mystic did is in the way you pathed the mutil and fidopoll command lines... with linux it's best to do something like

    ./mutil mailin.ini|./fidopoll send

    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Jeff Smith@21:1/128 to All/Avon on Monday, June 25, 2018 19:50:55

    Hello All/Avon!

    25 Jun 18 18:42, I wrote to you:

    + 2018.06.25 18:50:06 EVENT Running event: Poll 1:229/426
    + 2018.06.25 18:50:06 EVENT Cmd: fidopoll 1:229/426
    + 2018.06.25 18:50:06 EVENT Res: 127
    + 2018.06.25 18:50:06 EVENT Cmd: mutil import.ini
    + 2018.06.25 18:50:06 EVENT Res: 127

    While an excerpt from this MIS log is:

    + 2018.06.25 19:27:00 EVENT Running event: Poll (1:282/1031)
    + 2018.06.25 19:27:00 EVENT Cmd: /home/mystic/fidopoll 1:282/1031
    + 2018.06.25 19:27:01 EVENT Res: 0
    + 2018.06.25 19:27:01 EVENT Cmd: /home/mystic/mutil mailin.ini
    + 2018.06.25 19:27:01 EVENT Res: 0

    One item I see is the the path to the executable is specified on the lower FSxnet Mystic PC MIS log and it isn't on the upper Fido Mystic PC MIS log.
    I double checked and the full path is specified for all executables in each event on both PC's. The actual full path for the upper log executable is /home/bbs/mystic/mutil import.ini. Neither set of commandlines uses a preceding . (Period) as in ./home/<Etc.>.


    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 Flynn@21:2/102 to Jeff Smith on Monday, June 25, 2018 22:37:22
    On 06/25/18, Jeff Smith said the following...

    One item I see is the the path to the executable is specified on the
    lower FSxnet Mystic PC MIS log and it isn't on the upper Fido Mystic PC MIS log. I double checked and the full path is specified for all executables in each event on both PC's. The actual full path for the
    upper log executable is /home/bbs/mystic/mutil import.ini. Neither set
    of commandlines uses a preceding . (Period) as in ./home/<Etc.>.


    I had issues with this too - mine was that Mystic was seemingly not saving
    the setting. I put in ./ in front of the command and it would appear that it saved it but when I went back in later the ./ was gone. So what I did was
    just delete the entire line and put it back in with the pathing with ./ in front and then it worked.

    Thx
    Rich

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Flynn's Arcade (21:2/102)
  • From Jeff Smith@21:1/128.1 to Black Panther on Monday, June 25, 2018 21:05:14
    Hello Black,

    On 06/25/18, Jeff Smith said the following...

    In the Events tab, list the command as: ./mutil import.ini and ./fidopoll. I had the same issue.

    It's not doing it in this instance, as you are giving Mystic the path in the command.

    I have the complete path to the executable specified in each event on both Mystic PC's. On the Fido Mystic PC the event command-line is /home/bbs/mystic/mutil import.ini and on the Fsxnet Mystic PC the
    event command-line is /home/mystic/mutil mailin.ini. The same path is used for
    each executable on each PC respectively. That is why I couldn't understand why the full specified path would work on one PC and not the other. The only difference is the path's are different between the PC's. But each path used is
    correct for that respective PC. Mystic on this PC (I'm logged in to the BBBS PC at the moment) uses the path /home/mystic/mutil and Mutil returns a code of
    "0". One the other PC the path is /home/bbs/mystic/mutil and Mutil returns a
    code of "127".


    Jeff

    --- BBBS/Li6 v4.10 Toy-3
    * Origin: FsxNet: The Ouija Board - bbs.ouijabrd.net (21:1/128.1)
  • From Jeff Smith@21:1/128.1 to Avon on Monday, June 25, 2018 21:27:20
    Hello Avon,

    On 06/25/18, Jeff Smith pondered and said...

    I can log this as a request to pass to g00r00 when he next surfaces, it's hard coded as far as I know so only he can sort this.

    Kewl, Thanks. It was just a thought that it would be nice and hopefully wouldn't take much of a code change.

    When looking at the MIS screen on another machine I see "Res: 127" as
    I would assume a result indication. On this Mystic machine I see "Res:

    Yes it means the shell command did not run. The reason the other (linux?) version of Mystic did is in the way you pathed the mutil and fidopoll command lines... with linux it's best to do something like
    ./mutil mailin.ini|./fidopoll send

    Both PC's are Linux 64b. Both run Mystic v1.12 A39 Linux/64 Compiled 2018/04/21. Both Mystic event command-line's on each PC use the full path to the executable. The command-line on the Fsxnet Mystic PC uses the command-line of '/home/mystic/mutil mailout.ini' and when executed responds with a result code of "0". The Fido Mystic PC that uses the command-line of '/home/bbs/mystic/mutil import.ini' responds with a result code of "127". The resulting question that I had was why does the full path work on one PC and not
    the other?


    Jeff


    --- BBBS/Li6 v4.10 Toy-3
    * Origin: FsxNet: The Ouija Board - bbs.ouijabrd.net (21:1/128.1)
  • From Black Panther@21:1/186 to Jeff Smith on Monday, June 25, 2018 23:36:21
    On 06/25/18, Jeff Smith said the following...

    I have the complete path to the executable specified in each event on both Mystic PC's. On the Fido Mystic PC the event command-line is /home/bbs/mystic/mutil import.ini and on the Fsxnet Mystic PC the
    event command-line is /home/mystic/mutil mailin.ini. The same path is used for each executable on each PC respectively. That is why I
    couldn't understand why the full specified path would work on one PC and

    That's interesting... Have you tried just using './mutil import.ini' or './mutil mailin.ini' in the command line, to see if that works without giving the 127 errorcode?

    Otherwise, I'm stumped... :(


    ---

    Black Panther
    a.k.a. Dan Richter
    Sysop - Castle Rock BBS (RCS)
    telnet://bbs.castlerockbbs.com
    http://www.castlerockbbs.com
    The sparrows are flying again....

    --- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
    * Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)
  • From Avon@21:1/101 to Jeff Smith on Tuesday, June 26, 2018 19:24:35
    On 06/25/18, Jeff Smith pondered and said...

    Both PC's are Linux 64b. Both run Mystic v1.12 A39 Linux/64 Compiled 2018/04/21. Both Mystic event command-line's on each PC use the full
    path to the executable. The command-line on the Fsxnet Mystic PC uses
    the command-line of '/home/mystic/mutil mailout.ini' and when executed responds with a result code of "0". The Fido Mystic PC that uses the command-line of '/home/bbs/mystic/mutil import.ini' responds with a
    result code of "127". The resulting question that I had was why does the full path work on one PC and not the other?

    It sounds like a linux thing, could be permissions, or perhaps mystic cannot see where the main mystic.dat file is

    Refer to the setting in MUTIL

    ; Set this value if you want to run mutil from a directory other than
    ; the root Mystic directory or the mysticbbs environment variable:

    ; mystic_directory=c:\mystic\mystic.dat

    My hunch is it's related to the latter.

    Also what does the mutil logging show (level 3) when the 127 result code occurs?

    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From CyntaxX@21:4/113 to Jeff Smith on Tuesday, June 26, 2018 08:27:25
    On 06/25/18, Jeff Smith said the following...

    + 2018.06.25 18:50:06 EVENT Cmd: mutil import.ini

    + 2018.06.25 19:27:01 EVENT Cmd: /home/mystic/mutil mailin.ini

    When I run my events I use just ./mutil mailin.ini. I would check the permissions on your bbs directory.

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Digital Wurmhole | digitalwurmhole.ddns.net:2323 (21:4/113)
  • From bcw142@21:1/145.3 to Jeff Smith on Tuesday, June 26, 2018 12:55:14
    On 06/25/18, Jeff Smith said the following...

    executables in each event on both PC's. The actual full path for the
    upper log executable is /home/bbs/mystic/mutil import.ini. Neither set
    of commandlines uses a preceding . (Period) as in ./home/<Etc.>.


    It's a Linux/Unix thing. /home/bbs/mystic/mutil is the full path, that will always work. ./mutil is the relative path from mystic's root path, so either should work. The full path will always point to the same spot, but themes
    will point text, menus, and scripts to other relative paths and the full path will always point to the same place. So if you have snake.mpx in /mystic/scripts/snake.mpx and you use that full path in all themes they will all get the same version with the same high scores and such. Normally each theme would point to a different script directory, but the full path will override that.

    --- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
    * Origin: Workpoint (21:1/145.3)
  • From Jeff Smith@21:1/128.1 to bcw142 on Wednesday, June 27, 2018 03:24:58
    Hello bcw142,

    On 06/25/18, Jeff Smith said the following...
    executables in each event on both PC's. The actual full path for the
    upper log executable is /home/bbs/mystic/mutil import.ini. Neither set
    of commandlines uses a preceding . (Period) as in ./home/<Etc.>.

    It's a Linux/Unix thing. /home/bbs/mystic/mutil is the full path, that will always work. ./mutil is the relative path from mystic's root path, so either should work.

    I by default use the full path when specifying a path. There seems to be less chance of confusion with consistency. Ownership and permissions can also play a
    part sometimes with Linux. Especially when one or the other gets changed unexpectedly.

    Jeff


    --- BBBS/Li6 v4.10 Toy-3
    * Origin: FsxNet: The Ouija Board - bbs.ouijabrd.net (21:1/128.1)