• sigterm optional

    From Pequito@21:1/126 to g00r00 on Monday, November 20, 2017 18:58:25
    g00r00,

    Is it possible to make an option to opt out of checking for the sigterm? I
    do not see the need 100% in all areas and would like to know if this can be done. Something like a /nosigterm on the data line or something. =)

    Cheers!
    Pequito

    --- Mystic BBS v1.12 A35 (Linux/32)
    * Origin: Twinkle BBS # (21:1/126)
  • From g00r00@21:1/108 to Pequito on Monday, November 20, 2017 23:37:02
    Is it possible to make an option to opt out of checking for the sigterm?
    I do not see the need 100% in all areas and would like to know if this
    can be done. Something like a /nosigterm on the data line or something.

    There might be a misunderstanding of what Mystic is doing. Mystic is checking for a connection loss. If it gets one, it tells the door to stop running (in this case DOSEMU) so it knows to close.

    What is the situation where you'd not want Mystic to send a shutdown notice to the door or program if a connection is lost? The alternative is the process may get stuck and the node maybe cannot shut down, or Linux kills the process aburptly when Mystic shuts the node down (because Mystic is it's parent).

    --- Mystic BBS v1.12 A36 2017/11/20 (Windows/64)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
  • From Pequito@21:1/126 to g00r00 on Monday, November 20, 2017 21:53:44
    On 11/20/17, g00r00 said the following...

    Is it possible to make an option to opt out of checking for the sigte I do not see the need 100% in all areas and would like to know if thi can be done. Something like a /nosigterm on the data line or somethi

    There might be a misunderstanding of what Mystic is doing. Mystic is checking for a connection loss. If it gets one, it tells the door to
    stop running (in this case DOSEMU) so it knows to close.

    What is the situation where you'd not want Mystic to send a shutdown notice to the door or program if a connection is lost? The alternative
    is the process may get stuck and the node maybe cannot shut down, or
    Linux kills the process aburptly when Mystic shuts the node down
    (because Mystic is it's parent).

    Majority just for GX commands, as these are not really doors, least I do not see them as such and believe they are handled a little differently? If not
    tis OK, was a thought. :)

    Cheers!
    Pequito

    --- Mystic BBS v1.12 A35 (Linux/32)
    * Origin: Twinkle BBS # (21:1/126)
  • From g00r00@21:1/108 to Pequito on Tuesday, November 21, 2017 11:15:20
    Majority just for GX commands, as these are not really doors, least I do not see them as such and believe they are handled a little differently? If not tis OK, was a thought. :)

    It doesn't do anything for GX. :)

    MPL and Python are executed inside of Mystic! There is no running of any external program for those, they are built into Mystic.

    --- Mystic BBS v1.12 A36 2017/11/20 (Windows/64)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)