• Re: mis problem, likely exists in xurrent a18 does exist in

    From Bcw142@46:1/138 to g00r00 on Monday, June 13, 2016 06:26:08
    Then I don't get something. I never really see any updated info when I
    install a new version so perhaps that's part of it. But I run mis as a daemon so the only way I know to stop it is kill the task. If I do so I can't start
    it up again (till I kill the semaphore). I found that out the hard way on the last kernel update (which has to force a reboot to install the new kernel). How is mis -d designed to be stopped now?

    --- Mystic BBS v1.10 (Linux)
    * Origin: Orbit BBS - Opp, AL USA | orbitbbs.ddns.net (46:1/138)
  • From g00r00@46:1/127 to Bcw142 on Monday, June 13, 2016 12:02:39
    Then I don't get something. I never really see any updated info when I install a new version so perhaps that's part of it. But I run mis as a

    I don't quite understand what you mean by "I never really see any updated info when I install a new version".

    Changes in each version are very well documented, if that is what you mean?

    install a new version so perhaps that's part of it. But I run mis as a daemon so the only way I know to stop it is kill the task. If I do so I

    If you kill -9 any task, the task never gets to shutdown because the operating system kills it immediately, without even notifying the application. This leaves application residue that can have negative effects, and it can cause other corruptions in data too.

    Its difficult to tell what you're actually doing because you haven't provided detail of how you're starting up and shutting down in the message, so I don't know if you're using a -9 or not or if you're using something else entirely.

    install the new kernel). How is mis -d designed to be stopped now?

    Nothing has changed as far as how you stop the process.

    You use kill and Linux sends it a SIGTERM, then MIS traps the signal and shuts down gracefully. Below is a log of me doing it, I added some spaces between each command to make it more readable, but otherwise its a direct cut and paste from my Ubuntu 14.04 terminal running A18:

    (I may add a 'mis -shutdown' option one of these days to make it easily doable without grepping the PID first).

    - [MIS] Executing Mystic Internet Server in daemon mode

    me@ubuntu:/a18$ ps -A | grep -w mis
    9415 ? 00:00:00 mis

    me@ubuntu:/a18$ sudo kill 9415

    me@ubuntu:/a18$ cat logs/mis.log

    Jun 07 15:55:08 Starting MIS in daemon mode
    Jun 07 15:55:08 MIS startup complete
    Jun 07 15:56:42 MIS received SIGTERM; shutting down
    Jun 07 15:56:43 MIS shutdown complete

    me@ubuntu:/a18$ ls semaphore
    me@ubuntu:/a18$

    me@ubuntu:/a18$ ps -A | grep -w mis
    me@ubuntu:/a18$

    --- Mystic BBS v1.12 A19 (Windows)
    * Origin: Sector 7 [Mystic BBS WHQ] (46:1/127)
  • From Bcw142@46:1/138 to g00r00 on Monday, June 13, 2016 19:26:10
    Ok, I'll do sudo kill PID on the mis PID. I guess I've gotten too use to the run away tasks that hog everything, which is why the -9 from another system
    via ssh or telnet (the real use and need of it).
    I did update to A19 so things are working better again (few mpl's worked with A18).

    --- Mystic BBS v1.10 (Linux)
    * Origin: Orbit BBS - Opp, AL USA | orbitbbs.ddns.net (46:1/138)
  • From g00r00@46:1/127 to Bcw142 on Tuesday, June 14, 2016 02:15:02
    Ok, I'll do sudo kill PID on the mis PID. I guess I've gotten too use to the run away tasks that hog everything, which is why the -9 from another system via ssh or telnet (the real use and need of it).

    Yeah the -9 means to kill it immediately. Linux doesn't even contact the daemon it just kills it which can result in data loss and corruption because the application never gets to shut down gracefully. Its a mean beast!

    In the case of MIS at the very minimum, you'll get stuck with a .BSY file.

    I'm glad it is working better for you now.

    --- Mystic BBS v1.12 A20 (Windows)
    * Origin: Sector 7 [Mystic BBS WHQ] (46:1/127)
  • From wkitty42@46:1/132 to g00r00 on Friday, June 17, 2016 10:50:50
    On 06/13/16, g00r00 said the following...

    (I may add a 'mis -shutdown' option one of these days to make it easily doable without grepping the PID first).

    is there a pid file created when mis is executed? generally in /var/run... if so, one can do

    sudo kill `cat /var/log/mis.pid`

    ;)

    --- Mystic BBS v1.10 A57 (Windows)
    * Origin: (46:1/132)
  • From g00r00@46:1/127 to wkitty42 on Friday, June 17, 2016 13:20:54
    (I may add a 'mis -shutdown' option one of these days to make it easi doable without grepping the PID first).

    is there a pid file created when mis is executed? generally in
    /var/run... if so, one can do
    sudo kill `cat /var/log/mis.pid`

    Yes, the PID is in a file within the semaphore directory so you could also do
    a cat like you've mentioned!

    --- Mystic BBS v1.12 A20 (Windows)
    * Origin: Sector 7 [Mystic BBS WHQ] (46:1/127)